Core ERD
These diagrams show the core Capell database/model relationships. They are split so the relationship lines stay readable while still showing the real table links and polymorphic relationships.
Publishing And Routing
Section titled “Publishing And Routing”The publishing ERD covers URL resolution and localized content:
sitesownpages,site_domains, andpage_urls.site_domainsandpage_urlsare scoped bylanguages.page_urlstarget pageable records throughpageable_type/pageable_id.translationstarget translatable records throughtranslatable_type/translatable_id.redirect_health_snapshotsbelongs one-to-one withpage_urls.
Composition, Access, Assets, And Operations
Section titled “Composition, Access, Assets, And Operations”The composition ERD covers how pages are rendered and how cross-cutting records attach:
pages.layout_idreferenceslayouts.id.layouts.elementsstores element keys as a JSON-backed relationship to layout elements.- Layout elements own element assets.
widget_assets,asset_relations,media, andpage_role_restrictionsuse polymorphic relationships.content_graph_edgesstores derived source/target relationships.- Operational core tables track installed extensions, upgrade runs, and health alerts without owning content records.
Reading The Lines
Section titled “Reading The Lines”Solid lines represent normal database foreign key relationships. Dashed lines represent polymorphic or logical relationships. Dotted lines represent JSON-backed relationships. Orange dashed lines represent derived graph or operational relationships.
Cardinalities are shown near each line end. For example, the pages -> layouts relationship is many pages to one layout, while page_urls -> redirect_health_snapshots is one URL to zero or one health snapshot.