{{# Default page template — Replicator-based page builder with legacy fallback. PRECEDENCE: page_sections (Replicator) wins over page_template (legacy). Several pages (notably the five solutions pages) have BOTH populated: - page_sections: the CP-editable content, what visitors actually see. - page_template: hotel_automation / hostel_automation / etc. — a hand-coded view kept as a safety net so the page still renders if someone wipes the Replicator data. Treat the bespoke template as a mirror of the Replicator output; any content change should be made via the CP (Replicator), and the bespoke template should be edited in sync only for the fallback path. The third branch below is used by pages that have neither page_sections nor a non-default page_template — the Bard `content` field is rendered inside a standard hero + prose layout. #}} {{# 1. If page_sections has content → render hero + Replicator sections #}} {{ if page_sections }} {{ if hero_title && page_template != 'home' }} {{ partial:partials/sections/hero }} {{ /if }} {{ page_sections }} {{ partial src="partials/sections/_{type}" }} {{ /page_sections }} {{# 2. Legacy fallback — render old template partials (which include their own hero) #}} {{ elseif page_template && page_template != 'default' }} {{ partial:pages/{page_template} }} {{# 3. Fallback — render Bard content field #}} {{ else }} {{ partial:partials/sections/hero }}
{{ if title && !hero_title }}

{{ title }}

{{ /if }}
{{ content }}
{{ /if }}