#3362 - Themeing improvements in v11 (idea staging issue)
-
By Chris Graham
- Added
- 3 views
| Identifier | #3362 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Themeing improvements in v11 (idea staging issue) |
| Status | Completed |
| Tags |
Roadmap: v11 (custom) |
| Handling member | Chris Graham |
| Addon | core_themeing |
| Description | This issue links together a number of major initiatives to improve themeing and upgrading in v11. |
| Steps to reproduce | |
| Related to | #3359 - Extended theme options #3360 - Theme maintenance and testing tools #3361 - Improving CSS and JavaScript maintenance #3344 - Improved template choose-to-edit selector #2966 - Re-design icons using flat design #2912 - Hybrid responsive theme #508 - Support Content Security Policy #1753 - Improved cross-file editing #1562 - Replace EditArea with Ace Editor #3351 - Installer and Setup Wizard simplification #3367 - Prepare presentation for a review of our design #318 - Transfer theme options (like fixed-width) to theme.ini |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
1) Make new official themes, esp Bootstrap theme (#3206)
2) Make amazing WYSIWYG editing of themes (#2970)
Why?
i) We want to fix things that limits THIRD PARTIES making/maintaining themes.
ii) We don't want to make major changes to Composr themeing infrastructure AFTER making new themes, as we'd need to re-do our work.
iii) We feel improving core infrastructure is more important, because it's more of a one-off investment, than the ongoing investment needed to make and maintain a set of themes.
iv) A certain proportion of users will always want to make their own themes. So by improving core architecture we're serving a broader set of users than making new themes would.
v) Whenever we improve core infrastructure to make many complicated interconnected improvements, it tends to get us to a point where we can see the next set of innovations more easily.
So v10 is step 'a', and v12 might add some new official themes (or we might draw in some third party themes into the Setup Wizard).
As for "amazing WYSIWYG editing of themes", that's going to require an enormous effort, so it's going to require someone's full-time passion, or a large investment.