Add External Pipeline for Marketing Site
Problem to solve
Local development of this repo is slow and cumbersome. Production build times for Middleman are also slow.
Proposal
Let's move frontend asset builds out of Middleman and into an external_pipeline
. This will allow Middleman to do what it does best - compile the HTML.
For our external_pipeline
, lets have it complete the following tasks:
- preprocess scss
- minify css
- minify js
- bundle js
- sourcemaps
- copy web fonts, icons
- image resizing and processing* (depending on speed)
- browser reload (local dev) (local dev)
What does success look like, and how can we measure that?
Faster local development for developers.
Faster deployment times. Reduced publishing time for blog, handbook, and marketing webpages.
Iterative Approach
- Process Stylsheets with Webpack first, introducing build to system
- Monitor and fix edgecases
- Add javascript bundling to Webpack second
- Monitor and fix egecases
- Migrate rollup to Webpack for vue component bundles
- Monitor and fix edgecases
- Add image process to Webpack
cc @gl-website
Edited by Lauren Barker