The arch-green theme or dark theme should match with the codeberg colour scheme. The current colour scheme's main colour is the green colour from gitea. Meanwhile, the taskbar/topbar is blue in colour. I would like to see blue instead of green.
Or
Design a new dark theme for Codeberg.
image
Move Codeberg CSS (navbar) to default theme #392
PR welcome
Initial work is done with Codeberg/build-deploy-gitea@4b68de7caa. Close issue?
hehe no ... #434 ...
I'd prefer to revert the colours in upstream theme (this would turn arc-green green again) and create a true dark codeberg theme (maybe copy arc-green, replace colours and call it codeberg-dark or something).
So this is about that job, the other issue about properly fixing the upstream colours.
Or do you think it's good to globally override colours to have all-blue? Would be limiting to further themes, I guess.
I personally think not having a "colored" navigation bar in a dark theme makes more sense as it's somewhat visually disturbing, be it blue or green (unless desaturated/darkened. but even then it still feels smoewhat out of place).
One could probably use #292d39 too, but this is just a sample.
Hmm, the arc-green colour scheme would actually be completely different, probably looks like on this instance https://git.disroot.org/ ... the main issue with the colours is that we do override them for the Codeberg navbar, because we have a custom stylesheet in place.
The main idea behind this is to have the Codeberg colour scheme in all the themes (or it was probably simply put in place with the light theme in mind since theming is not the most obvious setting).
We could say that we don't care about having exactly matching Codeberg colours (that is: https://codeberg.org/Codeberg/Design/wiki/Branding#palette this palette), modify only the default Codeberg theme to include our custom navbar and let all the other themes be as-is ... that might be the best solution if we don't want to force the blue navbar for every theme.
It would certainly work against having a Corporate Design for Codeberg since many users would not see it for years after they changed settings, but since this setting is only available for registered users who are then on Codeberg anyway, we could probably live with this and let them choose their prefered theme - with consistent colours and no overrides.
I understand the rationale behind the decision but unfortunately things don't look that great in action. The blue navbar seems somewhat out of place even in the light theme, and more so in the dark theme (and the color isn't the only issue, the very narrow height compared to other elements and lack of shadow also seem to contribute to it looking somewhat out of place).
And well I think overriding themes like that would render theming kinda meaningless in a bigger picture, so having a custom default theme would indeed make more sense to me (although I would probably still not be in favour of the current navbar even for the custom theme, as I believe the default theme should look more consistent).
Maybe instead of coloring the whole navbar, we could use the colored icon to put an emphasis on the branding? (I think that's pretty much how apps/websites deal with dark/light theme variants these days, as colors can not be used extensively without creating conflicts).
I agree to moving the blue navbar to the default theme. Theme diversity is on my backlog, I didn't yet consider the navbar issue, but of course, this would have become a bigger issue anyway.
To the colour: I do like the navbar in the default theme and I think it will be kept anyway since this could be considered as Codebergs branding, but have a look at Codeberg/build-deploy-gitea#17 where there was a discussion about a redesign and maybe add some ideas there if you see room for improvement ...
Renamed the issue to reflect the actual ToDo, creating a dark theme fitting the Codeberg theme would be another cool thing - but after we managed a cool way for theme contributions.
A decision left for here is how much of the Codeberg CSS to move from the Overrides to the themes.
Some fixes might be useful in every theme to make the defaults work (i. e. with too many icons in the navbar), but others would be annoying to work around (someone might develop a theme for Gitea to see it screwed up by Codeberg's custom CSS).
Is there any tool that allows to try out different colors with gitea theme?
@mray if you wana play around i suggest user css and Stylus - that's how I shape websites to my personal needs & test :D
Thi is related: Codeberg/Design#50
It reads to me as if this discussion is solved and hence could be closed?
I don't think it's completely done yet.
Nearly done now. Only minor patches remain inside codeberg.css. Blue navbar colour is no longer enforced in all themes, and we can improve and style themes from here if necessary.
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
Something is not working the way it should. Does not concern outages.
Errors evidently caused by infrastructure malfunctions or outages
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
Please join the discussion and consider contributing a PR!
No bug, but an improvement to the docs or UI description will help
This issue or pull request already exists
New feature
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
An issue directly involving legal compliance
involving questions about the ToS, especially licencing compliance
Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
Things related to Codeberg's external communication
More information is needed
This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
Related to Forgejo. Please also check Forgejo's issue tracker.
Migration related issues in Forgejo
Issues related to the Codeberg Pages feature
Issue is related to the Weblate instance at https://translate.codeberg.org
Woodpecker CI related issue
involves improvements to the sites security
Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
No due date set.
No dependencies set.
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?