We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now, a user has to look through all the examples to know what classes can be added, and the process is generally a copy/paste exercise.
Whilst this is fine to get started, it's not so great for knowing what is available.
Add a "Reference" table at either the bottom or top of each page:
btn
btn-$variant
primary
secondary
text
btn-$size
sm
lg
Approach:
Consider:
Config; one of:
Build:
Apply:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Background
Right now, a user has to look through all the examples to know what classes can be added, and the process is generally a copy/paste exercise.
Whilst this is fine to get started, it's not so great for knowing what is available.
Proposal
Add a "Reference" table at either the bottom or top of each page:
btn
btn-$variant
primary
secondary
text
btn-$size
sm
lg
Research
Approach:
Consider:
Implementation
Config; one of:
Build:
Apply:
The text was updated successfully, but these errors were encountered: