qumo-website/openspec/changes/step-003-navigation-bar/specs/content-i18n/spec.md

ADDED Requirements

Requirement: Locale content JSON files contain nav strings

src/content/en.json and src/content/nl.json SHALL each contain a top-level "nav" key with the following structure:

• links: array of objects with label: string and href: string for each nav link
• cta: string — label for the Connect CTA button
• ctaHref: string — href for the Connect CTA button
• langSwitch: object with en: string and nl: string labels for the language switcher

Scenario: en.json nav section has correct structure

• WHEN src/content/en.json is parsed as JSON
• THEN it SHALL have a nav object containing links (array of 3 items with label and href), cta string, ctaHref string, and langSwitch object with en and nl keys

Scenario: nl.json nav section has Dutch labels

• WHEN src/content/nl.json is parsed as JSON
• THEN nav.links SHALL contain Dutch labels ("Diensten", "AI Launchpad", "Over Ons"), nav.cta SHALL be "Verbind", and nav.ctaHref SHALL be "/nl/contact"

Scenario: Build succeeds with nav strings added

• WHEN npm run build is executed after adding nav keys to both JSON files
• THEN the build SHALL complete without TypeScript errors