Skip to content
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

Add numbers to color palette #163

Closed
JoshuaAdrianJones opened this issue Oct 31, 2021 · 3 comments
Closed

Add numbers to color palette #163

JoshuaAdrianJones opened this issue Oct 31, 2021 · 3 comments

Comments

@JoshuaAdrianJones
Copy link

The information for the color palette and image simply says "All colors are numbered from nord0 to nord15 where each palette".

https://raw.githubusercontent.com/arcticicestudio/nord-docs/develop/assets/images/nord/repository-color-palettes.svg?sanitize=true

Could this SVG be updated to show the numbers of each one, this would make adjusting things much easier.

For context the defaults for Emacs Org-Mode TODO in https://github.com/arcticicestudio/nord-emacs/blob/develop/nord-theme.el set some colors and I would like to easily see which of nordx I should change some colors to.

@JoshuaAdrianJones
Copy link
Author

see: https://svgshare.com/s/bdU

@arcticicestudio
Copy link
Contributor

Hi @JoshuaAdrianJones 👋, thanks for your contribution 👍

Improving the documentations for the individual color IDs has also been raised in #153, but for now I'm not sure if the color & palette documentation page is not good enough. There are plans to improve these documentations, e.g. by splitting the page into sub-pages for each palette, but right now there are other tasks for the Nord project that must be completed first.

The SVG in the GitHub repository is more like a esthetic element for the visual project representation, even though it also includes HEX numbers already (which can unfortunately not be selected anyway 😕). The main source-of-truth should be the official website with its documentations, that why the README is kept quite minimal when it comes to more detailed information and refers/links to the website instead. "One-page" documentations like a README is often not optimal to document a project in a modular and clear way.

@JoshuaAdrianJones
Copy link
Author

closing in favour of #153

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants