Marketing Website Architecture

Purpose

apps/site is the public face of RCS. It communicates product value, drives demand-generation activities, and remains intentionally static for operational safety. Marketing content is tracked internally even though the surface itself is public.

Information Architecture

• Homepage — Value proposition, proof points, singular call to action.
• Product — Feature matrix, implementation assurances, technical depth available on demand.
• Solutions — Tailored narratives by industry or persona; re-use shared components.
• Resources — Blog (phase two), case studies, press releases, downloadable assets.
• Company — About, leadership, careers, contact, compliance statements.
• Legal & Ethics — Terms, privacy, future AI/ethics portal (served by a future public docs app).

Content Model

Content Type	Authoring Source	Notes
Pages	MDX under apps/site/src/pages	Prefer filesystem routing, keep layouts composable.
Case Studies	Structured data modules	Include metrics, testimonials, CTA metadata.
Blog Articles (future)	MDX with frontmatter	Frontmatter: title, summary, publishDate, tags.
Navigation	Central config module	Unit tests ensure all critical URLs resolve.

Release Checklist

1. Update relevant content pages and run pnpm lint (future) locally.
2. Verify Lighthouse performance locally (target 90+/90+/90+).
3. Confirm security headers in staging using curl or Mozilla Observatory.
4. Ensure ADR-0004 remains satisfied—no unintended dependency drift.
5. Publish via Cloudflare Pages preview; secure sign-off from marketing and security before promoting to production.

Security Posture

• No PII, credentials, or secrets in the marketing source—ever.
• Enforce CSP, HSTS, X-Content-Type-Options: nosniff, Referrer-Policy: strict-origin-when-cross-origin, and a defensive Permissions-Policy.
• Analytics tooling is undecided; default to NO_DATA until leadership approves a vendor.

Next Steps

• Build design token library once component set stabilises.
• Establish editorial calendar for future blog and case-study work.
• Coordinate with security to automate header validation once CI/CD is introduced.