You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's no way to tell which group header is clickable. In this example, you can click on Appbar and it opens the proper docs page, while clicking Avatar makes the section collapse. This makes it harder to just go through the docs.
It could either have some visual indication or maybe open the first sublink by default?
Other than that, great work with the recent changes. It really improved visually 👍
The text was updated successfully, but these errors were encountered:
Trying to style it might be the hardest way to handle it, I can't recall seeing it handled this way anywhere. But there's some other solutions that could work:
keep the non-clickable groups collapsed by default - this way the initial click moves you further suggesting to click the sublinks instead of hiding them
make it open the first sublink on group click
create extra doc pages for the non-clickable groups with an overview of the inside components (links to components, screenshots, some descriptions)
As for the styling ideas, the only one I can think of now is placing some extra "component" icon to distinguish components from empty links or description pages
I think the second solution will be the easiest option.
There are some more reason groups aren't collapsed by default 1) The pages work without JS, 2) We need to measure the height so they need to be not collapsed (not sure about this one)
There's no way to tell which group header is clickable. In this example, you can click on Appbar and it opens the proper docs page, while clicking Avatar makes the section collapse. This makes it harder to just go through the docs.
It could either have some visual indication or maybe open the first sublink by default?
Other than that, great work with the recent changes. It really improved visually 👍
The text was updated successfully, but these errors were encountered: