Highlights → Platform documentation overhaul

Platform documentation overhaul

April 13, 2026. SGEN's documentation surface gets a full rewrite. Every customer-facing feature now has a dedicated page. Reference, Guides, Changelog, and Start Here all open together.

What changed

Before today, SGEN's documentation was a starter outline — useful for orientation, thin on detail. As of April 13, the docs surface is its own project: hundreds of pages organized into four reading tracks, each shaped for a different reading intent.

After today, you can find the exact field, the exact step, the exact troubleshooting note you need without leaving the site.

The four tracks

Start Here. Three short pages for first-time visitors — Welcome, What Is SGEN, Why SGEN Exists. Read top to bottom in about 10 minutes. Sets the framing before you dive into Guides or Reference.

Guides. Task-oriented walkthroughs. "How to build your first site." "How to set up forms and route submissions." "How to launch a multi-location business." Each Guide reads as a sequential flow — open, follow steps, finish with a working result.

Reference. Feature documentation by surface. SG-Dashboard, SG-Admin, SG-Builder, SG-Core, plus the cross-cutting concepts. Each Reference page is exhaustive and lookup-shaped — land here, find the one field or option, leave.

Changelog. The Changelog page — every shipped change with a customer-readable summary, cross-referenced back to the relevant Reference and Guide pages.

What's behind the rewrite

The rewrite is driven by a simple constraint: every reader question should land on a page that answers it. "What does the Title field accept?" should resolve to the field's Reference entry. "How do I migrate from WordPress?" should resolve to the Guide that walks the migration. "What changed last week?" should resolve to the Changelog.

To meet that, every customer-facing feature gets its own page. The Reference tier has full per-feature pages for forms, posts, pages, blog, users, custom objects, custom fields, media, redirects, SEO, integrations, and more. The Guides tier has practical walkthroughs covering site setup, day-to-day editing, and launch checklists.

The reading rules

Each page is built against a shared structure so you can predict what you'll find:

  • What is this for — the feature in plain language
  • Good use cases — when to reach for this
  • What NOT to use this for — boundaries
  • How this connects to other features — cross-references
  • Before you start — prerequisites
  • Where to go — the admin path
  • Steps — numbered walkthrough
  • What success looks like — verification
  • What to do if it does not work — troubleshooting

Reference pages skip the "Steps" section. Guides pages keep all of it. That predictability matters more than clever layout — once you know where the troubleshooting section lives, you can skim straight to it on every page.

The voice rules

Every page follows a published voice canon:

  • No marketing fluff. No "seamless." No "effortless." No "best-in-class." Features earn praise by working, not by adjectives.
  • Concrete examples. The canonical fictional brand is Acme Coffee Roasters — a multi-product, multi-location coffee business. Every example uses Acme so the narratives stay coherent across pages.
  • Honest about edges. Every Guide closes with the things that go wrong and how to fix them. Every Reference page lists defaults, limits, and common mistakes.

The voice rules are enforced by a linter on every save. Drafts that violate them don't ship.

How to navigate

  • New to SGEN? Start at Start Here → Welcome. Ten minutes to orient.
  • Have a task in mind? Guides has the walkthrough. Sort by category or browse by area.
  • Need to look up a specific field or option? Reference is the lookup surface. Browse by SG-Admin area or use search.
  • Want to know what just shipped? Open the Changelog page.

What's coming next

A few items in flight that aren't in today's surface:

  • Architecture section — Foundation, Reliability, and Security pages are being authored as part of the Reference tier. Some leaves are placeholders; content fills in over the next two weeks.
  • Multi-site guides for agencies and operators running 5+ sites under one admin. Currently a placeholder in Guides.
  • Comparison pages for teams evaluating SGEN against other platforms. In flight on the marketing side.

When those land, they will be announced on the Changelog. For now, the four core tracks are open and ready.

Why this matters

A platform without docs is a platform with a customer-support tax. Every question that should resolve to a page becomes a ticket. Every team that joins SGEN spends weeks finding the same answers a doc would have solved in minutes.

Launching the docs at the same time as the platform — instead of months later — collapses that gap. The team that signs up on April 20 has the same docs surface available as the team that signs up six months from now. The first customer and the thousandth customer get the same answers from the same pages.

Next steps

  • Open Guides → Start Here to walk through SGEN end-to-end.
  • Pick a Reference area that matches your current task to feel the depth.
  • Bookmark the Changelog page for the running list of shipped changes.
On this page