-
Notifications
You must be signed in to change notification settings - Fork 23
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] use spacing tokens names instead of values #2140
Comments
@marionnegp Is this effort worth creating a doc or spreadsheet to capture all instances? |
Probably not. It'll double the amount of time spent looking for the instances, and you'll be able to view where changes were made within the PR. It would be good to have someone double check the DP- version of the site and review that instances weren't missed. |
ripgrep is our friend This one should help identify hex colours in backticks The search from above, expanded to include more units
https://github.com/BurntSushi/ripgrep?tab=readme-ov-file#installation |
Thank you, @bennypowers!! |
@bennypowers, is it useful to keep the number values in README files? Should those be replaced? For example, ripgrep found:
|
I'm going to leave the |
@marionnegp if there's a token name for those values, why not replace them in the READMEs, too? |
Description
This was briefly discussed in chat over the weekend. Docs pages should use token names for spacing instead of pixel values. e.g. Guidelines pages for elements or patterns should read "vertical spacing is
--rh-space-xl
" instead of "vertical spacing is24px
"I found the following instances of one or more digits followed by "px", surrounded in backticks
Links
https://ux.redhat.com/elements/call-to-action/guidelines/#space-in-groups
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: