General Process Overview

(Potential) Headless Process Overview

Headless presents an opportunity to rethink how a design becomes a live site and cut down on rework and copy pasting.

The following is a proposed possible process overview that has not been tested yet:

1. Techplan and Design are created and approved.
2. Integration team begins by creating the local-development environment and content model. During content modeling, Integration builds out (in the CMS) a style page set of pages, each featuring either a page type or a set of block types as appropriate and possible. See the style guide section in the Blend SaaS site for an example.

3. With the content types defined and local development environment built, the Presentation team begins implementing a static version of the site (within the live app, in a static group/path), following the properties defined in the styleguide.
4. With the static site built, Integration can build the final block / page views.

Unanswered Questions

• It's not clear when / how the Integration and Presentation hand-off is going to happen. Can Presentation start before 100% of the content type modeling is complete?
• It's not clear the relationship between the static version of block/page views and the live version of the block/page views. In theory, the static site could go so far as to use the live versions of the block/page views and just pass the expected data through, reducing redundancy and copy/pasting. But content from the CMS can be complex and hard to fake for static sites.