Content Workflow (UI & implementation)

[dmerckx]

We feel like we need an updated approach to managing drafts for a solid alpha version.

I suggest we start out with 3 different phases:

• draft version
• published version
• archived version

In between those phases we identify 2 transitions: publishing, unpublishing.

Technically I propose every phase exists as a separate file, within our repository: eg. blog.json, blog.draft.json, blog.archived.json.
Multiple versions can exist along side of each other: eg. a new draft version can be created for a published version.

By using an environment variable one should easily be able to tell the Alinea to only query the published pages, or also include drafts. This could allow to easily setup a staging environment (eg. creating a different Vercel project form the same repo, with different environment variables).

The following screens should highlight how this could work in practice and can serve as a starting point for building the UX:

TODO: add screens/flow for archiving

A lot of the functionality is based on how Prismic currently handles content workflow (drafting, publishing, archiving). Its worth their mechanism to get a good grasp of what I'm proposing.