After reading this blog by Zell: http://zellwk.com/blog/wrong-about-vertical-rhythm/, I thought it would be useful to apply this "proximity principle" to Shevy. While I am disappointed that the article did not share any specific mathematics that support why this is important, I cannot deny that there are times where strictly following a baseline is not as aesthetically pleasing as the mathematics would suggest.
Thus, I am going to add proximity (Boolean) and proximity-factor (Float) to the default $shevy map. The first will turn proximity mathematics on or off, likely defaulting to off. The second will be used to determine what percentage of the base-spacing to apply. For example, if a factor of 0.75 is provided, then the spacing between content elements (and possibly headings, will see if proximity is useful there as well) will be 75% of what it would otherwise be. This should enable the user the ability to fine tune the spacing of their typography.
After reading this blog by Zell: http://zellwk.com/blog/wrong-about-vertical-rhythm/, I thought it would be useful to apply this "proximity principle" to Shevy. While I am disappointed that the article did not share any specific mathematics that support why this is important, I cannot deny that there are times where strictly following a baseline is not as aesthetically pleasing as the mathematics would suggest.
Thus, I am going to add
proximity
(Boolean) andproximity-factor
(Float) to the default$shevy
map. The first will turn proximity mathematics on or off, likely defaulting to off. The second will be used to determine what percentage of the base-spacing to apply. For example, if a factor of0.75
is provided, then the spacing between content elements (and possibly headings, will see if proximity is useful there as well) will be 75% of what it would otherwise be. This should enable the user the ability to fine tune the spacing of their typography.