Convenience utility for a quick templating workflow.
Last updated 5 years ago by joshuabc .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install markr 
SYNC missed versions from official npm registry.


markr recursively finds all the Jade templates in a directory and dumps them into a build folder.


I found myself using a similar pattern to compile templates on all my projects, and I wanted a quicker way to get up and running while getting as many boilerplate dependencies as possible out of the individual project's package.json. I like the idea of small, UNIX-like tools and am experimenting with how I might be able to create specific and simple utilities that can be easily combined together.


Step 0: Install

npm install -g markr

Step 1: Prepare Your Templates

markr expects to receive a directory with Jade templates inside.

Step 2: Convert to Markup!

From the command line, run markr [<source> <destination>], where <source> is the path to a directory containing Jade templates and <destination> is the path to the directory in which you'd like the HTML generated. Paths can be absolute or relative.

Example: markr ui/templates build/html

Optional: Converting Single Files

If you give markr a path to a file instead of a directory, it will just render that file into the given directory.

Current Tags

  • 0.0.4                                ...           latest (5 years ago)

4 Versions

  • 0.0.4                                ...           5 years ago
  • 0.0.3                                ...           6 years ago
  • 0.0.2                                ...           6 years ago
  • 0.0.1                                ...           6 years ago
Maintainers (1)
Today 1
This Week 2
This Month 2
Last Day 0
Last Week 0
Last Month 1
Dependencies (3)
Dev Dependencies (0)
Dependents (0)

Copyright 2014 - 2016 © |