feat: legacy details #81
Conversation
This adds a details blocks for legacy mode. If one is toggled, all are toggled. Alternative to #80 The idea is to add legacy syntax inline into the documentation at the appropriate places using these notes, and devs can hide those when unchecking the checkbox. The "Reactivity Fundamentals" page shows how this would look like.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
I wonder if people will realize that collapsing one of the highlight sections will collapse them all. I think I'd just scroll past it and not collapse it because I wouldn't care about saving 100 pixels of space. If I knew it would close all of them I would certainly do that, but I wonder if we can make it more discoverable somehow I wonder if instead of the triangle in the top left having text in the top right that says "hide legacy docs" or something might be a bit clearer? |
|
nice idea. done. Styling-wise I think there's more we can do, but I want to tie that work into some other stuff I have in my head (will try and put an issue together shortly) |
|
Perhaps something for the issue: I was going to suggest dropping the bold font-weight from "show all"/"hide all". Here's a screenshot
|
3 participants
This adds a details blocks for legacy mode. If one is toggled, all are toggled. Alternative to #80
The idea is to add legacy syntax inline into the documentation at the appropriate places using these notes, and devs can hide those when unchecking the checkbox. The "Reactivity Fundamentals" page shows how this would look like.