Maturity tracker proof of concept
Created by: jyavorska
This contains fake data but demonstrates driving a feature maturity tracker off of a JSON data file, just like how https://about.gitlab.com/direction/maturity/ works. This would be a potential alternative to a private spreadsheet like https://docs.google.com/spreadsheets/d/101JXaau2EPvi322AOFmNeoeuXSJqlruD8gBBsHl1fmI/edit#gid=0 which was also meant to solve the issue of lack of clarity around maturity levels for features.
- Are these the right maturity definitions? Maybe do we want fewer?
- GitLab tracks the dates different maturity levels were reached. Do we care?
- GitLab also tracks when planned maturity increases are going to happen. That might be more interesting as it gives a sense of where we're focusing.
- Is there other metadata we'd like to show?
- Would we actually use the data on other pages, such that it makes sense to have it in a separate file (as opposed to just manually editing a maturity tracker)
The code is proof of concept level and would need to be rewritten for the real deal. Possibly this content makes sense to be generated at build time instead of run time as well.