Skip to content

2.2 Technical & Delivery Definition - Focused

Tier file - what this step includes at the Focused tier (bands S/M: analytics, forms/email).

Included

  • Platform confirmation ADR from the default stack - a reasoned recommendation for this client's context, never a default, recorded as the project's first ADR
  • Plan selection with its named upgrade trigger
  • Integration map at S/M: analytics, form submissions / email
  • Performance, accessibility, and security baselines stated as commitments with targets, from the boilerplate
  • Content migration approach where there is an existing estate, including the redirect principle - sized to the content estate, not the tier (migration SEO risk is assessed on every replatform)
  • Content ownership, feeding the content governance document (2.1); environments and constraints defined

Not Included (Upgrade Triggers)

  • CMS comparison matrix (options considered, editorial and development experience, migration effort, total cost of ownership) → Core.
  • Business-system integrations (CRM etc.) → Core.
  • Multiple, volatile, or custom APIs; multi-property or multi-region architecture → Full. A volatile or custom API is an XL driver on its own, regardless of count.

Outputs

The platform ADR, integration map, architecture overview, and migration approach - landing in the Cornerstone's CMS Recommendation, Technical Specification, and Content Migration sections.