Skip to content

Moving "Components" page into its own category #1230

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
yyx990803 opened this issue Oct 20, 2017 · 3 comments
Closed

Moving "Components" page into its own category #1230

yyx990803 opened this issue Oct 20, 2017 · 3 comments

Comments

@yyx990803
Copy link
Member

yyx990803 commented Oct 20, 2017

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?

@chrisvfritz
Copy link
Contributor

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.

How does that sound to you?

@yyx990803
Copy link
Member Author

Sounds good!

@sdras
Copy link
Member

sdras commented Apr 17, 2019

This has been done for a while :)

@sdras sdras closed this as completed Apr 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants