Platform Overview
SGEN is a connected product system composed of distinct operating surfaces rather than a single interface. This page defines the platform at the highest level, clarifies how the major surfaces relate to one another, and establishes the reference structure used across the library.
Definition
SGEN is organized as a connected product system rather than a single interface. SG-Dashboard serves as the multi-site command layer, SG Admin serves as the site administration layer, and SG Builder serves as the visual editing environment. Cross-product workflows, automations, integrations, and migration tooling complete the operating model. :contentReference[oaicite:0]{index=0}
Purpose
This page defines the top-level SGEN product portfolio and provides the structural model for reading the rest of the Reference library. It establishes the major operating surfaces, clarifies responsibility boundaries, and maps the supporting system areas that connect the platform together.
Scope
This page covers the platform at a system level. It is a structural reference, not a task guide, walkthrough, or release note.
Platform Surfaces
The platform is structured around three primary product surfaces and several supporting reference areas. These surfaces are separate by responsibility but connected through shared concepts, workflows, automation, integrations, and migration-aware operations.
The multi-site operations and portfolio visibility layer. It provides account-level control, site provisioning entry, billing access, reporting entry points, integrations access, and operational visibility across connected sites.
The site administration layer for content, modules, commerce, tools, records, and configuration. It owns structured site-level administration and control surfaces that affect site behavior.
The visual editing and layout composition environment. It owns page structure, presentation-level editing, and visual composition within the active site context.
Defines the cross-platform rules, models, and operating concepts used across the wider SGEN stack.
Defines cross-product process flows and handoff logic between product surfaces and system states.
Defines background actions, scheduled processes, and system-driven behavior that extend beyond direct manual interaction.
Defines how third-party systems connect into SGEN, where their outputs appear, and what operational role they serve across the platform.
Defines import, backup, validation, recovery, and migration-sensitive operations within the platform.
Responsibility Model
The platform depends on clear boundaries between its major surfaces. Each area has a distinct operational role, and the system should be interpreted through those ownership boundaries rather than through isolated features alone.
Owns account-level and multi-site operational control, including provisioning entry, billing access, portfolio visibility, reporting entry points, and routing into site-specific work.
Owns site-specific administration such as records, settings, modules, configuration, and operational control panels that affect the active site.
Owns layout composition, visual editing, and page-level presentation assembly rather than structured administration or portfolio-level control.
Shared Concepts, Workflows, Automation, Integrations, and Migration and Import define the rules, behaviors, connections, and guarded operational models that support the primary product surfaces.
Reference Hierarchy
The Reference library is structured as a set of top-level sections with embedded subtrees. Expand each section to view its internal structure.
Platform Overview
Shared Concepts
SG-Dashboard
SG Admin
Appearance
SG Builder
Workflows
Automation
Integrations
Migration and Import
Reading Model
The Reference library should be read from system-level structure to surface-level definition, then into subtrees and page-level references.
Operational Role
Platform Overview acts as the system map for the Reference library. It is the page used to understand where each major product surface sits, what each area owns, how the supporting layers connect, and how the documentation hierarchy should be interpreted before moving into deeper section-level or module-level references.
Constraints And Boundaries
This page defines the platform model and documentation hierarchy at a system level. It does not replace detailed module references, task guides, internal engineering implementation documents, or release-specific communication.
Documentation Guidance
Use this page as a reference definition. It should remain stable, structural, and product-facing. Procedural instruction belongs in Guides, while shipped updates and release-specific changes belong in What’s New or Changelog. :contentReference[oaicite:1]{index=1}