#set($keywords = "wiki,$!doc.getTags()") ## We verify that we don't display RSS feeds on the login page since it causes problems if these feeds are ## protected. In addition it makes the login redirect to the feeds page in some cases. #if($doc.fullName != "XWiki.XWikiLogin") #end
All those skin are simply created by using the appropriate derived skin of bootstrap taken for the purpose of this demo from. These CSS were downloaded and works AS IS. Here is the sample code used to override style.css:
@import "$xwiki.getSkinFile('css/amelia.min.css', true)"; @import "$xwiki.getSkinFile('css/bootstrap-responsive.min.css', true)"; @import "$xwiki.getSkinFile('css/font-awesome.min.css', true)"; @import "$xwiki.getSkinFile('bluebird.css', true)";
For this to be, the HTML generated by XWiki need to be adapted to the markup required by bootstrap. Doing so once could work, but will link us to bootstrap. This is why I suggest we investigate a way to decouple the HTML generated from the purpose of this HTML (having a button). Doing so will give us the flexibility to adapt to any framework. It will allow extension developer to build unified UI for their extension, which will be in favor of a uniform design of the UI over a given wiki. I also suggest that the HTML generated by the rendered be as well adaptable, and moreover that we develop more macros to easily benefit of formatting style in XWIkiDocument without needing complex (% %) syntax.
I hope this demonstration will convince you of the great benefit of this proposal.
A discussion is open on the mailing list .