Skip to content

Transition Wiki, Pages, and Content Editor to Plan > Knowledge

Eric Schurter requested to merge master-patch-b957 into master

Description

Wiki, Pages, and Content Editor are shifting from Create Stage to Plan Stage Knowledge Group. Associated Issue for transition.

Tasks

  • Move direction pages to Plan/Knowledge
  • Create group direction page for Knowledge
  • Update Editor group direction page @ericschurter
  • Redirect direction pages to /plan/knowledge
  • Check old redirects that may point to Wiki, Pages, Content Editor... then redirect the redirects @ericschurter
  • Add content to Knowledge group direction page @mmacfarlane (In progress. Gathering feedback from team in this Issue and set due date to publish this by March 3rd.)
  • Update content in Wiki direction page, fix links as needed @mmacfarlane (MR)
  • Update content in Pages direction page, fix links as needed @mmacfarlane (MR)
  • Update content in Content Editor direction page, fix links as needed @mmacfarlane (MR)
  • Update categories.yml
  • Update stages.yml
  • Update features.yml
  • Update team member yaml (complete by EM John Hope on 2023-03-14)
  • Update CODEOWNERS: @mmacfarlane updated CODOWNERS files for reach category direction page on 2023-03-02.
  • Handle triage bots (complete by EM John Hope)
  • Update planning issue automation (complete by EM John Hope)
  • Update automation in issues for kickoff, PI review (being complete in this MR by EM John Hope)
  • Update PI yaml (being complete in this MR by EM John Hope)
  • Create Triage-ops issue for label change @mmacfarlane (Issue)
  • Remove Plan Stage Direction Page for Certify @mmacfarlane (MR)
  • Close Certify Slack channel via Archive and create Knowledge group Slack Channel @mmacfarlane
  • Update Product Categories Page to Remove Certify @mmacfarlane
  • Update Matthew Macfarlane Persons Page to Reflect Changes @mmacfarlane (MR)

Author Checklist

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail

Edited by Matthew Macfarlane

Merge request reports