NixOS / NixOS/branding

Rationale behind the palette is missing

Open
#14 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
66
Forks
16
PR merge metrics
No merged PRs in 30d

Description

I've not interacted with this repo, even though I have strong opinions and feelings about what is being done... You know, having been involved and evolved the design language of NixOS in the past. Including tracking down its history.

I have been subscribed though to keep tabs on what is going on.


From #12, which got locked:

The color palette was designed grounded in ideas from color theory and color psychology.

Which are?

First, I'll give you benefit of the doubt, and talk about the palette, the ten options (including black and white) described in that section.

Now, AFAICT from the history (which got scrubbed by a needless and shameful squash merge) the best I can see is that a palette was added, and names retrofitted onto the colours, without much of a justification.

I think what proves my point that there is no such "design grounded in [whatever bullshit]" is also how the logo was added with its original colours (almost, #5377c3 instead of #5477c3), then got eyeballed to fit somewhat in the palette of unknown origins.

Is there some part of the work that got lost, or that I am missing? I can't find mentions of color theory or psychology in the repository.

Thanks!

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Review the palette section and the linked commits and repository history, including the referenced NixOS logo color sources. Determine whether the claimed color-theory or color-psychology rationale exists; done means either locating and documenting that rationale or clearly recording that it is absent.

Written by the indexing model from the issue text.

Assessment

Domain
design, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.