Deciding on Color Standards
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Talking on the usace-groundwork-water call we were discussing this issue:
We were wondering if it made more sense to push these into groundwork and have established colors we can select from in [tailwind(https://github.com/USACE/groundwork/blob/main/tailwind.config.js#L17).
These would be generic that could be used for a variety of purposes: Toast messages, table status alerts, notification count, etc
Open to suggestions on the colors but it was brought up that USACE may already have these standards defined.
508 compliance comes to mind in regards to visual considerations and color blindness.
@MikeNeilson I thought at one time you showed me a website that provided recommended colors?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with tailwind.config.js at the linked color definitions and read the related groundwork-water issue. Research the referenced USACE standards and assess the 508 and color-blindness considerations before proposing a palette. Done means the color standard and its intended uses are agreed and reflected in the project configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, tailwind
- Domain
- accessibility, design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100