oxidecomputer / oxidecomputer/omicron

Wicket styling tracking issue

Open
#2,560 3 comments 0 reactions 2 assignees View on GitHub

@benjaminleonard is already working on this.

Since Mar 14, 2023.

wicket
Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

  • Dim green is hard to see when used for text. A new color or two would be nice. Yellow and purple is not my fav combo.
  • All capital letters are hard to read for dyslexics.
  • Component status for updates should be displayed for the top level rack component in the tree, even when closed.
    • We should use colors for this
    • We should add a custom indicator character in front of the component name for each state for those who are colorblind
      -[ ] We should style sleds that are not present differently. Note that presence can be detected by ignition, but also ignition may fail and we may still see presence from the management network. We should check for both. If we can get data back the sled is present.
  • We should style components when they are present but unavailable. Style by power state?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.