[feat] `<rh-sidenav>` element

[markcaron]

We need a new Side Navigation component for use on documentation (like our ux.redhat.com) or web applications.

Based on prior art, we have 2 quite similar designs:

• PatternFly's Navigation component
• Our UX dot documentation's side nav

The priority is set to high because our current side nav on UX dot poses an inaccessible anti-pattern with it's checkbox-based hamburger menu.

[markcaron]

Worth considering whether this follows the other Navigation naming as <rh-navigation-side>

[wesleymiles]

Chiming in to say that the docs.redhat.com team would like to use this component if possible for the new docs site which will be launched by summit.

[coreyvickery]

@marionnegp Miro link for exploring designs.

https://miro.com/app/board/uXjVN1WFZHg=/

[zeroedin]

<uxdot-sidenav> has been created in #1465 to serve ux.redhat.com until more discovery on <rh-sidenav> is done

[coreyvickery]

@markcaron @hellogreg I would also like to get this done in Charmander. The design is still in progress, but a lot of work has been done so far. It would be nice to get it in front of design leads very soon, but I don't know what that new process is now.

[coreyvickery]

Update 5/27: Team and stakeholders reviewing specs.

https://www.figma.com/proto/aOOto0i3Ph9AfBy42VVej8/rh-side-nav?page-id=1%3A16&node-id=1-2028&viewport=119%2C146%2C1&t=ow7NYJOKiqR9QBTA-1&scaling=min-zoom

[coreyvickery]

@markcaron Do we have a developer assigned to work on this yet?

[bennypowers]

We spoke about this at office hours today:

• "side nav" and "table of contents" should be considered patterns, not elements
• the table of contents pattern is composed of a tree view with an optional filter input
• the side nav pattern is composed of at least two new elements
  1. working title: drawer
  2. working title: tree view (aka drill down?) (nested list of page links)
  3. working title: learning path (linear list of nav i.e. extra-page links) with descriptions
• the side nav pattern may also have things like header widgets (filter search, logo, etc)
• the side nav pattern can compose in a learning-path element instead of the tree view

The drawer, tree-view, and learning path elements do not have slots for things like titles or associated widgets. Rather, those elements are ancillary to the elements themselves, even if they are required in the pattern. In other words, it may be the case that the table of contents pattern requires a heading element as well as a tree view element, but that doesn't mean that tree-view itself is concerned with content headings, rather, it's up to the pattern implementation to make sure the heading is there.