# Form & Phase — Content and route map

Published site map · v0.5 · 17 September 2026

The studio has 16 pages at https://formandphase.studio. The routes below retain their local review prefix: remove `/studio` for the corresponding production route (for example, `/studio/expertise/` becomes `https://formandphase.studio/expertise/`). The Studio navigation item opens `/about/` in production.

Basis is at https://basis.formandphase.studio, with working components at `/lab/`. Studio links to Basis open a new tab; Basis includes a persistent return to Form & Phase. Local review uses the guide at `/`, studio at `/studio/`, and lab at `/system-lab/`.

## Main navigation

Expertise · Approach · Design systems · Work · Studio · Let’s talk

Every item opens a page. None targets a hash or a section on another page. Section links are confined to page indexes, contextual deep links, and the homepage scroll cue. The shared route manifest is `src/site-map.js`.

## Page inventory

| Destination | Preview route | What the page contributes |
|---|---|---|
| Home | `/studio/` | Broad promise, connected expertise, starting points, quality, design systems, method, compact work, studio, invitation |
| Expertise | `/studio/expertise/` | Three client situations and all six disciplines |
| Product strategy & discovery | `/studio/expertise/strategy/` | Product definition, assumptions, scope, web/mobile strategy, delivery plan |
| Experience design | `/studio/expertise/experience-design/` | Research, IA, UX/UI, content, responsiveness, complete interaction states |
| Application engineering | `/studio/expertise/application-engineering/` | Web/mobile build, architecture, stack, application boundaries, data strategy |
| Platforms & integrations | `/studio/expertise/platforms-integrations/` | APIs, integrations, e-commerce, payment/order state, cloud, automation |
| Launch & evolution | `/studio/expertise/launch-evolution/` | SDLC, QA, deployments, data migration, rollout/recovery, operations, maintenance |
| Design systems | `/studio/design-systems/` | Style foundations, semantic tokens, components and patterns, design/code alignment, documentation, adoption |
| Approach | `/studio/approach/` | Six connected delivery stages, collaboration, scope, handover, engagement questions |
| Quality & care | `/studio/approach/quality/` | Accessibility, security, architecture, performance, data care, testing, operations |
| Work | `/studio/work/` | Contained studio-project entry and an explanation of the evidence inside a case study |
| Form & Phase project | `/studio/work/form-phase-system/` | Clearly labeled studio-initiated work, actual decisions, working artifacts, connected result |
| Studio | `/studio/about/` | Independent studio point of view and working practices |
| Contact | `/studio/contact/` | Context, timing, validation, delivery feedback and a copyable fallback |
| Privacy | `/studio/privacy/` | Production-facing information practices, browser preferences and choices |
| Accessibility | `/studio/accessibility/` | Website access features, continued improvement and reporting route |

## Full journey coverage

| Concern | Main destination and specific section | Supporting connection |
|---|---|---|
| Product goals and discovery | Strategy: when it helps, scope, delivery strategy | Approach: frame |
| Architecture decisions and tradeoffs | Application engineering: `#architecture` | Quality: architecture |
| Stack selection and build versus buy | Application engineering: `#stack` | Approach: foundations |
| Web/mobile channel strategy | Strategy: `#web-mobile-strategy` | Engineering: web/mobile |
| Responsive behavior and device conditions | Experience design: `#responsive-design` | Engineering: `#web-mobile`; Quality: performance |
| Data ownership, models, migration, retention, backup | Application engineering: `#data-strategy` | Quality: data; Evolution: deployments |
| Application implementation | Application engineering: scope | Approach: build |
| API design and contracts | Platforms: `#apis` | Engineering and Quality: testing |
| Third-party integrations and workflows | Platforms: scope and APIs | Evolution: operations |
| E-commerce platform strategy | Platforms: `#commerce` | Discovery and experience design |
| Payments, subscriptions, orders, refunds, fulfillment | Platforms: `#commerce-reliability` | Quality: security/data; API event handling |
| Cloud, environments, secrets, infrastructure | Platforms: `#cloud` | Evolution: deployments/operations |
| Visual/style systems and tokens | Design systems: `#foundations` | Experience design and actual component lab |
| Components, variants, states and patterns | Design systems: `#components` | Lab and studio project |
| Design-to-code alignment and governance | Design systems: `#practice`, `#adoption` | Approach: shape/build |
| Development process and code review | Evolution: `#sdlc` | Approach: build |
| QA and release acceptance | Quality: `#testing` | Approach: release; Evolution: readiness |
| Deployment, CI workflows, migrations, rollback | Evolution: `#deployments` | Platforms: cloud |
| Observability, support, maintenance, modernization | Evolution: `#operations` | Quality: operations; Approach: learn |
| Accessibility, security, reliability | Quality & care | Cross-linked from every service |
| Ownership and handover | Approach: questions/collaboration | Evolution: outcomes |

## Evidence and boundaries

The user approved using the studio project for Work. It is explicitly studio-initiated. No client names, commercial outcomes, performance improvements, testimonials, or team credentials have been invented. The working guide and lab are the inspectable evidence.

Service copy describes the intended scope and working approach. Engagement-specific commitments—availability, pricing, support coverage, ownership, assurance, and specialist review—remain subject to agreement.

Public pages use production-facing copy. Inquiry delivery is not configured: the form reports a failed send rather than simulating success. Privacy and Accessibility share a section index, update date, brief summary, and a narrow reading column. Deployment requirements and notice assumptions are maintained in `PRODUCTION-NOTES.md`.

Perspectives remains a later collection, as in the original outline. It has no empty navigation destination. The two homepage detail teasers now lead directly into substantive expertise pages.