You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rave.apache.org by Apache Wiki <wi...@apache.org> on 2012/04/26 22:40:17 UTC
[Rave Wiki] Update of "ArchitectureTopics/FrontendCustomization/BootstrapCustomization" by StanDrozdetski
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Rave Wiki" for change notification.
The "ArchitectureTopics/FrontendCustomization/BootstrapCustomization" page has been changed by StanDrozdetski:
http://wiki.apache.org/rave/ArchitectureTopics/FrontendCustomization/BootstrapCustomization?action=diff&rev1=1&rev2=2
- This proposal addresses the strategy of customizing [[http://twitter.github.com/bootstrap/|Bootstrap]] for Rave so that:
+ This proposal addresses customizing [[http://twitter.github.com/bootstrap/|Bootstrap]] for Rave so that:
- * Rave is insultated from changes in future Bootstrap version (or, at least has a sensible upgrade path)
+ * Rave is insulated from changes in future Bootstrap versions (or, at least has a sensible upgrade path)
* Changes to Bootstrap definitions are easy to do
=== LESS setup ===
- * rave
+ The proposal is to create a rave.less file that contains:
+ * reference to /v2.03/bootstrap.less (@include, using LESS syntax)
+ * bootstrap.less pulls in the "stock" Bootstrap definitions
+ * versioning Bootstrap files in a separate folder lets you swap in a new version with ease
+ * Rave-specific customizations
+
+ A Rave integrator would then modify/append LESS definitions in rave.less to get their version looking the way they want.
+
+ === LESS compilation ===
+ The plan is to have server-side complication of the LESS files; as far as your Rave instance is concerned, it will be consuming a single (minified) CSS file – rave.css in the diagram above.
+
+ The ability to do client-side compilation (for quick troubleshooting on a development server) can be easily added.
+