How to find any page in SGEN Docs

In short. SGEN Docs is organized into seven top-level groups: Start Here (orientation), Platform (five product pillars — SG-Core, SG-Modules, SG-Dashboard, SG-Admin, SG-Builder), Operations (daily-driver surfaces like ecommerce, analytics, security), Architecture (reasoning pages), Changes (Changelog, Roadmap, Status), What's New, and supporting sections (How-to, FAQ, Reference). Every URL starts with /docs/. If you can't find a page, use search — then come back here to understand which group it lives in.

That's the gist — everything below is the same idea in depth.

On this page: Start Here · Platform · Operations · Architecture · Changes · Reading paths · Surface lookup

This is the master navigation surface. The left sidebar shows only the active section; search returns matches but not structure. This page shows the complete shape at a glance — bookmark it for orienting teammates or confirming where a surface lives.

A few notes before the map:

• URLs below start with /docs/. The full form is https://docs.sgen.com/docs/ — the host is omitted throughout.
• The sidebar is canonical for live structure. This map is updated regularly but may lag a release.
• The Reference group is scaffolded — pages exist as stubs while deeper content fills in. Use the Guides group for full how-to docs in the meantime.

The full map

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)

Platform — the product surfaces

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

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.

• /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.

• /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.

• /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.

Suggested reading paths

Different roles need different paths. Pick the one that matches you.

New to SGEN

1. Welcome → What is SGEN → Why SGEN Exists → How This Documentation Works → this page
2. Then open whichever section landing matches your role.

Operator running multiple sites

1. SG-Dashboard overview → Site Manager → Stage & Live → Analytics → Billing
2. Then bookmark Changelog and Status for daily reference.

Operator running one site

1. SG-Admin overview → Dashboard → Publishing → Backups
2. Open SG-Core for content structure when needed.

Content editor

1. SG-Core overview → Pages & Posts → Media Library → Templates → Custom Objects
2. Open SG-Builder when composing layouts.

Designer / page builder

1. SG-Builder overview → Builder Workspace → Component Library → Layer Manager → Site Settings (typography, colors)
2. Open Templates when reusing layouts.

Developer / integrator

1. What is SGEN → Why SGEN Exists → Architecture → Zero Plugins → Architecture → No-Plugin Architecture
2. Then open /docs/reference/ for structured detail (under construction) or the relevant feature page.

Marketer running multiple campaigns

1. SG-Modules → SEO → SG-Modules → Forms → SG-Modules → Attributions
2. Then SG-Dashboard → Live Analytics for cross-site reporting.
3. Bookmark What's New and Changelog for what's shipped that affects campaigns.

Procurement or compliance reviewer

1. What is SGEN for the platform definition.
2. Architecture → Infrastructure Overview for the operational posture.
3. SG-Modules → Tracking Consent for GDPR consent overlay.
4. Operations → Security for the security overview.

Customer support engineer (for an internal SGEN team)

1. Internal runbooks under 03-Support-Runbooks/ (private, behind authentication).
2. Status for current operational state.
3. Activity Log documentation under SG-Admin.

Quick lookup — surface to URL

A condensed lookup for common navigation needs.

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.

How the IA evolves

The map's overall shape is stable: Start Here, Platform, Operations, Architecture, Changes, What's New, supporting groups. New surfaces slot into existing groups rather than reshape the tree.

Update cadence:

• Per-release — newly shipped surfaces added with their first feature page.
• Quarterly — IA reviews: group renames, restructuring, realignments. Redirects land before any change ships.
• Per major launch — a new top-level group (e.g. Reference going GA) gets its own subsection.

If a URL breaks: old paths redirect for at least one full release cycle. Major changes are logged in Changelog under the docs-meta area. If you hit a 404 on a URL that used to work, the IA realigned and the redirect didn't catch — use the page-level feedback affordance to flag it.

Related reading

• What is SGEN — platform definition and the five surfaces.
• Why SGEN Exists — operational rationale.
• How This Documentation Works — content classes and reading model.
• Platform overview — the five product surfaces in depth.
• For your role — tailored start paths by role.