Theming options available in admin and user theming should share a component
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
With great pleasure I recognized the new user specific theming options. (Well, I'm not certain how new they actually are..) However, I wonder why you eg. use a different color picker in user theming than in admin theming panel.
Eg when I want to set a certain RGB code as background color, I can do it in admin panel but user panel is not capable of doing so. Here you invented the wheel twice and created a new / different color picker instead of sharing a color picker component.
The other way around, when setting background in admin theming panel, it would be great to have the same advanced options offered in user theming. Eg. why do you offer 15 backgrounds out-of-the-box for user theming, but in admin theming I can only reset to that awful clouds background image.
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
The issue names no files, tests, or entry points, so first locate the admin and user theming implementations and compare their color-picker and background-option paths. Done would require an agreed shared component and equivalent theming capabilities, followed by coverage for both interfaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100