This is the old issue tracking system for DokuWiki. Issues can not be added here anymore. Pleaser refer to for the new system.


FS#2316 - Using LESS for CSS

Attached to Project: DokuWiki
Opened by Andreas Gohr (andi) - Tuesday, 23 August 2011, 14:40 GMT
Last edited by Christopher Smith (ChrisS) - Friday, 02 August 2013, 22:13 GMT
Task Type Feature Request
Category CSS, XHTML, JS, Browsers
Status Closed
Assigned To Adrian Lang (adrianlang)
Operating System All
Severity Low
Priority Normal
Reported Version none
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No


We're working on a new default template and had some ideas about improving the CSS handling before, so it might be a good idea to include a more powerful CSS preprocessor.

LESS seems to be the current tool of choice.

A PHP implementation is available at - it seems clean and easy to integrate.

Adding a semantic grid framework as described in could ease the creation of modern, responsive templates even more.
This task depends upon

Closed by  Christopher Smith (ChrisS)
Friday, 02 August 2013, 22:13 GMT
Reason for closing:  Implemented
Comment by Anika Henke (ach) - Wednesday, 24 August 2011, 08:20 GMT
I generally don't like CSS preprocessors, but I'll have a look at LESS...

But we definitely don't need a grid framework, because we don't have a grid! All we have is the main content (which never has any columns inside it, unless you're using certain plugins) and a sidebar - I wouldn't call that a grid.
Comment by Adrian Lang (adrianlang) - Wednesday, 24 August 2011, 08:54 GMT
Currently we use a CSS preprocessor as well, and LESS would just be more powerful and quasi-standard.
Comment by Anika Henke (ach) - Wednesday, 24 August 2011, 20:32 GMT
Yeah, I know. But currently we're only using it for two purposes, while others will add more functionality (which is not a bad thing in general).

Another thing is: I planned to write an email to the mailinglist with new ideas regarding the style.ini file (and the not very ideal way it is handled currently). But Andi said I should wait until the next release, because there's already too much going on. That means 1) a change to a different CSS preprocessor should not go into the next (October) release and b) as there are so many issues (and solutions) to the style.ini problem, LESS could solve that as well (or at least a part of it). But that should be discussed properly before (but not before the release).
Comment by Adrian Lang (adrianlang) - Wednesday, 31 August 2011, 08:34 GMT
Comment by Myron Turner (turnermm) - Sunday, 22 April 2012, 11:39 GMT
I just took a look at the LESS web site and its web site, controlled by LESS, is not fully compatible with Chrome.
Comment by Guy Brand (bug) - Tuesday, 30 July 2013, 16:38 GMT Comment by Matthias Schulte (lupo49) - Friday, 02 August 2013, 21:41 GMT
Could be closed as the PR is merged?