Hi Andreas. I agree it would be very nice to just purchase a theme on themeforest.comand install it on XWiki. But I have never purchased a theme like that. What do you obtain? A set of CSS files + an HTML template? A file overwriting all bootstrap variables? The sources of a Boostrap fork?
If is is a CSS file, then probably the path URL for images will not work with the XWiki system (I mean /xwiki/bin/resources ), so you will have to modify it manually. If the reseller only provides a bootstrap variables file and some images, in a standardized package, then we could consider an automatic integration. If not, you will always need to spend some time to adapt your purchased theme to the XWiki mechanisms. Guillaume 2014-05-01 11:34 GMT+02:00 Andreas Hahn <[email protected]>: > Hi, > > I think it won't hurt to add an outsiders pov to the discussion > although I'd guess it may sound a little bit provoking ;-). > > Consider dropping support of all Xwiki specifc theme / color editors > in favor of an as-tight-as-possible developer-level integration of twitter > bootstrap. > > Bang ! > > The reasoning for this is that no matter how much efforts and brains you > will put into doing skins and colors a la xwiki you will never even come > close to an amount of options that is offered by 3rd party commercial and > free template vendors (that build on bootstrap). > > There are offers like themeforest > http://themeforest.net/search?utf8=%E2%9C%93&term=bootstrap > where you can find hundreds of theme templates based on bootstrap. > For a designer / developer who tries to build individual customized > front ends with very little effort this is a buffet of possibilities and > inspiration. > > Given a better (=deeper) integration with xwiki might break ground > for new use cases outside the 'traditional' wiki world. And xwiki users > would benefit > from an almost-as-easy individual site customization as other well > recognized platforms offer > (Wordpress, Joomla, Drupal, ...) > > IMHO Bootstrap is pretty much a safe choice in terms of long term support > for the front > end as java is as the programming language for the backend. > > And from my personal experience using themeforest / bootstrap as a > development > resource in a recent project: It's been fun, it's been effective, result > is good looking. > > Enjoy > > Andreas > > > > Am 16.04.2014 14:08, schrieb Ecaterina Moraru (Valica): > > Hi, >> >> With the new Flamingo skin and with the design investigations done on >> existing Applications, there are more and more questions related to: >> * how will the applications be displayed on the new skin, while conserving >> the same look on the old skin; >> * how much an application should preserve previous functionality and how >> many efforts are we putting in adapting the functionality for new layouts; >> * when do we create a new application vs. when do we retire one; >> * etc. >> >> This question applies in general to applications and you can also read >> some >> discussions about applications like Panels [1] or ColorThemes [2]. >> >> In this thread I want to discuss some variants related to application's >> presentation: >> http://design.xwiki.org/xwiki/bin/view/Proposal/ApplicationPresentation# >> HVariants >> >> I am interested in our position regarding this topic and if we have like a >> 'standard' solution or if the answer depends on the application in cause. >> >> Thanks, >> Caty >> >> [1] http://design.xwiki.org/xwiki/bin/view/Proposal/PanelsImprovements >> [2] http://design.xwiki.org/xwiki/bin/view/Proposal/ColorThemeforFlamingo >> _______________________________________________ >> devs mailing list >> [email protected] >> http://lists.xwiki.org/mailman/listinfo/devs >> >> > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
