twitter/bootstrap — Issue #957: @variable implementation needs improved documentation
Author: mralexgray
Created: 2012-01-10 15:03:39+00:00
State: open

I think there exists some confusion / mental stumbling blocks around the fundamental idea of @variables (and mix-ins, for that matter) in CSS frameworks such as LESS. One, and I'm sure many do.. think of @variables as _runtime_ parameters.. For example….

< OK.. I have a 2-column fluid layout. There is a new @sidebarWidth _variable_. That's something I could probably change on _this page's_ stylesheet.

No. This requires a recompile. Why? Not sure. Doesn't seem very variable to me.

This mechanism is glossed over in both the Bootstrap docs AND the LESS docs, and IMO could simply use some expanded explanation / direction as to how and why to use these features effectively.

This is sort of a "big-picture" "issue"… but take someone like me… I "get it" and i still struggle with how to implement these language abstractions to achieve practical results.. Lowering the bar of entry for these useful constructs is an exercise in empathy - in that once you get it, you get it… and if you don't - you really don't. Bootstrap is all about making this stuff useable, and I just think @variables and mix-ins need a more fundamental explanation / examples to promote adoption.