Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

@aisgbnok Thanks so much for opening a PR! I'll get this triaged for review ⚡

I based my syntax on the World Wide Web Consortium's CSS Color Module Level 3.

• RGB (HEX and RGB)
• HSL

While those links may be helpful, I decided against linking them because I don't think GitHub Docs needs to explain how web colors work. It could also be further confusing because the GitHub supported color models don't support the three hexadecimal characters format, as listed in W3C.

I included a note for the whitespaces, but wasn't sure if I should add one for the HEX requiring six hexadecimal characters.
Works: #FFFFFF Doesn't: #FFF

I think it's fine because the syntax column that I have only lists the six-character version. If someone tries three characters they should realize pretty quickly that six are required.

@aisgbnok Thanks so much for including all of this helpful information into the decisions you made 😍

We don't support .svg, if you could update these to be .png that would be super helpful. Thanks again!

Thanks, @janiceilene, I have replaced the .svg files with .png files. Let me know if there is anything else I can do!

@hubwriter, unfortunately, it seems like it only renders in Issue/PR descriptions or comments. I should have tested in a readme as well.

Should we scratch the whole section or add a warning note that it does not work in markdown files but will work elsewhere? Apologies for this oversight, thanks!

The background color should be #ffffff for light mode and #0d1117 for dark mode.

@aisgbnok - Ah, that makes sense. Thanks.

I think it would be a shame to lose this entirely.

I'd suggest making a couple of changes.

Change:

You can call out color within a sentence with single backticks. A supported color model within backticks will display a visualization of the color.

to:

In issues, pull requests, and discussions, you can call out colors within a sentence by using backticks. A supported color model within backticks will display a visualization of the color.

And also change:

Note: A supported color model cannot have any leading or trailing spaces within the backticks.

to:

Notes:

• A supported color model cannot have any leading or trailing spaces within the backticks.
• The visualization of the color is only supported in issues, pull requests, and discussions.

@hubwriter, thanks, I committed your suggestions.

@aisgbnok - That's great. Many thanks for your help. 🎖️

I've approved this to be merged. We have a merge freeze on the repo until 11 July but we'll get this merged/published after that. 🚀

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡