Routing and Rendering

Pipeline (Observed) 1. Frontend route matches based on site context (routes/web.php). 1. Controller loads models (e.g., MGPages, Locations) and dictionary content. 1. Content HTML is processed with App\Helpers\Placeholders::processContent(). 1. Controller sets SEO metadata via Theme and renders a Blade view.

Examples - Regional listing page: MintocomRegionalController::index returns mintocom.main.regional.overview.index-{category}. - Community main page: MintocomProjectController::index returns a project view using Locations data. - Minto Apartments project: MintoapartmentsProjectController::index uses the same pattern for rentals. - Search page: MintocomSearchController::index is routed from /search.html in routes/web/mintocom/core.php.

Content Source - HTML for pages comes from dictionary keys such as mgpage_content, ppage_content, and location_description*. - Page builder saves these fields via backend saveContent endpoints.

Placeholder Rendering - Placeholder templates live under resources/views/mintocom/placeholders/ and resources/views/mintoapartments/placeholders/. - GeneratePlaceholder creates structured HTML for placeholder tokens and reprocesses them through Placeholders.