Page History
Purpose
Goal
Front-end developers have sophisticated build pipelines that make them productive and help them build high-performance websites. It should be easy for them to use them with magnolia so that:
- They can be quickly productive
- They can create high-performance websites
- They like magnolia
- We can use this to generate marketing buzz on the intersection of frontend dev & CMS.
Proposal
Or - Hooks for frontend build tool integration - with examples.
This is a placeholder for now - where do we put that our build pipeline has to integrate with front end techs like
Front end dev typically do not want to learn freemarker to process css but would prefer to use their existing skill sets.
- LESS
- SASS
- Grunt / Gulp
- Browserify
- Minification
- Concatination
- Coffeescript compilation
Implementation
Maybe this already exists?
I know people on the forum have found a way to use the Vaadin SASS parser for the front-end. But i dont think thats the ideal approach necessarily.
TBDLESS, Sass, Browserify, grunt etc.