@port60/template-kit 1.0.0 → 1.2.0

package/README.md

@@ -50,11 +50,53 @@ See the [AI quickstart](https://developers.port60.com/guides/ai-quickstart/).
 
 ## The contract
 
-Kit 1.0.0 authors **port60-liquid@2**, content model **2.0**, using the contract under
+Kit 1.2.0 authors **port60-liquid@2**, content model **2.0**, using the contract under
 `src/vendor/contract/v2`. Collection envelopes, independent header/footer navigation,
 resolved actions and page-scoped sections are explicit. V1 sources need a deliberate migration,
 not a manifest-only relabel. Historical v1 contracts remain frozen for existing platform pins.
 
+### Optional editor controls in 1.2.0
+
+The editor only offers controls supported by the exact selected template version. Declare
+and implement these capabilities together; the validator checks the rendered result:
+
+- `supports.sectionHeadingAlignment`: supported section types and logical `start`, `center`
+  and `end` values. Put `data-p60-heading-align="{{ section.headingAlignment }}"` on the real
+  heading/eyebrow group. Move only that group within existing readable-width containers and
+  gutters at desktop widths of 1024px and above; preserve default and mobile layouts.
+- `supports.navigationModes`: explicit Simple/Mega options and a default, with
+  `data-p60-navigation-mode="{{ site.nav.headerMode }}"` on the real header menu. Both modes
+  preserve the supplied menu tree and destinations. Do not infer support from highlights.
+- `supports.sectionCollectionLinkVisibility`: sections whose existing onward collection link
+  has `data-p60-collection-link`. Keep that anchor in the DOM and add `hidden` only when
+  `section.showCollectionLink == false`, so the editor can reveal it without a page reload.
+- `supports.heroImageLimit`: an integer from 1 to 6 alongside `supports.heroImagery: true`.
+  The limit must reflect actual rendering, not just a carousel declaration. Missing means
+  one photograph; no imagery support means none. Stored photographs are never truncated.
+  Hidden markup and unrelated CSS URL text cannot prove multi-photo capacity.
+
+The compatible host must be deployed before these templates are published. Controls without
+declared support remain unavailable, and older pinned versions keep their existing behaviour.
+The visitor language switch remains dormant pending a separate multilingual-content flow;
+organisation language, RTL/LTR support and interface translation remain available.
+Generated AGENTS.md and CLAUDE.md contain the detailed authoring contract and validation loop.
+
+### Added in 1.1.0
+
+The v2 dialect adds `t` and `local_date`, matching the compatible platform host. Use
+`t: site.locale.code` only for supported interface phrases, not tenant-authored content.
+The initial phrase catalogue is Arabic; unknown phrases or languages preserve the supplied
+text. `local_date` formats English, Welsh or Arabic Gregorian dates in UTC with fixed
+`date` and `datetime` styles. It does not convert the tenant's prayer wall-clock times.
+
+Schedule rows can carry stable `key` values for prayer icons, independently of their supplied
+display names. Shared mobile island styling also uses logical offsets for both directions.
+Historical v1 filters and contracts are unchanged. These additions do not imply complete
+Arabic live-island, typography or legal-copy support.
+
+Deploy the compatible host before uploading templates that use the new filters. Kit 1.0.0
+will correctly reject them. See the [localisation guide](https://developers.port60.com/guides/localisation/).
+
 ## Designer previews
 
 The scaffold creates `preview/config.json` and `preview/media/`. Optional `content` points to

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@port60/template-kit",
-  "version": "1.0.0",
+  "version": "1.2.0",
   "description": "Build Port60 site templates locally: scaffold, live-preview, validate against the platform contract, and package for studio upload. AI-agent ready: every scaffold ships AGENTS.md and validate emits machine-readable JSON.",
   "type": "module",
   "bin": {

package/src/commands/create.mjs

@@ -60,7 +60,7 @@ export function create(args) {
   }, null, 2) + '\n');
   writeFileSync(join(target, 'README.md'), `# ${label}
 
-A Port60 site template using \`port60-liquid@2\`, content model \`2.0\` and kit \`1.0.0\`.
+A Port60 site template using \`port60-liquid@2\`, content model \`2.0\` and kit \`${KIT_PACKAGE.version}\`.
 Existing v1 platform pins keep historical support; this kit accepts v2 authoring only.
 Start with \`npm install\`, then:
 

package/src/lib/agentsMd.mjs

@@ -1,3 +1,7 @@
+import { readFileSync } from 'node:fs';
+
+const KIT_VERSION = JSON.parse(readFileSync(new URL('../../package.json', import.meta.url), 'utf8')).version;
+
 // A contract briefing shared by every generated coding-agent instruction file.
 export function agentsMd(name) {
   return `# Working on the "${name}" Port60 template
@@ -8,7 +12,7 @@ identity, authored content and inline editing markers while changing presentatio
 
 ## Versions and iteration
 
-Use format port60-liquid@2, content model2.0 and kit1.0.0. Existing v1 platform pins retain
+Use format port60-liquid@2, content model 2.0 and kit ${KIT_VERSION}. Existing v1 platform pins retain
 their historical contract; this kit explicitly rejects v1 for new authoring and uploads.
 Never relabel v1 without migrating its reads. Published name/version identities are immutable.
 
@@ -68,6 +72,30 @@ Use nil checks, not Liquid default, wherever clearing has meaning. Keep generate
 of raw section content. Mark an authored title only in the nonempty override branch. An inherited
 heading has no data-p60-field marker.
 
+Heading alignment is an optional per-section capability, not a global theme setting. Declare
+supports.sectionHeadingAlignment as a map, for example {"services":["start","center","end"]}.
+Each key must also be in supports.sections; list only the nonempty, unique subset you implement.
+Place data-p60-heading-align="{{ section.headingAlignment }}" on the actual h1 to h6 heading,
+its eyebrow, or a wrapper containing only that heading and eyebrow. The heading itself must be
+inside/on a matching hook; do not mark the whole section, cards, media, body copy or actions.
+Omit section.headingAlignment for the template's authored default. Never use a Liquid default
+filter or a hardcoded active hook value: absent/unsupported values must leave the design alone.
+Keep the empty hook on every visible heading at the default too, so the first editor choice
+can update immediately. Only omit the heading and its hook together when that copy is hidden.
+The platform applies start/center/end text alignment only at desktop widths (1024px and above).
+Template CSS may position only the heading group within its existing template-owned content
+container and gutters. Preserve its readable width; never widen it to the viewport, remove the
+gutters or move the whole hero copy block. A full-bleed image can stay full bleed independently.
+Introductions, body copy, buttons, cards, images and donation widgets keep their placement and
+alignment. Scope local group-placement rules to that template's heading hook, explicit active
+values and the same desktop breakpoint; do not introduce global margins or a new layout setting.
+Default and mobile keep the template layout. Start/end follow text direction, including RTL.
+Keep field markers and text unchanged; validate every advertised value and visually check every
+Look. Prove visible heading alignment and bounded group placement with readable width retained,
+unchanged surrounding content, reset and mobile; computed text-align alone is not visual proof.
+This capability needs a coordinated host/kit release; keep existing published dependency pins
+until that supporting kit version is available.
+
 Declare supports.fieldMarkers:true when showing authored field markers. A marker such as
 data-p60-field="title" or data-p60-field="items.{{ forloop.index0 }}.label" addresses only that
 section's content. Its node must contain exactly the authored value. Use a span when punctuation
@@ -75,6 +103,13 @@ or generated text surrounds it. Never mark source records, generated labels or r
 
 ## Navigation and actions
 
+Optional supports.navigationModes is {options:["simple","mega"],default:"mega"} (either supported
+mode may be the default). It requires supports.layout and both working presentations. Mark the
+header navigation root data-p60-navigation-mode="{{ site.nav.headerMode }}". The host resolves the
+saved choice or declared default; missing capability keeps the historical layout. Do not infer
+support from navigationHighlights. Both modes retain supplied destinations, node order and saved
+metadata. Scope mode CSS to that marker and verify mobile, keyboard and no-JavaScript navigation.
+
 site.nav.header and site.nav.footer are independent arrays. kind link has href; kind group has
 null href and children. Use disclosure controls for groups, not fake links. Render two child
 levels and preserve description, imageUrl and optional megaMenu.promo. No derived menus, CTA
@@ -85,6 +120,14 @@ site.actions.header and site.actions.hero are resolved actions or null. site.act
 donate, volunteer or none. Do not infer actions from navigation. Authored hero override text
 retains its field marker; resolved fallback actions do not.
 
+Optional supports.sectionCollectionLinkVisibility lists supported collection section types with
+an existing onward link. Mark only that anchor data-p60-collection-link, keep its supplied href
+and existing label, and add hidden only when section.showCollectionLink == false. Missing/true
+keeps the default link. Keep the hidden anchor for immediate editor updates; omit it only when
+there is no supplied destination. Do not hide headings, cards or individual record links, invent
+URLs, or add text/position controls. Unsupported saved preferences are retained but not rendered.
+Both presentation capabilities need a coordinated host/kit release, not a speculative registry pin.
+
 ## Safety and design
 
 - Output is escaped. Use raw only for contract-sanitised richtext.
@@ -97,7 +140,21 @@ retains its field marker; resolved fallback actions do not.
 - Declare only what you render, and render what you declare. Capability matching is metadata,
   not a transfer of route ownership or tenant entitlements.
 - Hero photos need a palette scrim, a carousel for multiple photos and a designed no-photo state.
+  Declare supports.heroImagery:true plus supports.heroImageLimit as an integer from 1 to 6
+  matching the homeHero's actual capacity. Missing limit means one photograph; no hero imagery
+  means zero. A limit above one must render every distinct photograph in a fixture of that
+  size or place the hero_carousel island. A generic carousel declaration is not proof.
+  The editor reads the exact selected template version, never the catalogue's latest version.
+  Saved photographs are never truncated on template switches. Publish a new immutable version
+  with this declaration only after the matching host and kit release; preserve existing pins.
 - Preserve settings and Looks. Use platform fonts and declared CSS tokens.
+- The host owns lang/dir and Arabic fonts. Use logical CSS properties. Read site.locale.code.
+- Do not add a visitor language selector. site.locale.languages is currently empty and the
+  legacy language_switch slot renders nothing. Interface catalogues are not translated tenant content.
+- The next coordinated kit release adds t for supported interface phrases and local_date for
+  fixed Gregorian date/datetime formatting in UTC. Do not use these on registry kit 1.0.0.
+  Never translate authored text, infer prayer identities from translated names or convert
+  supplied prayer wall-clock strings. Details: /guides/localisation/ in the developer docs.
 - Scope behaviour-dependent hidden content under .p60-js so no-JavaScript stays readable.
 - Keep loops bounded. Test empty collections, cleared text and unknown enum values.
 

package/src/vendor/contract/v2/content-model.json

@@ -746,7 +746,7 @@
       "since": "2.0",
       "cap": 4,
       "moreHref": null,
-      "description": "TYPE-DERIVED recurring schedules. `type` is an OPEN enum; 'worship' is the first (its shape is the layout worship contract: times, labels, today, next). Other institutions arrive as new types; render the types you know, ignore the rest.",
+      "description": "TYPE-DERIVED recurring schedules. `type` is an OPEN enum; 'worship' is the first (times, labels, today, next, jumah). Mosque daily times and next may carry a stable `key`: fajr, zuhr, asr, maghrib or isha. Use key for icons, never replace the supplied name. Missing/unknown keys remain readable without an icon. Friday rows are `jumah`, not `jumuah`. Other institutions arrive as new types; render the types you know, ignore the rest.",
       "item": {
         "type": {
           "type": "string",

package/src/vendor/contract/v2/dialect.json

@@ -88,7 +88,9 @@
     "upcase",
     "url_decode",
     "url_encode",
-    "where"
+    "where",
+    "t",
+    "local_date"
   ],
   "excluded": {
     "tags": [

package/src/vendor/contract/v2/islands.json

@@ -140,7 +140,7 @@
       "name": "language_switch",
       "label": "Language switch",
       "status": "available",
-      "description": "Switches between the platform's supported public languages while preserving the current route. The host supplies locale and text direction to Liquid and the document element.",
+      "description": "Temporarily inactive: currently renders nothing. Localisation supports a site's language and text direction; translated tenant content and an explicit per-site language choice need a separate opt-in design. The host supplies locale and direction independently. Do not add a replacement visitor selector.",
       "params": [],
       "stylingApi": [
         ".language-switch",

package/src/vendor/contract/v2/manifest.schema.json

@@ -91,6 +91,12 @@
         "pages",
         "sections"
       ],
+      "dependentSchemas": {
+        "heroImageLimit": {
+          "required": ["heroImagery"],
+          "properties": { "heroImagery": { "const": true } }
+        }
+      },
       "properties": {
         "pages": {
           "type": "array",
@@ -151,6 +157,30 @@
           "default": false,
           "description": "True when the layout renders the `worship` context (the prayer/service-times rail). Declared honesty: the choosers badge worship-enabled tenants toward looks that show their times, and warn on looks that don't. Requires supports.layout; the layout must actually branch on `worship`."
         },
+        "navigationModes": {
+          "type": "object",
+          "additionalProperties": false,
+          "required": ["options", "default"],
+          "properties": {
+            "options": {
+              "type": "array",
+              "minItems": 2,
+              "maxItems": 2,
+              "uniqueItems": true,
+              "items": { "enum": ["simple", "mega"] }
+            },
+            "default": { "enum": ["simple", "mega"] }
+          },
+          "description": "Explicit header presentation switch for this exact layout. Both simple and mega must be implemented without changing saved navigation nodes, destinations or metadata. Requires supports.layout. The host resolves an accepted saved menus.headerMode or this default into site.nav.headerMode. Mark the navigation root data-p60-navigation-mode with that resolved mode. Missing support preserves the historical layout and leaves saved preferences unused, never inferred from navigationHighlights."
+        },
+        "sectionCollectionLinkVisibility": {
+          "type": "array",
+          "minItems": 1,
+          "maxItems": 7,
+          "uniqueItems": true,
+          "items": { "enum": ["events", "articles", "courses", "campaigns", "services", "documents", "appealGrid"] },
+          "description": "Supported collection section types whose existing onward link may be hidden. Every entry must also be in supports.sections and render its supplied collection destination on a permanent data-p60-collection-link anchor. Only section.showCollectionLink == false adds hidden; absent or true retains the template default link. Keep its shared label and destination unchanged, and never hide the heading, records, cards or individual record links. No new URLs, text override or positioning control."
+        },
         "navigationHighlights": {
           "type": "boolean",
           "default": false,
@@ -162,11 +192,30 @@
           "description": "True when the sections mark which node shows which field with data-p60-field, so the editor can put the caret on the page instead of in a side panel. The address is inside that section's own content: data-p60-field=\"title\", or data-p60-field=\"items.{{ forloop.index0 }}.label\" for an entry in a list. Purely additive: the attribute is markup, the contract is untouched, and a template that marks nothing keeps the section-level editor. The validator reads the marks from the source and warns on any that does not name a field of that section. Missing or false leaves this exact template version editing in the panel.",
           "$comment": "Follows the navigationHighlights pattern: declared honesty, proven by the validator."
         },
+        "sectionHeadingAlignment": {
+          "type": "object",
+          "maxProperties": 16,
+          "propertyNames": { "enum": ["hero", "values", "cta", "homeHero", "impact", "events", "articles", "campaigns", "emergency", "stats", "appealGrid", "services", "documents", "people", "impactMap", "courses"] },
+          "additionalProperties": {
+            "type": "array",
+            "minItems": 1,
+            "maxItems": 3,
+            "uniqueItems": true,
+            "items": { "enum": ["start", "center", "end"] }
+          },
+          "description": "Explicit opt-in per supported section type to desktop heading alignment choices. Missing entries disable the editor control. The host projects section.headingAlignment only for declared options. Mark heading/eyebrow elements using data-p60-heading-align with that value. The shared base applies text-align at widths of at least 1024 CSS pixels; absent/empty hooks retain the template default at every width. The validator proves each declared option renders on real headings and cannot change unrelated content. No layout positioning is implied."
+        },
         "heroImagery": {
           "type": "boolean",
           "default": false,
           "description": "True when the homeHero renderer displays the tenant's hero photographs (homeHero.images, legacy imageUrl), always under a TREATMENT built from the template's own palette variables (scrim/tint/blend), never raw. Declared honesty, proven behaviourally at validation: the choosers badge photo-led tenants toward templates that show their images and warn on ones that won't. Requires the homeHero section among supports.sections."
         },
+        "heroImageLimit": {
+          "type": "integer",
+          "minimum": 1,
+          "maximum": 6,
+          "description": "Maximum homeHero photographs this exact template version can present. Requires supports.heroImagery: true. Missing means one; no hero imagery means zero. Values above one require rendering every image in a fixture of the declared size or placing the hero_carousel island. Generic carousel behavior or island declarations alone do not opt in. This gates editor additions, never truncates saved photographs or changes an older artifact's rendering."
+        },
         "behaviors": {
           "type": "array",
           "items": {

package/src/vendor/contract/v2/sections.json

@@ -9,6 +9,17 @@
       ],
       "description": "The page opener: a headline with an optional kicker and sanitised rich-text intro.",
       "fields": [
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "eyebrow",
           "kind": "text",
@@ -45,6 +56,17 @@
       ],
       "description": "A set of principles shown as cards or a numbered list, per the template.",
       "fields": [
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "eyebrow",
           "kind": "text",
@@ -120,6 +142,17 @@
       ],
       "description": "A closing band: heading, optional line, one button.",
       "fields": [
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "heading",
           "kind": "text",
@@ -165,6 +198,17 @@
       ],
       "description": "The home opener. EVERY field optional: eyebrow/title derive from branding when absent, the lead OMITS when absent (never a fabricated placeholder), buttons fall back to platform defaults.",
       "fields": [
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "eyebrow",
           "kind": "text",
@@ -227,7 +271,7 @@
           "name": "images",
           "kind": "items",
           "required": false,
-          "description": "Hero photographs (0-6, uploaded through the platform pipeline). One = a main image; several = rotation material, a template with supports.heroImagery renders at least the first and MAY place the hero_carousel island (or a CSS scroll strip) for the rest. Like every field: absent means the template's designed no-photo state, never a placeholder.",
+          "description": "Hero photographs (0-6, uploaded through the platform pipeline). One = a main image; several = rotation material. A template with supports.heroImagery renders at least the first and may place the hero_carousel island (or a CSS scroll strip) for the rest. Declare supports.heroImageLimit above one to offer multiple photographs in the editor; missing means one, and absent heroImagery means zero. Saved photographs survive template switches and are never truncated by this capability. Like every field: absent means the template's designed no-photo state, never a placeholder.",
           "itemFields": [
             {
               "name": "imageUrl",
@@ -295,6 +339,17 @@
       ],
       "description": "What gifts make possible, optional intro plus icon/title/description cards. Claims must be truthful for the tenant.",
       "fields": [
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "eyebrow",
           "kind": "text",
@@ -384,6 +439,23 @@
       "kind": "widget",
       "description": "Published events across registration modes. Render the supplied bounded site.content.events.items with this placement's authored introduction. Optional motion uses declared behaviours; ticket sales and RSVP stay on the platform-owned detail route supplied by each item.",
       "fields": [
+        {
+          "name": "showCollectionLink",
+          "kind": "boolean",
+          "required": false,
+          "description": "Only false hides this placement's existing onward collection link. Missing or true keeps the template default. Requires this exact template to declare supports.sectionCollectionLinkVisibility for this section. Keep a stable data-p60-collection-link anchor and add hidden only for false. The platform-supplied URL and shared label stay unchanged; headings, records and individual card links are unaffected."
+        },
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "eyebrow",
           "kind": "text",
@@ -422,6 +494,23 @@
       "kind": "widget",
       "description": "Published articles from the supplied bounded site.content.articles.items. Render the records with this placement's authored introduction and link through the supplied item URLs. Article engagement and comments remain platform islands on the detail page.",
       "fields": [
+        {
+          "name": "showCollectionLink",
+          "kind": "boolean",
+          "required": false,
+          "description": "Only false hides this placement's existing onward collection link. Missing or true keeps the template default. Requires this exact template to declare supports.sectionCollectionLinkVisibility for this section. Keep a stable data-p60-collection-link anchor and add hidden only for false. The platform-supplied URL and shared label stay unchanged; headings, records and individual card links are unaffected."
+        },
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "eyebrow",
           "kind": "text",
@@ -463,6 +552,23 @@
         "campaignsLabel"
       ],
       "fields": [
+        {
+          "name": "showCollectionLink",
+          "kind": "boolean",
+          "required": false,
+          "description": "Only false hides this placement's existing onward collection link. Missing or true keeps the template default. Requires this exact template to declare supports.sectionCollectionLinkVisibility for this section. Keep a stable data-p60-collection-link anchor and add hidden only for false. The platform-supplied URL and shared label stay unchanged; headings, records and individual card links are unaffected."
+        },
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "eyebrow",
           "kind": "text",
@@ -500,6 +606,17 @@
         "causes"
       ],
       "fields": [
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "heading",
           "kind": "text",
@@ -543,6 +660,17 @@
       ],
       "description": "Big headline numbers, the at-a-glance impact band. Values are author-entered text (write them exactly as they should read), or, per item, a live figure the platform counts (`source`).",
       "fields": [
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "eyebrow",
           "kind": "text",
@@ -626,6 +754,23 @@
         "causes"
       ],
       "fields": [
+        {
+          "name": "showCollectionLink",
+          "kind": "boolean",
+          "required": false,
+          "description": "Only false hides this placement's existing onward collection link. Missing or true keeps the template default. Requires this exact template to declare supports.sectionCollectionLinkVisibility for this section. Keep a stable data-p60-collection-link anchor and add hidden only for false. The platform-supplied URL and shared label stay unchanged; headings, records and individual card links are unaffected."
+        },
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "eyebrow",
           "kind": "text",
@@ -715,6 +860,23 @@
         "services"
       ],
       "fields": [
+        {
+          "name": "showCollectionLink",
+          "kind": "boolean",
+          "required": false,
+          "description": "Only false hides this placement's existing onward collection link. Missing or true keeps the template default. Requires this exact template to declare supports.sectionCollectionLinkVisibility for this section. Keep a stable data-p60-collection-link anchor and add hidden only for false. The platform-supplied URL and shared label stay unchanged; headings, records and individual card links are unaffected."
+        },
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "eyebrow",
           "kind": "text",
@@ -752,6 +914,23 @@
         "resources"
       ],
       "fields": [
+        {
+          "name": "showCollectionLink",
+          "kind": "boolean",
+          "required": false,
+          "description": "Only false hides this placement's existing onward collection link. Missing or true keeps the template default. Requires this exact template to declare supports.sectionCollectionLinkVisibility for this section. Keep a stable data-p60-collection-link anchor and add hidden only for false. The platform-supplied URL and shared label stay unchanged; headings, records and individual card links are unaffected."
+        },
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "eyebrow",
           "kind": "text",
@@ -786,6 +965,17 @@
       ],
       "description": "The key people behind the charity, trustees, staff, volunteers, as simple cards: name, position, an optional photograph (uploaded through the platform pipeline) and an optional one-line statement. Templates render a card grid that collapses to a single column on small screens; a card without a photo renders cleanly (initials or plain), never a placeholder face.",
       "fields": [
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "eyebrow",
           "kind": "text",
@@ -878,6 +1068,17 @@
       "description": "The organisation's impact map: a themed map whose points link existing content (campaigns, causes, articles, events, places), each opening a card derived from the linked thing. Place the `map` island, it brings the map, the points and the cards; your template brings placement and tokens (the island theming contract).",
       "context": [],
       "fields": [
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "eyebrow",
           "kind": "text",
@@ -917,6 +1118,23 @@
         "home"
       ],
       "fields": [
+        {
+          "name": "showCollectionLink",
+          "kind": "boolean",
+          "required": false,
+          "description": "Only false hides this placement's existing onward collection link. Missing or true keeps the template default. Requires this exact template to declare supports.sectionCollectionLinkVisibility for this section. Keep a stable data-p60-collection-link anchor and add hidden only for false. The platform-supplied URL and shared label stay unchanged; headings, records and individual card links are unaffected."
+        },
+        {
+          "name": "headingAlignment",
+          "kind": "select",
+          "required": false,
+          "options": [
+            "start",
+            "center",
+            "end"
+          ],
+          "description": "Desktop alignment of the heading and optional eyebrow. The template may position their heading-only group within its existing content container and gutters while preserving readable width. Only applied when this exact template declares supports.sectionHeadingAlignment for this section and option. Absent means template default. Start/end follow the site direction. Below 1024 CSS pixels the template retains its own layout. Introductions, body copy, buttons, cards, images and islands keep their placement and alignment; full-bleed imagery does not widen the heading bounds."
+        },
         {
           "name": "eyebrow",
           "kind": "text",

package/src/vendor/contract/v2/site.schema.json

@@ -52,6 +52,10 @@
         "footer"
       ],
       "properties": {
+        "headerMode": {
+          "enum": ["simple", "mega"],
+          "description": "Resolved header presentation only when the exact template declares navigationModes. The host uses the accepted saved preference or the declared default. Omitted for unsupported templates; never inferred from menu shape or highlights."
+        },
         "header": {
           "type": "array",
           "items": {