Changelog

The tutorials page had a fixed-position sidebar + main column layout that produced a persistent visual bug — sidebar nav items were rendering behind the hero text in some viewports, and the layered positioning made the page hard to read.

Rebuilt /tutorials.html to match the simpler content-page pattern used by the rest of the site: top nav, page hero, six full-width step sections with alternating backgrounds, CTA, footer. All step content (the V1.9.0 we-create-the-bot flow for Step 1, plus Brainwriting, Gmail, Onboarding, Delegating, Scheduling) is preserved verbatim. The "Start with Setup" button still smooth-scrolls to Step 1.

Also fixed footer links: Privacy Policy, Terms of Service, and Refund Policy now point to the right pages instead of dead anchors.

The site moved from villapx07.github.io/Banana/public/ to its own proper domain: getforge.ph. Cleaner URLs, real credibility, free email matching the domain, and a real address to put on invoices and KYB forms.

What changed under the hood:

• Purchased getforge.ph via dot.ph (2-year registration, with WHOIS privacy)
• Pointed the domain at GitHub Pages via 4 A records + 1 www CNAME
• Flattened the repo from /public/ to the repo root so GH Pages could serve the custom domain (the folder dropdown wouldn't accept /public)
• Promoted the real homepage from forge-assistants.html to index.html (they were duplicates, the new one won)
• Updated every canonical, og:url, and internal link across all 8 pages to use getforge.ph instead of the GitHub URL
• Free dot.ph email bundled with the domain registration (10GB, real IMAP/SMTP, SPF/DKIM/DMARC pre-configured) — usable as paolo@getforge.ph for pitches, billing, and customer comms

Bonus: the hero price label changed from "Starting price / month" to "Plans from / month" to make it clear ₱599 is a floor, not a ceiling, since the pricing section has multiple tiers.

HTTPS via Let's Encrypt is propagating — should be live within 1–4 hours. The HTTP version works in the meantime.

Setting up your Forge Assistant used to require a 5-step BotFather dance: open Telegram, create a bot, copy a token, send it to us, then find your numeric user ID. That was too much friction for the moment a customer decides to start.

Now you just send us three things:

• The name of your Forge Assistant (e.g. "Ava", "Max", "Maya")
• Your Telegram handle (e.g. @janedoe)
• Your numeric Telegram user ID — get it by messaging @userinfobot

We create the bot, name it @forge_<your-handle>_bot, bind it to your user ID, and message you on Telegram when it's live — usually within 5 minutes during business hours.

Also: the inquiry form now has a banner for customers who already know they want to start. And the security page was updated to reflect the new model — your bot is now routing infrastructure we hold, not a credential you hold.

PayMongo and a self-serve payment journey are coming, but the refund policy needs to be in place before the first paid charge happens. So we wrote it now.

The principle is the same as the landing page: cancel anytime, no refunds on paid periods. Once a monthly payment is processed, the service is committed for that month — but you can cancel any time and never be charged again.

Read the full policy at /refund.html. The one exception is a service credit if our infrastructure fails — not a refund, but a credit on your next bill.

The old "When Forge Is the Wrong Choice" section had 4 self-flagellating cards sitting right before the social proof — too much self-criticism in the conversion zone.

Replaced with a tighter 2-card "Quick gut-check" at the bottom of the page (after the Final CTA, before the footer) covering the two cases that actually matter: you need a human's signature on the output, or you want a headcount replaced rather than a workload augmented. Less apologetic, same honesty.

The hero now opens with "Wake Up to Work Already Done" — anchored on the outcome, not the mechanism. The How It Works section shows a real-looking 6:00 AM Telegram delivery so visitors see exactly what they'll get.

Added a "When Forge Is the Wrong Choice" section, an inquiry form hook ("we'll tell you if it's not a fit"), and a paragraph on the about page making clear that Paolo is the only human on the Forge team — we ship the product we sell.

Two clarifications customers were asking about:

• How we handle your credentials: bot tokens and IMAP passwords are stored in encrypted provisioning config, used only to deliver the service, never shared with anyone (including the Forge team), and removable on request.
• Your brainwriting is your data — not used to train any external model, never sold, and you can revise or erase any of it at any time.

Old copy said "Give Forge Your IMAP Credentials" and asked you to share them with the team. New copy says "Connect Your Gmail Inside Forge" and walks you through entering them directly into your own Forge instance. We never see your password.

The setup guide now includes an explicit step for finding your numeric Telegram user ID via @userinfobot, with a one-liner on why we use a number (not a username) to identify you.

Renamed the sidebar label from "Sections" to "On this page", added a sticky "You are in [section name]" indicator so you always know where you are on long pages, and a "Need help?" / "Back to top" footer block.

You are here. This page is the public, customer-facing version of our internal CHANGELOG. We also added a soft link to the tutorials page in the hero and final CTA of the landing, and a "Changelog" link in the footer.

The sidebar that helps you jump between tutorial sections was hard to see against the page background on some browsers — the panel edge blended in with the scrolling content underneath.

Now it stands out clearly, and section navigation reads as a proper panel.

We heard you: 3 plans, 3 prices, no quick way to know which one fits.

Added a short "Pick this if you…" guide under each plan with the 3 best-fit scenarios:

Starter — freelancer, consultant, or solo founder testing AI agents before committing.

Pro — daily AI workflow (research, scraping, writing, scheduling), code execution, and the 300-action Starter cap is too tight.

Advanced — small team running multiple agents in parallel, building websites or landing pages with Forge, needing max throughput and a dedicated support channel.

We now have a dedicated /security.html answering the question every serious buyer asks: "is this safe to give my password?"

Covers what we protect, what we don't do (no selling your data, no model training on your emails, no ad networks), how to request data deletion, our incident response, and our SOC2 Type 1 audit roadmap for Q1 2027.

Also: the team page now clearly states "Paolo is the only human on the Forge team. Everyone else is an AI." (We ship the product we sell.)