d72:1382435856 wrote:
As I dug deeper I discovered how badly those templates are connected to functionality or to be more precise - presentation layer is so mixed up with functions and logic that it can't be done easily.
I would disagree, I think the abstraction in DokuWiki is okay (although not perfect). Although I understand that it would be best if a template could change all of the markup, the HTML and CSS is generally very semantic and easy to handle.
The trouble is that CSS frameworks are usually not very semantic and unfortunately require you to have a certain markup. IMHO it's equally bad to need a certain markup (e.g. Bootstrap) than to need a certain CSS structure (e.g. DokuWiki). Ideally you should be free to determine both. But changing the CSS is usually much easier than changing the markup...
d72:1382435856 wrote:
At the moment Dokuwiki is so perfused with XHTML that not only tpl folder contents needs to be changed but many other files also to use freely any design sliced to HTML5.
I don't understand what you mean. The difference between XHTML and HTML5 are not important at all in this context. I don't see any problems with using HTML5 in DokuWiki. Do you have any specific example?
d72:1382435856 wrote:
we ended up building our own templating engine on top of Dokuwiki.
We keep everything as is for the editing mode and we will build a new readers view that uses only Dokuwiki's content data files + some related metadata.
That sounds very interesting. It would be great if you could share that when you're done.
I have had another idea how it's much easier to use Bootstrap (or any other CSS framework) in DokuWiki. The latest release (currently "only" a release candidate, soon to be stable) includes a LESS compiler. With LESS you can simply inherit from a Bootstrap class. Just a quick example:
/* make all buttons use the default bootstrap button: */
input.button {
.btn;
}
/* make the search button use the info bootstrap button: */
#dw__search input.button {
.btn-info;
}
