🌸 `DesignLibrary`: `NeighborhoodNavigation`

[zspencer]

• https://github.com/zinc-collective/convene/issues/1187

OK, so I really like where @anaulin went with the Marketplace::ManageComponent, and I'm trying to imagine what something like that could look like for the entire application.

For a navigation hierarchy that looks something like this:

1. Neighborhood  # Maybe only if current_person.operator?
  a. People
  b. Spaces
2. [Space](edit_space_path(space)
  a. [Members](space_members_path(space))
    i. [Invitations](space_invitations_path(space))
    ii. Groups
  b. Utilities
    i. Stripe
    ii. GitHub
    iii. Add Utility
  c. Rooms
    i. Room A
      1. Marketplace
        a. Products
        b. Delivery Areas
        c. ...
      2. Add Furniture
    ii. Room B
      1. Journal

How far the navigation is expanded is determined by the particular page we're editing. For example:

• If we are on the edit_room_path(room_a) the side panel would show items 1, 2, 2.a, 2.b, 2.c, 2.c.i, 2.c.i.1, 2.c.i.2, and 2.c.ii.
• If we're in the edit_space_room_marketplace_path(room_a_marketplace) the side panel would show the example above, plus 2.c.i.1.a, 2.c.i.1.b, etc.

Ideally, this will build on the sense of location that we've established with our horizontal breadcrumbs, but also provide affordances for navigating sideways and down

From a visual hierarchy perspective, my gut says that indenting deeper and deeper is not going to fly, but perhaps something where we use font weight and size to indicate how far they are from the "trunk" of their space.

Thoughts?