Epic: Establish Wagtail as a usable workflow on existing mozorg surfaces.

[alexgibson]

Description

Bedrock has a new Wagtail powered CMS back-end / database, but it is not yet powering any pages in production. The aim of this epic is to migrate one or more existing surfaces to be editable by the CMS, as well as establish the processes, guardrails, and workflows that need to be implemented in order to support CMS management in a safe, predictable manner.

Key results:

• Migrate one or more existing mozorg surfaces to Wagtail. Possible candidates include
  • Leadership page (updated regularly, en-US only).
  • VPN resource center (localized workflow).
• Implement user groups and permissions for editing, previewing, approving and publishing content.
• Implement content publishing approvals and workflow.
• Document workflows, processes and software-enforced “guard rails” for:
  • CMS users editing, and publishing content to existing CMS surfaces.
  • Developers creating new CMS editable content pages.
  • Developers updating models / templates for existing CMS editable content.

Epic will be broken down into individual issues below:

Tasks

Beta Give feedback

1. Update make preflight to create a local CMS admin account #14798
   Backend Wagtail +2
   
2. Add docs for creating new content editable surfaces in Wagtail #14797
   Documentation 📝 +1
   
3. Migrate /about/leadership/ page to Wagtail #14801
   Backend Frontend +2
   
4. Document how to migrate a page to the CMS
5. Add docs for running DB migrations and squashing migrations
6. Add cms_url helper to provide lang-prefixed relative path to a CMS page from any page #14871
   +0
   
7. Prototype prefer_cms decorator to allow for transitioning from existing hard-coded to CMS pages #14829
   +0
   
8. Support limiting which pages can be selected for use in a Dev/Stage/Prod #14843
   Wagtail +1
   
9. Add automated check for missing Django migrations #14859
   Backend +1
   
10. Migrate VPN Resource Center to Wagtail #14860
    +0
    
11. Document scheduled publishing of pages (including making it explicit that the TZ in use is always PST)
12. Establish user groups, roles, permissions and publishing workflows for Wagtail pages. #15059
    +0
    
13. URLs that use prefer_cms should merge active_locales data #15349
    Bug 🐛 +1
    
14. Publish VPN RC content in Wagtail for en-US #15350
    +0
    
15. Order VPN articles by first published date (descending) #15517
    Bug 🐛 +1
    
16. Localize VPN resource center content via Smartling/Wagtail #15520
    +0

[stevejalim]

Re moving the VPN Resource Center to Wagtail is that it'll be v interesting to see if the existing translation work is recognised as being valid and automatically reused, or if Wagtail will chunk the strings differently from Contentful. The latter would be a surprise, but let's see...