[Feature]: Replace FAQ fixed documents with a CMS

[rmccue]

Current Behaviour and Context

Currently, FAQ entries are stored in this repository as part of the documentation. This creates overhead to updating these entries, which somewhat defeats the purpose of them.

We created the FAQs as a way to move faster and have some lightweight docs which intentionally weren't linked to the codebase (unlike our full docs, which are designed to be updated alongside the codebase). This setup doesn't really fulfill this.

Improved Behaviour

We should move our FAQs into a dynamic CMS - I think a custom post type in Vantage probably is a decent spot for this to live. With the new docs system, we can hook this up fairly easily with an Astro <> WP connector.

At the same time, we should change the sidebar navigation to list only the categories, and then the category pages can link out to the FAQs. We could even consider having all the FAQs for a category on a single page similar to AWS' FAQs:

Additional Info

No response

[rmccue]

Thrown together pretty quickly in Astro with a CPT:

[rmccue]

cc @owaincuvelier @mikelittle for your feedback

[mikelittle]

This seems like a good idea. Certainly, easier to update/add to than the current set up.
Will the docs site pull them live from the source client-side, or just during the site build. The latter seems more performant to me. They don't get updated that often, and there's no reason to have random visitors hitting vantage.

Will the CPT editor accept markdown, or will it do WordPress blocks? The latter will require numerous css and js files from WordPress, that feels unnecessary.

[rmccue]

Will the docs site pull them live from the source client-side, or just during the site build. The latter seems more performant to me. They don't get updated that often, and there's no reason to have random visitors hitting vantage.

The POC I've got in the screenshot here is build-time, works the same way as the docs (using Astro's content collections). Means we have to rebuild when we update the content, but if we rebuild and push docs daily that's not a big issue.

Will the CPT editor accept markdown, or will it do WordPress blocks? The latter will require numerous css and js files from WordPress, that feels unnecessary.

Currently, rich HTML in Gutenberg; no complex blocks (eg columns) will work but the standard rich formatting works I think.