-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
[docs][base] Move styles to the bottom of demos code #36498
Comments
@michaldudak @gzrae I would like to work on this |
Go ahead! Please create separate PRs per component, so it's faster to check, and the progress is more visible. |
@gitstart even i want to work on this, before working can you list components you are working. so that we both don't end up working on same components. |
Hi @sai6855, I was actually planning on working on all the components, but you can feel free to choose the ones you want to work on so I can ignore them. |
Cool I'll work on, |
@varunmulay22 if you want, you can work on this issue |
sure looking into it @sai6855 |
anything I can help here guys? please share the ones you haven't started. I don't see any PR's from your end yet hence asking |
I've pushed a few PRs, the rest are coming soon. |
I have made a list of the unstyled components and updated them with the respective PRs in the description. Feel free to take the remaining components. |
The changes done with this issue make a lot of sense 👌. A possible continuation on this issue: #38911. Instead of moving the source to the bottom, we could move them to a different tab. |
The most important part of the demo - the actual component code should be as high in the file as possible. Currently, most of the demos have significantly large style definitions, which must be scrolled to get to the most important parts of the code.
BadgeUnstyled
#36723Button
demos #36590FormControl
#36579InputUnstyled
#36724Menu
#36582ModalUnstyled
#36580Popper
#36578SelectUnstyled
#36718SliderUnstyled
#36721Snackbar
#36719SwitchUnstyled
#36720TablePagination
#36593Tabs
#36577The text was updated successfully, but these errors were encountered: