Since a while I have found myself enjoying building sites based upon Twitter's Bootstrap. More and more projects are basing their styling on it, and while the default is rather too common these days, it does look a lot nicer than plain old CSS straight out of the browser.
I plan to utilize Bootstrap for the new Wicket site design. The site design doesn't have anything to do with Wicket proper, but I do think that the examples project can use a face lift in the light of Bootstrap and a new site design. A couple of reasons to provide bootstrap as a Apache Wicket component: - tied to our own release schedule, so we can be sure it works and is properly licensed - ability to use it in our own examples - many requests for a better default theme for Wicket will suddenly silence - nice showcase for our pick of jquery as base Wicket ajax - nice showcase for resource aggregations - looks pretty decent (did I mention that already?) - prevent fragmentation in the wicket bootstrap universe (one integration to rule them all) There are a number of integrations already with Wicket and bootstrap: - https://github.com/l0rdn1kk0n/wicket-bootstrap - https://github.com/tdziurko/wicket-bootstrap-navbar - http://www.david-robson.co.uk/?p=155 Questions: - does anyone object to creating a wicket-experimental/wicket-bootstrap project (we can always choose to abandon it—I'd support it on github in such a case) - if so, should we ask to adopt https://github.com/l0rdn1kk0n/wicket-bootstrap as a base to work on or roll our own (it does require some work IMO)? - if not so, and I still want to revamp wicket-examples using bootstrap, does anyone object to rolling bootstrap directly into wicket-examples (with the risk of folks asking for the integration to become proper)? - to support theming (http://bootswatch.com) less css integration is required, should we provide a development mode integration with wro4j for less css? (I'd suggest using the maven plugin for deployment) Martijn
