Improved theming to fully replace legacy themes
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
The old custom theme mechanism was deprecated quite a while ago in favor of the theming app but we still keep it around since there are a couple of common cases that are not yet covered by the theming app approach:
- Replace templates (while this is quite common, I'm unsure if we want to continue supporting it)
- Replace icon files (https://github.com/nextcloud/server/issues/27423)
- Replace translations
My initial idea would be that we could handle this in addition to https://github.com/nextcloud/server/issues/15815 and allow any app to register for handling theming. That way if a custom theme is required with additional customization such as changing image/template paths or translations we could add hooks to let a separate app handle those then.
cc @nextcloud/server-triage What do you think about that, especially if we should continue supporting those individual possibilities?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the legacy custom theme mechanism and the theming app, then read issues #15815 and #27423 for related context. A complete proposal should decide whether apps can register theming handlers and whether template, icon, and translation replacement remain supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- design, frontend, internationalization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100