Content Hierarchy

The CMS models three levels of content. The implementation uses database tables and Blade rendering rather than a formal domain schema object.

Observed Mapping - National level: websites (model App\Models\Websites), plus website pages in websites_pages (App\Models\WebsitesPages). - Regional level: CategoriesCities (market/category for a city), MGPages (regional pages), NewsPages (regional news). - Community level: Locations (projects/communities/properties) and PPages (project pages). Associated entities include Series, Units, Collections, Slideshows.

Hierarchy Diagram

erDiagram
    WEBSITES ||--o{ WEBSITES_PAGES : has
    CATEGORIESCITIES ||--o{ MGPAGES : has
    CATEGORIESCITIES ||--o{ NEWSPAGES : has
    CATEGORIESCITIES ||--o{ LOCATIONS : has
    LOCATIONS ||--o{ PPAGES : has
    LOCATIONS ||--o{ SERIES : has
    SERIES ||--o{ UNITS : has

Implemented - The hierarchy is visible in controllers and routes for each brand (routes/web/mintocom/*, routes/web/mintoapartments/*). - Models reference city/category fields and URL helpers (app/Models/MGPages.php, app/Models/Locations.php, app/Models/Legacy/RW.php).

Partially Implemented / Inferred - Cross-level inheritance (national to regional to community) is implied by shared templates and media, but not formalized in a single model. - Reusable content blocks exist (content_blocks) but retrieval for use across pages appears incomplete.