A Grunt templating plugin to generate static HTML files from given pages, templates and partials written in either pure HTML, doT.js, or markdown.
Stencil is a Grunt plugin for templating that generates static HTML files from given components. Stencil provides the following:
See the Wiki pages for full documentation.
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-stencil --save-dev
A more detailed explanation of all options can be found in the Wiki.
Each of the following is optional.
An object that specifies the template settings that are passed to the doT compiler (see doT.js).
Initial environment seen by all compiler, doT.js sees it as
it. This environment is for each file with their header fields.
A String value specifying the location of all templates. When specified, this will allow to call templates in pages' meta data without the full path to it (the specified
templates will be prepended).
A String value specifying the location of all partials. When specified, this will allow to call partial
include functions without the full path (the specified
partials will be prepended).
String | RexExp
A String value specifying the characters to search for when separating meta data from the content of a file. By default, the JSON header of a file is considered to end after the first blank line in the file.
An elaborate list of examples can be found in the Wiki.
In your project's Gruntfile, add a section named
stencil to the data object passed into
gruntinitConfigstencil:options:// Task-specific options go here.your_target:// Target-specific file lists and/or options go here.
Grunt's rules for defining target and destination files apply, but care needs to be taken to make sure each input page maps to a single output file.
In this example, doT's it object is used to specify the location of script files and the main title of all pages; and the location of partials and templates is given. All pages in
pages/ will be compiled to
.html files in
gruntinitConfigstencil:main:options:env:title: "Stencil"partials: "content"templates: "templates"files:expand: truecwd: "src/pages/"src: "**/*.dot.html"dest: "tmp"ext: ".html"flatten: true
In lieu of a formal styleguide, take care to maintain the existing coding style. Lint and test your code using Grunt. Please ignore W092 errors (wrapping regexps). The warning will show up until there's an option to disable it in jshint.
You can run the test suite with
grunt test or
grunt testv for more verbose output.
Each new feature ough to have full test coverage. We usually start by writing a fixture which is a pair of two file: the one to process (the fixture) and it's expected output.
Fixture are html or md files in
spec/fixtures. Any partials and templates required by this fixture should be stored in
spec/templates, respectively. The expected output of a fixture should be put in
Once we run tests and the fixture is failing, we can implement any necessary feature by starting with writing specs (unit tests) in the
spec directory, (like
spec/my_new_feature_spec.js) and then implementing it in
lib directory (
Once all the unit tests pass, we can integrate new code back to the task with making the fixture test pass in mind :) .
If you take a look at any file in
lib/ you can notice that there's no dependencies between modules. All dependencies are injected in the task file
tasks/stencil.js. That's the place where the integration happens.