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
We are having more and more content in the component page, which itself is arguably one of the most important concept in the framework. However currently in the sidebar it only has a very low-profile link to the entire page. The page itself is also getting extremely long, making it difficult to navigate.
I think it's time that we break the page into multiple ones and make "Components" a category of its own. In the sidebar, we could have listing like below:
Components
Intro
Props
Events
Slots
Async
Misc
For the new component composition page, I'm not entirely sure whether it should be included here or in the dedicated Reusability and Composition section. Thoughts?
The text was updated successfully, but these errors were encountered:
Agreed - I plan to do this soon. I was thinking of keeping the components page, but changing it to more of an intro with only the basics of slots, props, and events. The reasoning is I still want to keep basic component usage in Essentials.
Then all the more advanced content would be split between new pages in a new Advanced Components section (name TBD). The new component composition page would then be moved there.
We are having more and more content in the component page, which itself is arguably one of the most important concept in the framework. However currently in the sidebar it only has a very low-profile link to the entire page. The page itself is also getting extremely long, making it difficult to navigate.
I think it's time that we break the page into multiple ones and make "Components" a category of its own. In the sidebar, we could have listing like below:
Components
For the new component composition page, I'm not entirely sure whether it should be included here or in the dedicated Reusability and Composition section. Thoughts?
The text was updated successfully, but these errors were encountered: