Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Functionality] Research and selection of a CMS or SSG for managing Vocabulary Docs #215

Open
1 task done
possumbilities opened this issue Oct 14, 2024 · 0 comments
Open
1 task done
Assignees
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

Comments

@possumbilities
Copy link
Contributor

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

  • I would be interested in implementing this feature.
@possumbilities possumbilities added 🟩 priority: low Low priority and doesn't need to be rushed 🧹 status: ticket work required Needs more details before it can be worked on ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository labels Oct 14, 2024
@possumbilities possumbilities self-assigned this Oct 14, 2024
@possumbilities possumbilities moved this to Ready in possumbilities Oct 14, 2024
@possumbilities possumbilities moved this from Ready to Backlog in possumbilities Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
Status: Backlog
Development

No branches or pull requests

1 participant