Open bmorelli25 opened 5 years ago
I don't think this is something we'll do before the re-design.
I'd be interested in suggestions on how to annotate this in the Asciidoc so that this information can be automatically determined. Unless we just want to automatically (maybe via a per-book configuration section) make the first level TOC entries "categories".
This feature request came up in a conversation with @gchaps, @DonNateR, @lcawl, and @nik9000. Please feel free to edit this issue if I missed anything.
The Problem
Nested content is hidden, which can make it more difficult to find. This problem was brought to light when Machine learning docs were nested under the Extend your use case heading:
Data point: When I created that ^ screenshot, it took me four guesses to figure out which tab the ML content was nested under.
The solution
Allow TOC "categories". The categories could be used to break up the doc nav, without hiding important content.
Here's an example. The categories are:
Get started
,Explore, analyze, visualize
, andShare and collaborate
. Indented headings are links to content:A quick mockup as to what this might look like:
Short-term
A short-term fix has been outlined in https://github.com/elastic/docs/issues/1286