Codeberg/Design
Archived
23
51
Fork
You've already forked Design
4

Few color tweaks for the new dark theme #50

Closed
opened 2022年03月25日 00:25:38 +01:00 by mray · 10 comments
Collaborator
Copy link

The current dark theme seems to be a quick adaption that could need many more refinements, here are the three most important issues I spotted that could need fixing:

  • 1. change header colors, too (currently not affected)

  • 2. tone down primary and secondary colors

  • 3. use colors from the palette for key interactions


1.

I added a proposal for the menu header colors in the overview below.
image

2.

I propose colors like #061c2a and #050c10 to be used as primary colors to tone down the relative strong saturation and contrast of the main colors. As a comparison you can see github(gh) and gitlab(gl) main colors in dark mode, and codeberg
image


3.

Key buttons still apply colors from the previous theme, instead of the codeberg palette.
image

overview

image

The current dark theme seems to be a quick adaption that could need many more refinements, here are the three most important issues I spotted that could need fixing: - [ ] 1. change header colors, too (currently not affected) - [ ] 2. tone down primary and secondary colors - [ ] 3. use colors from the palette for key interactions --- ### 1. I added a proposal for the menu header colors in the overview below. ![image](/attachments/da3afd8a-ad3f-41f3-8263-d06331719f95) --- ### 2. I propose colors like #061c2a and #050c10 to be used as primary colors to tone down the relative strong saturation and contrast of the main colors. As a comparison you can see github(gh) and gitlab(gl) main colors in dark mode, and codeberg ![image](/attachments/f43a5e5b-8cc3-44a0-8923-90375f91a255) --- ### 3. Key buttons still apply colors from the previous theme, instead of the [codeberg palette](https://codeberg.org/Codeberg/Design/wiki/Palette). ![image](/attachments/5f51fbce-e220-401f-8616-2f54948ed56c) # overview ![image](/attachments/b5d4506d-40fe-435d-815f-0f4f02562a82)
Owner
Copy link

I still want this to be solved some day :)

I still want this to be solved some day :)
Author
Collaborator
Copy link

I wanted this, too. Half a year ago I suggested the changes above as low hanging fruits – in case anybody touches colors. Just as a bare minimum, as I expect things to go slow. But what was it worth compared to a merge request from last week?

Codeberg/gitea#42

Let us not stand in the way of the few things that actually do happen - there is just no place for suggestions.

I wanted this, too. Half a year ago I suggested the changes above as low hanging fruits – in case anybody touches colors. Just as a bare minimum, as I expect things to go slow. But what was it worth compared to a merge request from last week? https://codeberg.org/Codeberg/gitea/pulls/42 Let us not stand in the way of the few things that *actually do happen* - there is just no place for suggestions.

Reopening as I wanted to discuss the proposal made here (#82 seems to be a duplicate, TL;DR the file that needs to be changed can be found here Codeberg/forgejo@00f7439f97) and take a look at whether I can implement some changes based on what you said here:

I shared the screenshot in the Codeberg Matrix chat and asked if the right window looked better than the left window. The person who inspired me to open the aforementioned issue and investigate this problem, @Akselmo, told me something about "keeping the green buttons". I trust you as an authority here, do you think that retaining the green button color would look better?

Reopening as I wanted to discuss the proposal made here (https://codeberg.org/Codeberg/Design/issues/82 seems to be a duplicate, TL;DR the file that needs to be changed can be found here https://codeberg.org/Codeberg/forgejo/commit/00f7439f97d2e9a77438808629f7b570a4e60b4c) and take a look at whether I can implement some changes based on what you said here: I shared the screenshot in the Codeberg Matrix chat and asked if the right window looked better than the left window. The person who inspired me to open the aforementioned issue and investigate this problem, @Akselmo, told me something about "keeping the green buttons". I trust you as an authority here, do you think that retaining the green button color would look better?

Not necessary to keep the green buttons, but I think it's a bit easier to eyes than yellow

Not necessary to keep the green buttons, but I think it's a bit easier to eyes than yellow
Author
Collaborator
Copy link

do you think that retaining the green button color would look better?

I think the problem isn't how things look, but what they mean. There is a need for "loud" buttons and for buttons that seamlessly fit into the rest. The question is what options does the design system provide? And which button style was chosen for what reason.

My proposal is an attempt to find an equivalent to the screenshot on the left. Maybe it is too dominant in that context, but it is equivalent.

It would make sense to understand the underlying system and start theming from there – and not change particular buttons on particular pages based on the looks.

Maybe all it takes is to just apply the same style twice, like so:
image

and keep the yellow button for other use cases where a loud button is necessary.

> do you think that retaining the green button color would look better? I think the problem isn't how things look, but what they mean. There is a need for "loud" buttons and for buttons that seamlessly fit into the rest. The question is what options does the design system provide? And which button style was chosen for what reason. My proposal is an attempt to find an equivalent to the screenshot on the left. Maybe it is too dominant in that context, but it is equivalent. It would make sense to understand the underlying system and start theming from there – and not change particular buttons on particular pages based on the looks. Maybe all it takes is to just apply the same style twice, like so: ![image](/attachments/fd90b50a-ef6c-4e56-bd86-41b64e3324dd) and keep the yellow button for other use cases where a loud button is necessary.

Hm, do you think this would work white letters, maybe?

The font hasn't been sitting right with me, I shared this in the Matrix chat again and someone said that "this looks like codeberg-dark and solarized (dark) mixed together" (@aryak), "yellow gives me warning vibes" (@akselmo) and I kind of agree.

Here's how GitHub does it:

image

Do you think that a white (#000000) font would be acceptable?

@akselmo and @aryak mentioned that a dark shade of blue for the font inside of the button could work too, I'm personally not 100% sure. (the one in your original proposal definitely looks great though)

Hm, do you think this would work white letters, maybe? The font hasn't been sitting right with me, I shared this in the Matrix chat again and someone said that "this looks like codeberg-dark and solarized (dark) mixed together" (@aryak), "yellow gives me warning vibes" (@akselmo) and I kind of agree. Here's how GitHub does it: ![image](/attachments/280de6b0-77d9-4ed9-951a-10135f69700c) Do you think that a white (`#000000`) font would be acceptable? @akselmo and @aryak mentioned that a dark shade of blue for the font inside of the button could work too, I'm personally not 100% sure. (the one in your original proposal definitely looks great though)
8.3 KiB

P.S. So far, this looks way better. Thanks!

P.S. So far, this looks way better. Thanks!

Example provided by @akselmo:

image

These are tiny details, but why not clear them up while we're at it?! :D

Example provided by @akselmo: ![image](/attachments/8571dd0e-541e-4050-a5b6-0a5fb1fd0400) These are tiny details, but why not clear them up while we're at it?! :D
2.8 KiB

When looking at other designs, this seems to be the common pattern

  • General action: blue
  • Confirming action: green
  • Cancel action: orange or red
  • Possibly dangerous action: red
  • Warnings: yellow

Considering the background is very dark blue, having blue button for any general actions would still be visible.

Edit: To add, I do like the light green/blue shown in the first post in the search bar. But the yellow button next to it screams at me like it's a warning.

When looking at other designs, this seems to be the common pattern - General action: blue - Confirming action: green - Cancel action: orange or red - Possibly dangerous action: red - Warnings: yellow Considering the background is very dark blue, having blue button for any general actions would still be visible. Edit: To add, I do like the light green/blue shown in the first post in the search bar. But the yellow button next to it screams at me like it's a warning.
Author
Collaborator
Copy link

I think it is safe to assume the issue is abandoned.

I think it is safe to assume the issue is abandoned.
Commenting is not possible because the repository is archived.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
Kind: Breaking
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Maintenance
Kind: Public Relations

Design relevant outside of Codeberg
Kind: Question
Kind: Security
Kind: Testing
Kind: Web Design
Part: Color Palette
Part: Design Kit

Codeberg Design Kit
Part: Fonts
Part: Logo
Part: Navbar

Codeberg's navigation bar
Part: Themes

Gitea themes
Priority: Critical

The priority is critical
Priority: High

The priority is high
Priority: Low

The priority is low
Priority: Medium

The priority is medium
Reviewed: Confirmed

Something has been confirmed
Reviewed: Duplicate

Something exists already
Reviewed: Invalid

Something was marked as invalid
Reviewed: Wontfix

Something won't be fixed
Status: Blocked
Status: Completed

Work is complete
Status: Help wanted
Status: In progress

Work is in progress
Status: Needs feedback

Feedback is needed
Status: Stale
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Design#50
Reference in a new issue
Codeberg/Design
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?