Welcome to SGEN Docs

The operator documentation for the SGEN platform — start here to find the right page for what you are trying to do.

This is the landing page for SGEN's documentation. It is written for operators — the people running sites on SGEN — and is structured so that the most common reasons to open the docs lead to the right page in one or two clicks.

If you are new to SGEN, the recommended path is: read this page, follow the orientation links into the Start Here pillar, then move into the Shared Concepts pillar to internalize the platform's operating model. After that, the per-area Reference and Guides will make sense in operator language without backfilling.

If you are returning to the docs after time away, the documentation map and the per-area Reference are the fastest re-entry points.

What is this for?

This page is the entry point to SGEN documentation. Use it to orient yourself, to confirm you are in the right place for your question, and to pick the next page that matches what you are trying to do. The page is short on definitions and long on direction — definitions live in the Start Here pillar and the Shared Concepts pillar, both linked from here.

Good use cases

• You created a SGEN account and want to know where to start.
• You are returning to SGEN after time away and need a fast re-entry into the docs.
• You are evaluating SGEN and want to read the operator-facing docs to assess fit.
• You are explaining SGEN to a stakeholder and want a single link to share as a starting point.
• You hit a "where does this question even belong?" moment and want a navigation page that helps you triage.

What NOT to use this for

• Step-by-step procedures — open the relevant Guide.
• Per-area Reference for a specific module — open the per-area Reference page.
• Architecture-tier explanations of how SGEN is built — open the Architecture pillar.
• Per-release shipped behavior change — open What's New or Changelog.

How this connects to other features

• Welcome to SGEN Docs — the longer-form welcome that this landing routes into.
• What is SGEN — the operator-language definition of the platform.
• Documentation Map — the full docs structure at a glance.
• How This Documentation Works — the conventions used across the docs.
• Shared Concepts Index — the operating-model pillar.
• Platform Architecture Overview — the architectural framing.

The three platform surfaces — pick the one that matches your task

SGEN exposes three operating surfaces. The right one to open depends on what you are trying to do.

SG-Dashboard — account-tier control

SG-Dashboard is the multi-site control surface. Use it for billing, per-site provisioning, account-level reporting, and managing the account user roster. Open it when your task is "across all our sites" rather than "inside this one site."

SG-Admin — per-site administration

SG-Admin is the per-site administrative surface. Use it for content (Pages, Posts, Products, Forms, Custom Objects, Locations, Events), modules (Store, Custom Objects, Configuration), publishing operations (save, publish, promote), and per-site user management. Open it when your task is "inside this one site."

SG-Builder — visual page composition

SG-Builder is the visual page editor. Use it to compose Pages and to apply per-page styling without writing template code. Open it when your task is "build or edit this specific page."

The Start Here pillar — orientation reading

The Start Here pillar gives operators the orientation they need before diving into per-area work. Read these pages in order if you are new to SGEN.

• Welcome to SGEN Docs — the longer-form welcome and platform introduction.
• What is SGEN — the operator-language definition of what SGEN is and what it replaces.
• How This Documentation Works — the conventions, structure, and reading models the docs use.
• Documentation Map — the full structure of the docs at a glance.

The Shared Concepts pillar — operating model

The Shared Concepts pillar is the platform-tier operating model that every per-area Reference and Guide assumes. Read these five pages after the Start Here pillar.

• Shared Concepts Index — pillar entry point with reading order.
• Environments and Site States — staging vs live + record states.
• Publishing Model — save / publish / promote operations.
• Roles and Access — account-tier vs site-tier authority.
• Data and Tracking Model — capture surfaces + governance.
• Integrations Model — first-party connectors.

Architecture pillar — how the platform is built

The Architecture pillar describes how SGEN is built rather than how it operates. Open it when you want the system-level framing.

• Platform Architecture Overview — the architectural framing for the rest of the section.

Find the right page by question

Sometimes you arrive at the docs with a question and want to know which page answers it. The mapping below is for the most common starting questions.

Definition

This page is the landing page for SGEN documentation — the canonical entry point at the docs root URL. Its role is orientation and routing rather than content depth. Definitions live elsewhere; this page directs the reader to where each definition is.

The landing page is intentionally short on operating-model content. The Shared Concepts pillar (linked above) carries that load. This page's job is to make that pillar discoverable for new readers and to be a stable re-entry point for returning ones.

Purpose

The purpose of this page is to be the smallest useful first page. A new reader should be able to read this page in under three minutes, follow the recommended links, and arrive at the right next page without having to guess which one applies to their question.

Scope

This page covers the docs landing at the orientation level — direction rather than definition.

The page covers:

• The three platform surfaces and when to open each.
• The Start Here pillar and recommended reading order for new operators.
• The Shared Concepts pillar entry point.
• The Architecture pillar entry point.
• A question-to-page mapping for fast triage.

• Definitions — those live in the linked pillars.
• Procedures — those live in per-area Guides.
• Per-area Reference — open the relevant area page.
• Per-release behavior change — open What's New or Changelog.

What the docs are organized around

SGEN documentation is organized into four content categories. Knowing the categories speeds up navigation.

Category 1 — Documentation

Concept-and-orientation pages. The Start Here pillar, Shared Concepts pillar, Architecture pillar, and per-area overviews live here. Open Cat 1 when you want to understand how the platform works.

Category 2 — Reference

Per-feature definition pages. Each module, each setting, each surface has a Reference entry. Open Cat 2 when you want the structural shape of a specific feature.

Category 3 — What's New

Per-release announcements of shipped features. Open Cat 3 when you want to see what landed in the most recent release.

Category 4 — Changelog

Per-release status-transition record. Open Cat 4 when you want the history of a feature's behavior across releases.

Examples

Example 1 — A new operator's first 15 minutes

A new operator opens this page. They read the orientation (under three minutes), open Welcome, then What is SGEN, then How This Documentation Works, then Documentation Map. They have an oriented mental model. Next they open the Shared Concepts Index and walk through the five pillar pages in reading order. They are now ready to open per-area Guides without backfilling vocabulary.

Example 2 — A returning operator triages a question

An operator who knows SGEN well opens this page after returning from a quarter away. They scan the question-to-page mapping, find their question (a CRM connector is failing), follow the link to Integrations Model, jump to the failure-handling section. The landing page handed off the triage in under a minute.

Example 3 — A stakeholder wanting context before a meeting

A stakeholder needs to understand SGEN at a high level before a partner conversation. They open this page, follow the link to What is SGEN, read it once, then come back to the landing and skim the three platform surfaces. They have the orientation they need for the conversation without committing to operator-tier reading depth.

Example 4 — A partner agency landing a new client account

An agency principal sets up a new SGEN account for a client. They send their team this page as the canonical onboarding link. The team works through Start Here and Shared Concepts in order, then opens the admin and SG-Dashboard Reference. The agency is ready to operate.

Example 5 — Confirming the docs are still aligned with SGEN's behavior

An experienced operator notices SGEN's publish flow looks slightly different from what they remember. They open this page, follow the question-to-page mapping to Publishing Model, and confirm whether the change is shipped (the page would be updated) or whether they are misremembering (the page matches their old memory and the difference is in their recall, not the platform).

Example 6 — Sharing a precise docs entry

An operator wants to send a colleague the right docs page for "why can this user not publish?" They open this landing, find that question in the mapping, copy the link to Roles and Access, and share that link directly. The colleague does not have to land on a generic docs root and search.

Documentation guidance

This page is the docs root landing. Treat its links as the canonical entry-points to each pillar. Per-area Guides should reference this page only when they need to send a reader back to orientation; deeper-context references should link to the specific Reference or shared-concept page directly.

For step-by-step procedures, open the relevant Guide. For the operating model, open Shared Concepts. For architectural framing, open Architecture. For per-area definitions, open the per-area Reference page.

Reading order

If you are new to SGEN, the recommended order is: this page → Welcome → What is SGEN → How This Documentation Works → Documentation Map → Shared Concepts Index → the five Shared Concepts siblings → per-area Reference for the area you need.

Related reading

• Welcome to SGEN Docs — longer-form welcome.
• What is SGEN — operator-language definition.
• How This Documentation Works — docs conventions.
• Documentation Map — full docs structure at a glance.
• Shared Concepts Index — operating-model pillar.
• Platform Architecture Overview — architectural framing.
• SG-Dashboard Overview — account-tier surface.
• SG-Admin Overview — site-tier surface.
• SG-Builder Overview — page-tier surface.

Vocabulary cross-reference

• Landing page — this page; the canonical entry point at the docs root URL.
• Pillar — a coherent set of docs pages that together describe one operating concern (Start Here, Shared Concepts, Architecture).
• Surface — a SGEN platform tier exposed to operators (SG-Dashboard, SG-Builder).
• Per-area Reference — pages defining specific platform areas; assumes Shared Concepts.
• Per-area Guide — step-by-step procedures inside a specific area; references Shared Concepts.
• Cat 1 / Cat 2 / Cat 3 / Cat 4 — the four content categories the docs are organized into.
• Question-to-page mapping — the table on this page that helps a reader locate the right docs entry by question.
• Operator — a person running a SGEN site or account; the primary audience for these docs.
• Re-entry point — the role this page plays for returning operators.
• Orientation read — the recommended first-15-minutes path through the docs for new operators.
• Stakeholder read — a shorter path for stakeholders; may stop at this page plus What is SGEN.
• Partner agency read — the role this page plays for external agencies setting up SGEN for clients.
• Docs root — the URL the landing page sits at; the canonical share target for "send the SGEN docs."
• First-15-minutes path — the recommended new-operator reading sequence; designed to fit inside a single sitting.
• Triage — the act of figuring out which docs page applies to a question; this landing's question-to-page mapping accelerates triage.
• Routing link — a link from this landing into a pillar or per-area page; routes the reader rather than re-explaining content.
• Operator-tier docs — documentation written for the people running SGEN sites; this landing's primary audience.
• Stable share link — the property of this landing's URL: the docs root URL is stable so that external references and onboarding emails do not break across releases.
• Pillar entrypoint — a link from this landing into the index of a pillar (Start Here, Shared Concepts, Architecture).
• Multi-audience landing — the role this page plays for new operators, returning operators, stakeholders, partner agencies, and contractors with a single coherent entry.