Standalone Service Mesh docs:

Prereq:

• File "new CP product" issue for CP team to add Service Mesh to product index + add taxonomy

Process:

• Separate out Service Mesh docs from OCP docs
  • fix incoming/outgoing xrefs 
  • create new distro for Service Mesh
  • get local asciibinder (doc.openshift.com) and portal builds working
  • set up redirects (info)

• Automate docs.openshift.com build
  • Automate Service Mesh build
  • Password-protect the separated content, while still layered in OCP docs

• Set up GitLab for Portal
  • set up branches for versions
  • test sync script

• PV1 
  • set up titles
  • get stage build to work
  • set up separate splash page

• Migration d.o.c
  • Remove password protection
  • Ensure redirects are set up
  • Remove all Service Mesh content from OCP main branch
  • Add stub in OCP docs, pointing at standalone page
  • Check that content is being indexed by google in its new location (check d.o.c/sitemap.xml and manually test)

• Fix conditional content for distros
  • Identify ROSA/OSD-only content and include it in SM docs

• Migration CP
  • Publish new content
  • Remove content from existing OCP splash page
  • Add stub pointing to new splash page
  • Check that content is being indexed by google in its new location

Change management

We will follow a modified version of the OCP docs change management process. Since this restructure is touching most areas of Service Mesh docs, it will be an iterative process to implement.

Stakeholders to approve the epic

Please add a comment on this epic with an ack/approval, indicating that you approve of our TOC restructure plan.

Engineering:
PM:
PX:
Docs:
QE:
PgM: