Closed tlberglund closed 5 years ago
Nested tabs is a really tricky/taboo UX pattern because it ends up being hard to reason about the content as a viewer. Making adjustments like this would be better left to a real designer. Let's find one!
One thing to add: there's definitely more scrolling than we'd like on the page right now. I think it certainly needs something better in the way of navigating. As an orthogonal solution, one of the things I've seen before and really like are expansion code blocks. Bulma does this in its own documentation:
The idea is that if the block is bigger than, say, 320px, it's automatically bound at that size unless you choose to expand it. That's one way to make it look friendlier out of the gate.
Autocompressed code blocks and a linkable TOC the top of the page work for me! And agreed on nested tabs. Let's just have the TOC be the working TOC for each tab. (NB: combinatorially that is equivalent to dueling tabs, but prolly easier to think about.)
Design's swooping in :)
The tabs for the separate platforms (
kafka
,kstreams
, andksql
) are super handy. What would we think of extending the tabbing system to the three...let's call them "modalities," so we can sound extra annoying (try/test/deploy)? It might make each recipe page a bit less daunting and require less scrolling.