OOP-like CSS component definition library including features of fluent API, Dependency Injection etc.
I consider whether I should still use Sass as a preprocessor. The feature that allows us to handle parent selector in 3.3.0 rc will come back as new Selector Functions in 3.4.0.
- HTML/CSS Class Naming Convention for Scalable/Modular CSS.
- Naming Convention for Sass library
- Map getter & overridding
- A flexible component definition
- Polymorphic placeholder & mixins
- Generating decoupled color schemes
- Typed value factory & validator using Map (with descriptor)
- Passing/Getting property value(s) into/inside mixins/functions
- Dependency Injection into Mixins
- Resolving component dependencies (Improved)
- Creating new Scope & Instance Variable/Method (Another Example, The easiest way)
- Placeholder Factory(Mixin) based on the argumetns
- Automatically reducing duplicated declarations
- Back-slash as the namespace separator in HTML/CSS
- The Way to Define Robust CSS Module/Component
- Element-type-based Conditional Styles Inside Mixin
- placeholder-exists()
- Pseudo
undefined
value - OOSASS: Writting OOP-like Sass/CSS Component
- CSS/Sass: Robust/Scalable Layered CSS Architecture(Element Property, Aggregation vs Composition)
- IOCSS: Component with the Structural Interface
- OOP-like component definition (encapsulation, extending, polymorphism)
- OOP-like property handling
- Fluent API
- Dependency Injection
- Conflict proof mixins & functions
- Accessor/Mutator/Listener, Custom type hinting (as ideas)
- Sass 3.4.0+ (considering support of SassC)
- or considering of use of AbsurdJS (better than Sass, I feel)
- Core
- Configuration (storage)
- Object
- Container
- Injection
- Provider
- Type (Constraint), Validator
- Ruleset (placeholder definition)
- Accessor/Mutator
- Injection