cityofaustin / techstack

Project management for the City of Austin's new digital service delivery platform, Austin.gov.
11 stars 3 forks source link

Create a "Staging" site for content, not code #3161

Open Niicck opened 4 years ago

Niicck commented 4 years ago

As a content editor on Joplin I want a "staging" site so that I can see my content published on a site, without publishing to production.

Is your feature request related to a problem? Please describe. During the Municipal Court kickoff today, Luz asked if our workflow included a "staging" site to view content drafts on.

This got me thinking what kind of workflow would work for users outside of our ODD group.

What Luz meant by "staging" is not what we would call staging. Our "joplin-staging" site is for staging code, not content. Public content authors should never use "joplin-staging" for anything. "joplin-staging" is only for testing experimental features by ODD internally.

We don't have a "staging" site for drafted content on production that would be used by content authors. We have Preview pages for displaying single pages of content. But we don't have an entire staging site.

Here's a question: should we have an entire staging for content? Is it necessary? Would it be helpful for content authors? Is it something they might expect/want when migrating from Drupal or other CMS tools? Are Previews sufficient?

It's an option to keep in mind as we start transitioning users over.

Describe the solution you'd like A clear and concise description of what you want to happen.

Describe alternatives you've considered Right now, pages can be in a "Draft/Published" state or they can be "Preview" pages.

One implementation for this new feature would be to add an intermediate step between "Preview" and "Published" called "Staging".

So pages could be set to "Draft/Staging/Published" or "Preview."

Additional context This is more of a question for the Content/Design team, I think. But sometimes it's helpful to get ideas that might open up previously unknown possibilities.

easherma commented 4 years ago

Interesting! This makes me thing of two things:

1) We could leverage Wagtails moderation flow: https://docs.wagtail.io/en/v2.6.3/editor_manual/new_pages/previewing_and_submitting_for_moderation.html It's possible that what she's looking for may be a draft version of the site, and there may be a way use these extra page statuses. More likely, it sounds like a confidence issue around previews vs production.

2) It reminds me of the netlify CMS editorial workflow, which I always thought was nifty: https://cms-demo.netlify.com/#/workflow