Static site compiler built around swig
A static site compiler for grunt based on swig templates
This plugin requires Grunt
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-swig --save-dev
In your project's Gruntfile, add a section named
swig to the data object passed into
swig:development:init:autoescape: truedest: "www/"src: '**/*.swig'generateSitemap: truegenerateRobotstxt: truesiteUrl: ''production: falsefb_appid: '1349v'ga_account_id: 'UA-xxxxxxxx-1'robots_directive: 'Disallow /'sitemap_priorities:'_DEFAULT_': '0.5''index.html': '0.8''subpage.html': '0.7'
Grunt Swig will loop through files listed in
source/index.swig. It will look for a
source/index.json and add it to
the rest of the variables provided in
swig:development or in
global.js, and then run swig
source/index.swig saving the output to
You can also provide context, for example
swig:development:blue which will
perform the same actions above, but after process the JSON it will also expand
the variable list with
source/index.blue.json and provide the variable
context to the rest of the swig template.
The siteUrl is used to build a sitemap. Right now all the other elements are hard coded, eventually this could be set in the config object.
The 'sitemap_priorities' will set custom priorities based on the page name when building the sitemap. The first item 'DEFAULT' will be the default priority used if a page name is not explicitly set. In the above example the page 'index.html' would be given priority of '0.8', 'subpage.html' would be given a priority of '0.7', and all other pages would get a priority of '0.5', You need to give the relative path to the output html file for this to work.
Path and base name of the source template file are available in
the path and
tplFile.basename for the basename.
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.
ANYONE RUNNING 0.1.1 IS ADVISED TO UPGRADE TO 0.1.2 - There is an error in 0.1.1 package.json