This is a stretch goal for Elektra.

Problem/Challenge: In the release notes, the list of new features, enhancements, changes, fixed issues and known issues is getting longer and longer.

Solution: To improve the the UX and findability for the end user, it would be easier to categorise the lists of items according to a Quarkus taxonomy, starting with the top level. For example, grouping enhancements, fixes and issues into categories like: Security, Data, Web services... and so on.

Use a consistent set of categories to apply to lengthy lists/tables of items in the Quarkus product doc content.

Challenge:

Who decides what the high-level Quarkus taxonomy should be? Engineering, Docs team (CS and TWs), Community project SMEs, other Runtimes SMEs? 

The RHBof Quarkus taxonomy must align with the community project.