Content Update Process Improvement

[santwuma]

Story: As content editors for the PCP site, we need to provide PCP team with a standardized process for new request intake and resolution in order to efficiently fulfill new content update requests

Background: PCP is a static site generator (went live June 2023) and doesn't have a CMS backend for Content owners to manage and post new content on site. All content (or functional, design updates) require a developer and a production deployment.

Ideas to streamline process:

• Create an SOP that outlines ticket reqs (DOR, ticket templates for different requests), a breakdown of website and terminology (site sections, pages etc..), development process ( including review cycles and timeline) - Sandra
• Streamline CI/CD pipeline so not all updates require a prod deployment - implement markdown file process - James/Erik
• Add Zola and Tula (PCP comms POCs) to Github so they can skip JIRA and enter tickets directly in Github and assign

Next steps:

• Implement dev work to enable markdown files process by end of January (ahead of de date for publishing annual report) - meeting scheduled for Mid Jan
• Create SOP by end of January
• Review new process with PCP

[santwuma]

PCP wants to move to the DP as a microsite - so only implementing below process improvements ahead of the move.

Process changes:

• Remove backstop regression tests
• Update process so Test is updated when a PR is merged in