#3181 - W3CSS Compatability
-
By Adam Edington
- Added
- 10 views
| Identifier | #3181 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | W3CSS Compatability |
| Status | Closed (no changes needed) |
| Handling member | Chris Graham |
| Addon | core_themeing |
| Description | There are still certain elements missing from Composr which exist in external libraries. I know Bootstrap doesn't play well with Composr, but maybe W3CSS will.
https://www.w3schools.com/w3css/default.asp |
| Steps to reproduce | |
| Related to | |
| 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
There's a lot more to this than just adopting a particularly library that people like. These libraries tend to go out of fashion very quickly which would have a severe impact on us if we went too deep into a rabbit hole coding to the oddities of a specific library across a thousand templates, and we've learnt the hard way with a project that they can make the CSS so complex that nobody but a professional web designer can work with it. And even just upgrading to a new version of a library can be a massive overhaul, e.g. Bootstrap switched from LESS to SASS. We might do some kind of dual approach where we make some further improvements to the default theme (which will also have responsive design) and stay relatively simple, and then some very complicated official theme that has an advanced framework but is too complicated for regular users to be expected to change.