PG Facts Site Guide
Where navigation, layouts, tiles, and site settings are maintained.
Managing Pages
How to add pages and keep them aligned with the shared topic structure.
Rendering Content
How content is displayed as reusable cards on web pages.
Documentation Inventory
The database and DCMS pages below describe the current SQL project, seeded lookup data, supplied menu export, and proof-of-concept behavior. The SQL project is authoritative for schema definitions; the menu export and MenuItemList output provide the current menu examples.
| Topic | Current page | What it covers |
|---|---|---|
| Database schema | DCMS Database Schema | Tables, relationships, constraints, lookup rows, procedures, and representative menu data. |
| Main tables | Main Tables | Core relational domains and examples from the current menu snapshot. |
| Database purpose | Why a database | Why DCMS uses structured relational data and what remains to build. |
| Dynamic menus | Dynamic Menus | Runtime menu hierarchy, persona filtering, route links, and POC behavior. |
| Routing | Dynamic Routing | RouteTarget, document identity, placeholders, and current route handling. |
| Menu workflow | Menu Workflow | Master_Menu.csv import, staging, validation, publication, and rebuild limitations. |
| Dynamic content | Dynamic Content | ContentDocument and ContentElement, current content status, and future capabilities. |
| Content curation | Curating Content | Content model, migration path, review needs, and publication status. |
Older copies in the docs section point to the canonical pages so readers do not encounter conflicting schema and routing descriptions.