Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Optimize build process #49
TL/DR plan of attack: relegate Jekyll to Markdown parsing and building HTML and leave assets (CSS, JS, images, and fonts) to Gulp (or equivalent task runner).
The time to
Made Mistakes Jekyll stats as of 8/23/2016:
Windows Test System:
Mac Test System:
To test build tasks, disable or remove from source and compute average time of 3 builds using
Worst case offenders appear to be resizing large amounts of images, copying images from
Decoupling asset generation tasks from main Jekyll build so they don't trigger a rebuild each time they are updated should help with development build times. Browsersync can also come to the rescue injecting updated CSS/JS to circumvent the entire Jekyll build process.
Jekyll build times comparison: