Closed GuentherJulian closed 2 years ago
@GuentherJulian thanks for this issue. I fully agree that it is kind of confusing for the reader. However, IMHO the answer is not to restructure some asciidoc files but to generally stop making the website a hierarchical bullet list of our includes of asciidoc files. It is perfectly fine to have small asciidoc files per specific topic and to have many of them. It is rather a question how to present them to the end user. Options could be:
Java
, .NET
, TypeScript
, etc. then e.g. in TypeScipt
choose frontend or backend, in TypeScript/Frontend
choose Angular
or React
, etc.The bullet points are sorted with most maintenance effort downwards.
Meanwhile the website team also agreed about this strategy so I am closing this here. Changes need to be done in the website build itself.
There are currently many guides in the 'General' section of Java in the homepage outline. Therefore this outline becomes quite long and unclear when expanding this section.
We should think about a solution to improve the structure of the outline so that it is easier for the reader to read and find the right documents.