This document discusses using Gulp for automation tasks in Sitecore projects. It provides an overview of Gulp and how it compares to Grunt. Gulp can be used to automate publishing processes and compilations for Habitat, a modular Sitecore solution. Specific Gulp plugins like gulp-msbuild and gulp-watch are useful for ASP.NET development. The document demonstrates how Gulp works with an example.
2. WHAT IS GULP?
Tool for automatization tasks
Running on node.js
Highly customizable – over
2000 plugins available
Very flexible
3. SOMETHING
SIMILAR?
Precursor of Gulp
Still good and widely used
tool
More than 5000 plugins
Large and still growing
community
Recently gives a way of
leadership to Gulp
4. QUICK COMPARISION
Grunt focuses on configuration, Gulp focuses on code
Grunt has lot of commonly used heavy tasks
Gulp provides platform to connect lightweight tasks, built by community,
between each other
VS
5. HOW CANWE USE GULP WITH SITECORE?
Automatization of publish process for solutions with many web projects (Habitat)
Automatization of publishing for changes in e.g. MVCViews, CSS, JavaScripts
Automatic compilation of Sass/Less, CoffeeScript, etc.
6. SITECORE HABITAT PROJECT
Sitecore solution example built on a modular architecture
The architecture and methodology focuses on:
Simplicity - A consistent and discoverable architecture
Flexibility - Change and add quickly and without worry
Extensibility - Simply add new features without steep learning curve
In few words:
Total split of solution into three separate sections: Features, Foundation &
Project
Features are separated from themselves so they can be used in other projects
8. USEFUL PLUGING FOR ASP.NET DEVELOPER
gulp-msbuild – running MSBuild commands
gulp-watch – file watcher that can make action just as file is changed