Skip to content

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

@possumbilities

Description

@possumbilities

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.

Metadata

Metadata

Labels

Type

No type

Projects

Status

Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions