Codeberg/Community
54
325
Fork
You've already forked Community
12

Place for the Coderberg users / Community to publish custom themes for the Codeberg frontend #1131

Closed
opened 2023年08月10日 20:14:28 +02:00 by GamePlayer-8 · 4 comments

Good evening,

Just a suggestion - a place where users would publish custom CSS for Forgejo / Codeberg and share with other users.

May look like a list with upvotes / downvotes + report/install buttons and will require signing with through Codeberg.

⚠️ This suggestion may require rewriting the way of how Forgejo loads themes.

<!-- NOTE: If you wish to report a security issue, please send an email to contact@codeberg.org (for Forgejo, see: https://forgejo.org/.well-known/security.txt) instead. Thank you. Welcome to the Codeberg Community Tracker. This is the place central for bug reports, feature requests and feedback. If you are not sure whether you should use trackers of other Codeberg Projects, then you should use this one. Please keep the following in mind: - Please check https://github.com/go-gitea/gitea/issues or https://codeberg.org/forgejo/forgejo to confirm that your issue hasn't already been reported. Codeberg uses Forgejo (referred to as the "upstream"), which is based on Gitea. - This is *not* a customer support hotline. We are volunteers with limited time and resources, and we consider you, the reporter, to be one as well. Please maintain a courteous and respectful tone, and provide as much information as possible, so that we can work together. - We may take a while with resolving your issue. Your work is still important, even if we cannot acknowledge it directly. Thank you for reporting your findings and giving feedback on Codeberg. ## FAQ ### What happens after I open an issue? Separate contributors will use your issue to communicate with each other. It will also be used to provide updates. There is a decent chance that we will ask you for additional feedback or information. ### sing_up: I noticed a typo in the URL of the registration page. This is an intentional, temporary, surprisingly effective change that helps us against spam. Nice catch! ### I want to contribute to Codeberg! That's awesome, thank you! Take a look at https://codeberg.org/Codeberg/Projects and this tracker, we have a variety of both technical and non-technical tasks that we need help with. --> Good evening, Just a suggestion - a place where users would publish custom CSS for Forgejo / Codeberg and share with other users. May look like a list with upvotes / downvotes + report/install buttons and will require signing with through Codeberg. ⚠️ This suggestion may require rewriting the way of how Forgejo loads themes.
Member
Copy link

I think Codeberg's community would be open to the introduction of new themes by sending pull requests to https://codeberg.org/codeberg/forgejo

What you're describing sounds somewhat interesting, but as you mentioned, it would require extensive changes to Forgejo which may be undesirable in other applications.

I think Codeberg's community would be open to the introduction of new themes by sending pull requests to https://codeberg.org/codeberg/forgejo What you're describing sounds somewhat interesting, but as you mentioned, it would require extensive changes to Forgejo which may be undesirable in other applications.

Slightly off-topic, but I'd love to have, for the sake of making an example, Catpuccin. I would also advocate for having it included in Codeberg, like other themes (but I'm not sure who maintains it - so I can't ask them): https://github.com/catppuccin/codeberg

Do we think that "established color schemes" (e.g. that one, or some sort of a solarized dark theme, etc.) would be something that Forgejo would be open to approving?

P.S. It was mentioned somewhere (possibly verbally) that if we allow that on the fork itself, we would have the expectation that the theme authors would contribute to adding support for their own themes from version to version or get removed at a later version.

Slightly off-topic, but I'd *love* to have, for the sake of making an example, Catpuccin. I would also advocate for having it included in Codeberg, like other themes (but I'm not sure who maintains it - so I can't ask them): https://github.com/catppuccin/codeberg Do we think that "established color schemes" (e.g. that one, or some sort of a solarized dark theme, etc.) would be something that Forgejo would be open to approving? P.S. It was mentioned somewhere (possibly verbally) that if we allow that on the fork itself, we would have the expectation that the theme authors would contribute to adding support for their own themes from version to version or get removed at a later version.
Member
Copy link

I believe many members of the Forgejo community would also be open to the introduction of new themes. We do need to consider how much additional technical overhead will be incurred by testing and maintaining themes that are added to the codebase, as anything that's included with Forgejo should work perfectly out of the box.

I believe many members of the Forgejo community would also be open to the introduction of new themes. We do need to consider how much additional technical overhead will be incurred by testing and maintaining themes that are added to the codebase, as anything that's included with Forgejo should work perfectly out of the box.
Owner
Copy link

Codeberg/Documentation#114 (comment) is basically how custom themes could work. The maintenance is the important aspect, I doubt that sharing random snippets works fine.

Some apps have many themes, but when you click through them and they're all basically broken, you simply stop using any custom theme (or you are bored too much). I went through this with Geany and Adminer, for example. And Atom (IDE).

https://codeberg.org/Codeberg/Documentation/issues/114#issuecomment-998493 is basically how custom themes could work. The maintenance is the important aspect, I doubt that sharing random snippets works fine. Some apps have many themes, but when you click through them and they're all basically broken, you simply stop using any custom theme (or you are bored too much). I went through this with Geany and Adminer, for example. And Atom (IDE).
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

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.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

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.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
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/Community#1131
Reference in a new issue
Codeberg/Community
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?