Revamp themes section #60
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "xeruf/awesome-gitea:master"
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?
@ -156,1 +145,3 @@
* [theme.park](https://github.com/gilbN/theme.park/wiki/Gitea) - A theme suite for Gitea.
* [Modern](https://codeberg.org/Freeplay/CSS-Styles/src/branch/main/Gitea#gitea-modern) - Changes the layout for a more modern look. Usable with other themes that only change colors.
* [theme.park](https://docs.theme-park.dev/themes/gitea) - A theme suite that includes Gitea
* [Adaptive GitHub](https://github.com/pat-s/gitea-github-theme) - GitHub-inspired Gitea theme with dark and light styles
Thanks.
I am not sure if all theme authors would agree to such naming changes - being the author of the
gitea-github-theme
I'd prefer to stay with the previous name rather than calling it "Adaptive GitHub".I agree the "Gitea" repetitions might be worthless here but outside of this list the Gitea term is important within the standalone repos.
Yes, It is important within the standalone repos, but we do not have to label the themes as they are in the repos
This list should be user-friendly with expressive names - having two themes named "Github" really does not help (and adding a 2 also does not fit with the original repo), and one distinguisher is that yours is adaptive in the sense that it has light and dark schemes.
We do not but we should maybe check back with the authors instead of changing the names substantially.
Yes, adding a "2" is also not a super solution but closer to the upstream name than putting a new word in front of it.
I am not sure if we should put that opionions on theme names here.
OTOH it is also not really worth spending so much time to discuss this as it's just a list. We should use this time and energy discussing the general implementation of user-defined themes and the user instructions.
So if you have a really strong opinion that this is better than before, I won't block it but maybe my arguments can be considered in some way :)
per #60 (comment)
Maybe making it a table with screenshots if possible?
d96194054a
to1c1625d7d3
@xeruf Thanks, I think using the repo slugs is a good unbiased solution. Maybe we should do this for all even?
@freeplay
Could be nice but it's quite some work - do you want to help here?
@freeplay nice idea, but gitea does not seem to support markdown tables by default, see https://gitea.com/xeruf/awesome-gitea/src/branch/themes-table
Anyways, should be updated to your liking now @pat-s :)
Now also supercedes #56 :)