Architecture Overview Is Now Available
SGEN's public architecture overview is now live in the docs. It explains the shared platform foundation, site-aware behavior, environment separation, and release flow in a single readable reference — written for stakeholders, product readers, and technical teams without exposing internal implementation detail.
What's now live
Legacy CMS architecture is often a black box of plugin layers — teams have to infer the system from behavior or trial and error. SGEN's scoped component system is documented end-to-end. The new overview page gives readers the full public platform model: what the shared foundation provides, how sites inherit and extend it, and how environments and releases are managed. The page is written to be useful at first read, not just as a reference to return to.
What the overview covers
Five areas of the platform model are introduced in reading order.
Foundation
Shared platform foundation
The core layer that all SGEN sites run on — the runtime, component system, and the services every site inherits by default.
Sites
Site-aware behavior
How each site's configuration, content, and customizations stay isolated while sharing the platform foundation below.
Environments
Environment separation
How staging and live environments relate — what is shared, what is scoped per environment, and where promotion happens.
Release
Release flow
How platform updates move from build through staging to production and what that means for sites built on top.
Where it fits
The architecture overview is the technical orientation layer for the docs. It is the right starting point for anyone evaluating the platform model, scoping a build, or onboarding to the system. All other technical reference in the docs assumes this model is understood — the overview makes that assumption safe to hold.
Read this first
Start with the architecture overview before reading component references, API docs, or environment configuration guides. It establishes the vocabulary and model everything else builds on.
Public scope, not internal
The overview covers the public platform model — the system as it appears to builders and operators. Internal implementation details are deliberately excluded so the doc is stable and shareable.
Heads up No setup required. The architecture overview is a documentation page, not a product feature — nothing in your account or site configuration changes. Open the link and read.