npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

grunt-multi-lang-site-generator

v0.6.0

Published

Runs templates and i18n at grunt's compile time.

Downloads

34

Readme

NPM Build Status

grunt-multi-lang-site-generator

Creates multiple language versions of a site based on vocab JSON files and templates. Example:

grunt.initConfig({
  multi_lang_site_generator: {
    default: {
      options: {
        vocabs:           ['english', 'mundo'],
        vocab_directory:  'vocabs'
      },
      files: {
        'index.html': ['templates/index.html.tmpl']
      }
    }
  }
});

Will take vocab objects and templates:

templates/index.html.tmpl
vocabs/english.json
vocabs/mundo.json

And create the following output:

english/index.html
mundo/index.html

The vocab objects are JSON, each property corresponds to a variable in the template file...

{
foo: "bar"
}
<p><%= foo %></p>

It uses lodash's template engine.

Getting Started

This plugin requires Grunt ~0.4.1

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-multi-lang-site-generator --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-multi-lang-site-generator');

The "multi-lang-site-generator" task

Run this task with the grunt less command.

Task targets, files and options may be specified according to the grunt Configuring tasks guide.

Options

vocab

Type: Array Default value: {}

Mandatory list of languages to use to make a translated site with. Each item in the array must correspond to a JSON file in the vocab directory. Each item label will be used to name the language site directory with.

Use the value ['*'] or '*' if you want to render all vocabs in your vocab directory.

vocab_directory

Type: String Default value: ''

Mandatory path relative from your grunt file where your vocab JSON files reside.

output_directory

Type: String Default value: ''

Optional directory to output the language sites to. By default an 'english' translated site will be created next to your grunt file. If you wanted it to be created in a 'site' directory, set output_directory to 'site'.

data

Type: JSON Default value: {}

Optional additional data to pass into the template. This is useful for data values you want to pass into the templates that are common for each site, e.g. domain values for assets.

template_directory

Type: String Default value: ''

Optional path relative from your grunt file where your templates reside. This is useful if you are creating multiple files and do not want to repeat the template directory path many times.

Special variables

When the templates run, there are additional template variables available that are not defined by the vocab or options.data object. This are:

<%= vocab_dir %> - name of directory template is being rendered into, e.g. 'english'.

Sub templates

You can reference other templates with your templates, for example the template main.tmpl:

hello <%= include('other_template.tmpl') %>

Will include all the content from the template other_template.tmpl. Sub templates have all the same functionality as normal templates, so you can reference the vocabs and add JavaScript into it.

Passing values between templates

Each template is scoped locally, so you cannot reference a JS variable set in a template from an included template. E.g.

// MAIN.TMPL
<% var title = "Index page"; %>
<% include("header.tmpl") %>
<h1><%= title %></h1> // outputs "Index page"


// HEADER.TMPL
<html>
<head>
<title><%= title %></title> // Throws an error
</head>
<body>

To pass variables set in your template to included templates, use the optional 2nd parameter in the include call, e.g.

// MAIN.TMPL
<% var title = "Index page"; %>
<% include("header.tmpl", {
  title: title
}) %>
<h1><%= title %></h1> // outputs "Index page"


// HEADER.TMPL
<html>
<head>
<title><%= title %></title> // outputs "Index page"
</head>
<body>

User defined functions and passed in data

Any data passed in from the vocab files or the optional data parameter are available as local variables within the templates and sub templates.

Unfortunately they are not available within the closure of functions that are defined within your templates. For example, if you ran this grunt config setup and template:

grunt.initConfig({
  multi_lang_site_generator: {
    default: {
      options: {
        vocabs:           ['english', 'mundo'],
        vocab_directory:  'test/fixtures/vocabs',
        output_directory: 'test/output/extra_data/',
        data: {
          "foo": "bar"
        },
        templatetoken: {
          evaluate:      /\{\{(.+?)\}\}/g,
          interpolate:   /\{\{=(.+?)\}\}/g,
          escape:        /\{\{-(.+?)\}\}/g
        }
      },
      files: {
        'index.html': 'templates/index.html.tmpl'
      }
    }
  }
});

// index.html.tmpl
console.log(foo); // outputs "bar";
function subFunc() {
  console.log(foo); // returns undefined
}
subFunc();

The var foo passed in from the data option would be recognised in the scope of the module (i.e. file (files are modules in node.js)) but would not be recognised in the scope of the user defined function subFunc.

Thankfully lo-dash.js has an object called obj which is referenceable anywhere in the template. So changing the example to this makes the var foo referenceable in the user defined function:

// index.html.tmpl
console.log(foo); // outputs "bar";
function subFunc() {
  console.log(obj.foo); // returns "bar"
}
subFunc();

BB Code

You can use Bulletin Board (BB) inside of vocabs, the BB code will be replaced with HTML markup when generating. Currently supported BB code's are strong, paragraphs and URL's.

The generator will firstly process the BB code into markup. The processed vocabs are then passed to lodash's template method to generate the final markup files. Therefore you can only use BB code inside vocab files and not the template files.

Paragraph tags

{P}This is a paragraph.{/P}

Will generate

<p>This is a paragraph.</p>

Bold tags

This sentence contains {B}important information{/B} 

Will generate

This sentence contains <strong>important information</strong> 

URL tags

A URL tag must contain a URL parameter and must surround the content that will become a link.

Check out this {URL=http://example.com}example{/URL}

Will generate

Check out this <a href="http://example.com">example</a> 

Changing default template tokens.

There may be occasions when you are using the generator and you need to output client side templates to be rendered. If these client side templates use the same token i.e <% %> then the genrator will of course attempt to render these!

One option is to change token on your client side templating solution, but this may not always be possible as there maybe a dependency outside your scope.

templatetoken exposes lodash's option to change template tokens.

For example, to perform Mustache.js style templating:

templatetoken: {
    evaluate:      /\{\{(.+?)\}\}/g,
    interpolate:   /\{\{=(.+?)\}\}/g,
    escape:        /\{\{-(.+?)\}\}/g
  }

Thanks

This project was originally forked from Erik Loubal's grunt-template-runner. This didn't quite do what I wanted it to do, but was an excellent starting point. This project would have taken MUCH longer without grunt-template-runner, thank you Erik.