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

feat: Add(+enhance) color/theme usage specification #5

Open
bigpick opened this issue Jun 11, 2021 · 0 comments
Open

feat: Add(+enhance) color/theme usage specification #5

bigpick opened this issue Jun 11, 2021 · 0 comments
Assignees

Comments

@bigpick
Copy link
Collaborator

bigpick commented Jun 11, 2021

Info

Right now, the palette at https://github.com/pineapplegiant/spaceduck#colors-palette- just has a "SYN ID" column, that sort of says where a color should be used, but is pretty limited.

What would be really great is if we had a full (or at least, much more detailed) spec that outlined what colors should be used for what and where. Granted, it's hard to specify exactly all possible fields since each port will likely use slightly different variations for names and whatnot, but having a solid basis to work off would be a huge improvement.

E.g, Dracula has https://spec.draculatheme.com/# which is nice because its a lot more specific for things like syntaxes, which would help when filling out a port for something like VS code or Atom Syntax or w.e.

Nord has https://www.nordtheme.com/docs/colors-and-palettes which is a looser guide (not specific syntax names) and more of a "when to use what where" spec.

Personally, I think having a combination of both would make it so that the ports have a much better chance at all being consistent, and your original vibe of the theme is persisted across them all.


I think the first step though is getting the colors/palette finalized first, though.

  1. Finalize colors/palette
  2. Define/create/publish spec
  3. Update existing ports to match/comply, use a guide for future ports (updating when necessary)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants