Feature Proposal: Adopt SASS

Motivation

Current CSS is mostly handcrafted, i.e. we aren't using any preprocessor such as SASS or LESS. This leads to a lot of redundant css with properties not being shared among skins and extensions.

Description and Documentation

This will also change the way skins load their css into the page, i.e. how PatternSkin is customized: instead of cascading different css files individually will there be a SASS compiler generating a derived single css file from the skin's base definitions together with any user changes such as modifying the colorset or the icon set.

Examples

Impact

• BuildContrib
• DefaultSkin
• PatternSkin
• NatSkin
• JQueryPlugin
• and mostly any extension coming with css

Implementation

-- Contributors: MichaelDaum - 19 Nov 2015

Discussion

This proposall spinned off from AdoptACSSFramework. See some of the discussion there now valid here.

-- Main.MichaelDaum - 19 Nov 2015 - 12:50

Now that we've got CSS variables this proposal might not be required anymore. Instead CSS variables should be used in a structured way.

-- MichaelDaum - 20 Jul 2021

Commenting is disabled while not logged in