Guides → Documentation Map

How to find any page in SGEN Docs

This page is the full IA map. Every group, every section, every page lives somewhere in this tree.

Use it when you can't remember where a page lives, when you want to see the full picture, or when you're orienting a teammate. Bookmark it if you switch between sections often.

Field	Value
Audience	public
Area	welcome
Updated	2026-05-14

What is this for?

The Documentation Map is the master navigation surface. Unlike the left sidebar (which only shows the active section's depth) or search (which returns matches but not structure), this page shows the complete shape of the docs at a glance.

You read it when you need the full picture. You stop reading it once you've memorized where things live.

Good use cases

You're new to SGEN Docs and want to see the full tree before drilling in.
You're looking for a page and don't know which group it lives in.
You're explaining the docs to a teammate.
You're auditing your own docs coverage and want to know what exists.
You're checking if a recent surface has documentation yet.

When NOT to use this

For specific page content — open the page directly.
For step-by-step setup — use the how-to articles.
For released change history — that's Changelog.

How this connects to other features

This page sits alongside the other orientation pages.

Welcome to SGEN Docs — entry point.
What is SGEN — platform definition.
Why SGEN Exists — operational rationale.
How This Documentation Works — content classes and reading model.

Read those first. This map then snaps into place.

Before you start

A note on the map.

This is a snapshot of the IA as of 2026-04-30. The platform evolves and so do the docs. If you find a discrepancy between this map and the actual sidebar:

The sidebar is canonical for live structure.
This page is updated regularly but may lag by a release.
Open a support ticket if a critical page is missing from both.

A note on URLs.

Every URL in this map starts with /docs/. Full canonical form is https://docs.sgen.com/docs/. The shorthand throughout the page omits the host and shows only the path.

A note on under-construction sections.

The Reference group is currently scaffolded — most pages exist as placeholders awaiting deeper content. Use the Guides group for full narrative documentation while Reference fills in.

The full map

Full IA map — 7 top-level groups

Start Here — 6 pages · orientation

Platform — 5 pillars + cross-cutting

Operations — 7 daily-driver surfaces

Architecture — 7 reasoning pages

Changes — 3 release streams

What's New — editorial highlights

Supporting — How-to · FAQ · Reference · Practical Guides · Production Docs

Start Here — orientation

Where every new SGEN user begins. Read in order on first visit.

/docs/start-here/welcome — Welcome to SGEN Docs (entry point with per-segment routes)
/docs/start-here/what-is-sgen — What is SGEN (platform definition with five product surfaces)
/docs/start-here/why-sgen-exists — Why SGEN Exists (operational rationale, pain → architecture)
/docs/start-here/how-this-documentation-works — How This Documentation Works (content classes, reading model)
/docs/start-here/documentation-map — This page (full IA tree)
/docs/start-here/shared-concepts/ — Cross-platform concepts (publishing model, environments, roles, integrations, data and tracking)

Start Here · 6 pages
📁 /docs/start-here/
├─ welcome
├─ what-is-sgen
├─ why-sgen-exists
├─ how-this-documentation-works
├─ documentation-map (this page)
└─ shared-concepts/

Platform — the product surfaces

The five product pillars and their supporting surfaces. Each pillar has a section landing plus deep pages per feature.

Platform · 5 pillars + cross-cutting

SG-Core — 9 surfaces · foundation

SG-Modules — 12 modules · capability

SG-Dashboard — 8 surfaces · multi-site

SG-Admin — 6 surfaces · single-site

SG-Builder — visual editor + component library + breakpoints + layer manager

Cross-cutting — Appearance · Site Settings · Automations · Integrations · Workflows · Custom Codes/CSS/Fonts

SG-Core (the foundation)

The structural objects every site depends on. Read the section landing first; deep pages cover individual surfaces.

/docs/platform/sg-core — Section landing
/docs/platform/sg-core/users — User accounts and access (Members, Invitations, role assignments)
/docs/platform/sg-core/menus — Navigation structures (header menus, footer menus, mobile menus)
/docs/platform/sg-core/media-library — Asset storage (images, videos, documents, with WebP conversion)
/docs/platform/sg-core/pages-posts — Core content objects (pages, posts, scheduled publishing, revisions)
/docs/platform/sg-core/templates — Reusable layouts for pages and posts
/docs/platform/sg-core/custom-objects — Structured content beyond pages and posts
/docs/platform/sg-core/popups — Overlay surfaces (cookie banners, exit intents, scheduled popups)
/docs/platform/sg-core/blogs — Blog content with categories and tags
/docs/platform/sg-core/custom-fields — Field schema for structured content

SG-Modules (capability layer)

First-party modules that replace plugin-stack capability. Module count grows quarterly — see the changelog for the current shipped list.

/docs/platform/sg-modules — Section landing
/docs/platform/sg-modules/forms — Form creation, submissions, and notifications
/docs/platform/sg-modules/discussions — Discussion and comment surfaces
/docs/platform/sg-modules/events — Event records with date and location
/docs/platform/sg-modules/locations — Location records for multi-location operators
/docs/platform/sg-modules/phone-taps — Phone tap attribution and call tracking
/docs/platform/sg-modules/redirects — Redirect rules with regex support
/docs/platform/sg-modules/tracking-consent — Consent management for GDPR compliance
/docs/platform/sg-modules/seo — SEO module (meta titles, descriptions, schema, sitemaps)
/docs/platform/sg-modules/page-builder — Page Builder module (the SG-Builder integration)
/docs/platform/sg-modules/ecommerce — Ecommerce module (products, orders, coupons)
/docs/platform/sg-modules/attributions — Marketing attribution tracking

SG-Dashboard (multi-site command view)

Account-level surface for portfolios. Multi-site operators land here daily.

/docs/platform/sg-dashboard — Section landing
/docs/platform/sg-dashboard/site-manager — Per-site control surface (status, environments, owners)
/docs/platform/sg-dashboard/analytics — Dashboard reporting across sites
/docs/platform/sg-dashboard/live-analytics — Connected analytics views (Ads, GA, GMB, GSC)
/docs/platform/sg-dashboard/reports — Generated report outputs (PDF, CSV)
/docs/platform/sg-dashboard/billing — Subscription, plans, and per-site billing math
/docs/platform/sg-dashboard/backups — Site-level backups with .sgen archive format
/docs/platform/sg-dashboard/support — Support ticket surface
/docs/platform/sg-dashboard/dashboard-guides/ — Onboarding guides for SG-Dashboard

SG-Admin (single-site operating shell)

Inside each site. Where day-to-day site work happens.

/docs/platform/sg-admin — Section landing
/docs/platform/sg-admin/dashboard — Site dashboard (key metrics, quick actions)
/docs/platform/sg-admin/blacklist — IP and entity blocking
/docs/platform/sg-admin/activity-log — Admin event capture (sign-ins, publishes, settings changes)
/docs/platform/sg-admin/stage-and-live — Staging-to-live promotion workflow
/docs/platform/sg-admin/setup-wizard — Initial site setup walkthrough

SG-Builder (visual page composition)

The visual editor. Drag-and-drop with publish-ready output.

/docs/platform/sg-builder — Section landing
/docs/platform/sg-builder/component-library/ — Block catalog (basic, extra, posts, ecommerce blocks)
/docs/platform/sg-builder/breakpoints — Six standard responsive breakpoints (1920 / 1199 / 991 / 767 / 575 / 480)
/docs/platform/sg-builder/layer-manager — Component hierarchy and selection
/docs/platform/sg-builder/site-settings — Builder design system surface

Cross-cutting platform surfaces

Surfaces that span multiple product pillars.

/docs/platform/appearance — Theme administration (themes, theme editor, custom codes, custom CSS, custom fonts, shortcodes helper, menu, site settings)
/docs/platform/site-settings — Builder design system (global colors, typography, buttons, header, footer, layout, navigation)
/docs/platform/automations — Trigger-driven workflow logic
/docs/platform/integrations — External service connections (analytics, ads, mail providers)
/docs/platform/workflows — Cross-product process flows
/docs/platform/custom-codes — Direct authoring surface for site-wide HTML, CSS, JavaScript
/docs/platform/custom-css — Site-wide CSS authoring with scope rules
/docs/platform/custom-fonts — Self-hosted font registration and Google Fonts integration

Operations — practical operating surfaces

Operational surfaces span the platform pillars. Each one is a daily-driver view for a specific type of work.

Operations · 7 daily-driver surfaces
📁 /docs/operations/
├─ ecommerce/ — products · orders · coupons · configuration
├─ seo-performance — Core Web Vitals · schema · sitemap
├─ tools/ — search-replace · helpers
├─ migration-and-import/ — WordPress · Squarespace · CSV
├─ analytics — event logs · reports · top paths
├─ security — auth · sessions · blacklist · activity
└─ ux — mobile-first · accessibility · perf-UX

/docs/operations/ecommerce — Commerce operating surface
/docs/operations/ecommerce/products/ — Product catalog (catalog management, variants, inventory)
/docs/operations/ecommerce/orders/ — Order management (statuses, fulfillment, refunds)
/docs/operations/ecommerce/coupons/ — Discount coupons (codes, percentages, scope rules)
/docs/operations/ecommerce/configuration/ — Store configuration (payment, shipping, taxes)
/docs/operations/seo-performance — SEO and performance (Core Web Vitals, schema, crawlability)
/docs/operations/tools/ — Utility tools (search and replace, import-export helpers)
/docs/operations/migration-and-import/ — Data migration and import workflows
From WordPress (XML export, plugin equivalence map)
From Squarespace (page-by-page rebuild guide)
From a CSV (custom-objects import)
/docs/operations/analytics — Analytics landing (event logs, traffic reports, top paths)
/docs/operations/security — Security overview (auth, sessions, blacklist, activity log)
/docs/operations/ux — UX operating surface (mobile-first, accessibility, performance UX)

Architecture — platform position

The architectural reasoning behind the platform's shape. Read these for design rationale, not for feature how-to.

Architecture · 7 reasoning pages
📁 /docs/architecture/
├─ architecture — section landing
├─ zero-plugins — structural choice
├─ no-plugin-architecture — rationale
├─ updates-stability — release cadence + rollback
├─ performance-reliability — delivery model
├─ infrastructure-overview — managed posture
└─ codebase-overview — customization scope

/docs/architecture/architecture — Architecture & Reliability landing
/docs/architecture/zero-plugins — Zero plugin position (the structural choice)
/docs/architecture/no-plugin-architecture — Architectural rationale (what replaces the plugin extension model)
/docs/architecture/updates-stability — Change control model (release cadence, rollback paths)
/docs/architecture/performance-reliability — Delivery model (server-first speed, smart-loading, edge delivery)
/docs/architecture/infrastructure-overview — Infrastructure overview (managed platform, customer ownership)
/docs/architecture/codebase-overview — Codebase boundary map (what's in scope for customer customization)

Changes — release streams

Three streams, kept separate on purpose.

Changes · 3 streams kept separate on purpose

📋 Changelog

Released changes · append-only · dated · by area

🗺 Roadmap

Planned + in-progress · planned / active / shipped

📊 Status

Operational state · incidents · maintenance · resolutions

/docs/changes/changelog — Released changes (append-only, dated, by area)
/docs/changes/roadmap — Planned and in-progress work (state labels: planned, active, shipped)
/docs/changes/status — Current operational state (incidents, maintenance windows, recent resolutions)

What's New — editorial highlights

/docs/whats-new/ — Featured posts (launches, improvements, notable additions). Hand-curated; not every changelog entry appears here.

How-to articles

/docs/how-to/ — Published how-to articles for common operating tasks. Procedure-focused, step-led, with screenshots.

Production docs

/docs/production-docs/ — Production-ready articles with companion marketing email mappings. Used by the marketing team to align outbound copy with documented platform behavior.

Practical guides

/docs/practical-guides/ — How We Build Pages and other build process guides. Composer-and-builder oriented.

FAQ

/docs/faq/ — Frequently asked questions. Short answers, with cross-links into deeper documentation.

Reference (under construction)

/docs/reference/ — Structured per-feature reference. Currently scaffolded; deeper content pending.
Field-by-field enumeration of feature options.
Boundary behavior (what each value does, what edge cases apply).
Cross-references to the matching Guide page.

Quick lookup — surface to URL

A condensed lookup for common navigation needs.

Surface	URL prefix
Start Here	`/docs/start-here/`
Platform → SG-Core	`/docs/platform/sg-core/`
Platform → SG-Modules	`/docs/platform/sg-modules/`
Platform → SG-Dashboard	`/docs/platform/sg-dashboard/`
Platform → SG-Admin	`/docs/platform/sg-admin/`
Platform → SG-Builder	`/docs/platform/sg-builder/`
Operations	`/docs/operations/`
Architecture	`/docs/architecture/`
Changes → Changelog	`/docs/changes/changelog`
Changes → Roadmap	`/docs/changes/roadmap`
Changes → Status	`/docs/changes/status`
What's New	`/docs/whats-new/`
How-to	`/docs/how-to/`
FAQ	`/docs/faq/`
Reference (under construction)	`/docs/reference/`

Steps

To use this map effectively, work through it like this.

1. Read this page top to bottom once.

You'll have the shape of the docs in your head. The seven groups (Start Here, Platform, Operations, Architecture, Changes, What's New, supporting) become the mental scaffold.

2. Bookmark sections you'll return to.

Operators usually bookmark Site Manager, Stage & Live, Changelog, and Status. Designers bookmark SG-Builder Component Library and Site Settings. Marketers bookmark SEO and Live Analytics.

3. Use Search instead of re-navigating from this map.

Once you know the IA, search is faster. Use this map for orientation and discovery, not for routine navigation.

4. Come back to this map when a new section appears.

Major IA changes will be reflected here. Updates date-stamped at the top.

5. Send this URL to teammates onboarding.

This page is the canonical "see the full shape of the docs" surface. Linking it directly is faster than describing the IA.

What you'll find on each page type

A quick cheatsheet for what to expect:

Section landing — the group's overview. What's in the section. What relates to what. Read this before deep pages.
Feature page — how to use a specific feature. Steps, examples, troubleshooting, success criteria.
Reference page — exact field-by-field detail. Boundary behavior. Used when you need precision.
Changelog entry — dated, area-tagged, one-paragraph summary of a shipped change.
What's New post — editorial framing of a notable launch with summary and CTA.
Roadmap entry — planned work with state label (planned, active, shipped).
Status entry — incident, maintenance window, or recent resolution.

What success looks like

You're using the Documentation Map well when:

You can name the section a feature lives in without checking.
You stop re-navigating from the homepage and use direct URLs.
You catch yourself sending teammates direct links instead of "go to the docs."
You notice when a new section appears and update your mental model.
You guess URL paths correctly most of the time.
You stop bookmarking individual feature pages and start bookmarking section landings.

Reading time

This page is reference-heavy — most readers skim first, then return to detail. Approximate budgets:

First read — 10 minutes to get the full shape in your head.
Return visits — 1 to 2 minutes to look up a specific URL or section boundary.
Quarterly re-read — 5 minutes to catch IA changes from the last quarter.

What to do if it does not work

A page in the map doesn't open. The page may be a stub or pending. Try the section landing or open a support ticket.
A page exists but isn't on the map. Map updates lag occasionally. Use search if a page is missing here. Tell the team if it's a major surface that should be added.
The sidebar shows a different structure. The sidebar is canonical for live state. This map is the snapshot. Trust the sidebar when they conflict.
A URL in the map redirects somewhere else. The IA realigned in 2026-04-30. Old /guides/ and /docs/start/ URLs now redirect to /docs/start-here/* and matching canonical paths. Update bookmarks when redirects appear.
A surface you expected isn't in the map. Some surfaces are still being added as the platform expands. The IA review cadence is quarterly — large additions surface in the next review. Use search to confirm a surface exists in the live docs.
The map shows a different shape than the section landings. The map shows the full tree; section landings show the section's depth only. They should be consistent — if they conflict, the section landing usually has the more current state.

How the IA evolves

The Documentation Map updates on a regular cadence:

Per-release — newly shipped surfaces get added with their first feature page.
Quarterly — IA reviews. Section restructuring, group renames, IA realignments. Old URLs are mapped to new ones; redirects land before the change ships.
Per major surface launch — a new top-level group (e.g. Reference becoming generally available) gets its own subsection.

The map's overall shape is stable: Start Here, Platform, Operations, Architecture, Changes, What's New, supporting groups (How-to, FAQ, Reference). New surfaces fit into this shape rather than reshape it.

When IA changes break URLs

When the IA changes a URL path:

Old URLs redirect to new ones for at least one full release cycle.
Major changes are recorded in Changelog under the docs-meta area.
Bookmarked URLs get a 301 redirect rather than a 404.

If you hit a 404 on a URL you used to use, the IA likely changed and the redirect didn't catch. Tell the team through the page-level feedback affordance.