Highlights → SGEN Docs is now live

SGEN Docs is now live

April 20, 2026. SGEN Docs launched the same day the platform did. Every admin feature, every public-side flow, every common workflow has a page you can read before, during, or after using the feature itself.

What you can read today

The docs site is organized into four top sections:

  • 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 top-to-bottom, with numbered steps and example narratives.
  • Reference — feature documentation by surface. SG-Dashboard, SG-Builder, SG-Core, plus configuration, workflows, and shared concepts. Each Reference page is exhaustive and indexable — land here, find the one field or option, leave.
  • What's New — launch announcements like this one. Read what shipped, when, and what it changes for you.
  • Changelog — the engineering ledger. Two weeks of pre-launch foundation work (April 3 through 16) plus every change shipped since.

Why launch-day docs matter

Most platforms ship features and then catch up on documentation. The result: a window of weeks or months where customers discover features by guessing, by reading support threads, or by emailing the team. That window erodes trust in the product and burns the support team's time.

SGEN's approach inverts the timeline. The documentation surface was built alongside the platform. Every Admin controller, every public flow, every workflow that the dev team built has an accompanying page. By the time the product was public, the docs were not a backlog — they were a finished surface.

That means:

  • When you click into a feature for the first time, the help link works.
  • When you search for a term — "redirects", "tracking consent", "custom objects" — you find the page, not a placeholder.
  • When you need to onboard a teammate, you can hand them the docs URL and walk away.

Three audiences, one docs surface

The docs site serves three different reader intents under one URL:

  • Customer admins building a site. Most pages are written for this reader — clear language, concrete examples, no platform jargon.
  • Internal staff running support and ops. Some pages link out to internal runbooks (private — not on this site). Others are public but written with the assumption you know SGEN deeply.
  • Platform engineers evaluating the architecture. The Architecture section (Foundation, Reliability, Security) is for people deciding whether to adopt SGEN at scale.
Each page declares its audience at the top so you know whether you're in the right place.

The voice contract

A consistent reader experience matters as much as completeness. The docs follow a published voice canon:

  • No marketing fluff. No "continuous." No "simple." No "standard." If a feature is good, the doc shows you how to use it and you decide.
  • Concrete language. "Click Save" not "engage the persistence layer." "The Title field accepts up to 60 characters" not "title configuration is highly flexible."
  • Honest about edges. Every Guide page has a "What to do if it doesn't work" section. Every Reference page has the defaults, the limits, and the common mistakes.
  • One canonical fixture. Examples use a fictional brand (SGEN Digital) so customer data never appears in public-facing prose.
The voice contract is enforced by a linter on every save — drafts that violate the contract don't ship.

How to navigate

  • First time on SGEN? Open Guides → Start Here. The "Welcome" and "What Is SGEN" pages set the framing.
  • Looking up a specific feature? Open Reference and browse by admin area. Or use the search box.
  • Want the engineering ledger? Open Changelog.
  • Want the roadmap? Open Roadmap — features organized by Horizons (NOW / NEXT / LATER).

What's next for the docs site

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

  • Architecture section. Foundation / Reliability / Security pages are being authored — the L1 is visible but the leaves will fill in over the next two weeks.
  • Multi-Sites guide for agencies and operators running 5+ sites under one admin login. Currently a TBD slot in Guides.
  • Why SGEN Explained — a positioning page for people comparing platforms. In flight on the marketing side.
The docs are now the source of truth for what SGEN does. If something is missing, that means we haven't written it yet — file a request through the in-product feedback path.

Next steps

  • If you're new, start at Guides → Start Here → Welcome.
  • If you've used SGEN before today, the rest of the Highlights set walks through each major capability that shipped — Sandbox, Custom Objects, Cross-site Analytics, Site Backups, and more.
On this page