[Functionality] Research and selection of a CMS or SSG for managing Vocabulary Docs #215
Open
1 task done
Labels
💻 aspect: code
Concerns the software code in the repository
✨ goal: improvement
Improvement to an existing feature
🟩 priority: low
Low priority and doesn't need to be rushed
🧹 status: ticket work required
Needs more details before it can be worked on
Problem
At current the Vocabulary Docs are one long static html file. Over time this could become increasingly difficult to manage.
Description
There is an argument that the introduction of a CMS/SSG (like 11ty, for example) could be useful here.
However, any CMS/SSG utilized would have to fully weigh the complexity it adds to the complexity it resolves.
Alternatives
Keep the file as a static .html file and don't add a CMS/SSG.
Additional Context
While this decision remains unmade: major design work or advances in the UX of the docs are essentially frozen as that might impede a smoother migration into a chosen CMS/SSG.
Implementation
The text was updated successfully, but these errors were encountered: