DocOps Pipeline for LM (MVP 1)

[cloudjumpercat]

AC:

• [x] Exported files from WordPress are converted to markdown and uploaded to GitHub
• [x] Markdown files are linted correctly
• [x] Branching strategy is in place
• [x] Release strategy is in place
• [x] Releases are pushed/built in a GitHub pages site
• [x] GitHub pages page is in the correct style
• [x] branch protections in place

[cloudjumpercat]

Here's how GH does their own RN: https://github.com/github/docs/tree/main/data/release-notes/enterprise-server

[cloudjumpercat]

Here's how GH does the backend of their MD pages: https://github.com/github/docs/tree/main/content

• includes how they specify which tier the content is for (and what version)
• also redirects

[cloudjumpercat]

Release Notes Strategy: Based on what I know now (and assuming RN are owned by TC), there seems to be two sort of MVP 1 options:

• have a folder with separate MD files for each release (complication of this is how do people add to the same RN when they are working on different branches?) and those live in a category on the main docs site. These will be branched in and merged like a regular MD file.
• use the Release GH feature. I think you should be able to pull these in to the docs site using a blank MD file with some yaml backend. Complication of this is how do you write release notes (especially longer ones that will need more text, I don't want writers to need a "parking lot") before a release is made?

I think the "release" feature could still be used in either way just as a visual for writers about what is in a release.