feat: deeper nav

[wesleyboar]

Peer asked me about doing this. I'll show the result on pre-prod for stakeholder meeting tomorrow, where I offer his request be presented.

Important

• What documents want this?
  ^Hazmapper
• What do T.C., E.R., and H.P. think?
  ^{No concern. They left me to decide.}
• What documents/nav are affected?
  ^{Hazmapper, Vortex, several Use Cases}
• Make deeper headings compete less for attention.

Hazmapper:

pre-prod Hazmapper

pre-prod.deep.mov

prod Hazmapper

prod.shallow.mov

[silviamazzoni]

I'm always a fan of freedom and opportunity.... when you go so deep you either have to make the left nav much wider, of you have to use short words. but that's up to the author.

[wesleyboar]

@silviamazzoni, yup.

I worry this affects more than just the document of concern (unknown, awaiting answer from peer). I'll check tomorrow before meeting (as time allows) which nav items will newly show up, and which are just too long for this.

[taoteg]

I think the level 6 depth would work okay as is.
I don't see any unintended changes to the nav design by this change.
The only places in the existing docs that this unintentionally extends are these:

• Hazard Apps > VORTEX-Winds: DEDM-HR > Jupyter Notebook for DEDM-HR > Implementation > entries_visible
• Several Use Cases would also reveal new L5 headings (a few have L6 - Seismic section).

The nested headings at L6 aren't gorgeous but they are usable (imho).
Is there a way we could style the L6 links to not be so heavy and large?
Maybe a plain or italicized text for the L6 links at a smaller font?
Or possibly just all the leaf nodes get that treatment?
Dunno if that is possible with the mkdocs theme setup.

But the main reason for adopting imo is that all the linking just works out of the box using the markdown without having to resort to html hacks or weird inconsistencies in the config setup.

[wesleyboar]

Thanks for checking what else is affected. I had no bandwidth yesterday. Yes, I can make deeper headings compete less with existing headings. I anticipate no problem with this change.