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

butter-assemble

v1.3.9

Published

The assembly engine behind Butter

Downloads

19

Readme

Butter Assemble

The assembly engine behind Butter. Not associated with Assemble. Inspired by Fabricator Assemble.

Turn this:

---
title: Document Name
name: World
---

<h1>{{home.greeting}}, {{name}}!</h1>

{{> button}}

Into this:

<!doctype html>
<html lang="en">
<head>
    <title>Document Name</title>
</head>
<body>

    <h1>Hello, World!</h1>

    <a href="#" class="button">Click me!</a>

</body>
</html>

Usage

The task returns a promise, so it can be used in an async task runner, like Gulp:

var assemble = require('butter-assemble');
var gulp = require('gulp');

gulp.task('assemble', function () {
	return assemble(options);
});

The task accepts options, but assumes this directory structure:

└── src
	├── data
	│   └── *.{json,yml}
	├── docs
	│   └── *.md
	├── materials
	│   └── components
	│       └── *.html
	└── views
	    ├── *.html
	    └── layouts
	        └── default.html

Options

Default options:

{
	layout: 'default',
	layouts: 'src/views/layouts/*',
	layoutIncludes: 'src/views/layouts/includes/*',
	views: ['src/views/**/*', '!src/views/+(layouts)/**'],
	materials: 'src/materials/**/*',
	data: 'src/data/**/*.{json,yml}',
	docs: 'src/docs/**/*.md',
	keys: {
		materials: 'materials',
		views: 'views',
		docs: 'docs'
	}
	helpers: {},
	logErrors: false,
	onError: function(error) {},
	dest: 'dist'
}

options.layout

Type: String Default: default

Name of the default layout template.

options.layouts

Type: String or Array Default: src/views/layouts/*

Files to use as layout templates.

options.layoutIncludes

Type: String or Array Default: src/views/layouts/includes/*

Files to use as layout includes.

options.views

Type: String or Array Default: ['src/views/**/*', '!src/views/+(layouts)/**']

Pages to pass through the assembler to be templated. Butter pages are stored at the root level views and user-defined views can be stored in subdirectories.

options.materials

Type: String or Array Default: src/materials/**/*

Files to use a partials/helpers. These are the materials that make up your toolkit. by default, Butter comes with "components" and "structures", but you can define your own taxonomy.

options.data

Type: String or Array Default: src/data/**/*.{json,yml}

JSON or YAML files to use as data for views.

options.docs

Type: String or Array Default: src/docs/**/*.md

Markdown files containing toolkit-wide documentation

options.keys

Type: Objects Default: materials/views/docs

Object keywords for accessing "materials", "views", and "docs" in a view templating context. Butter uses some specific terms like "materials" to describe what are really "partials" in Handelbars. This option give you the flexibility to define your own terms for materials, views, and docs.

For example:

assemble({
	keys: {
		materials: 'patterns'
	}
});
<!-- formerly `{{#each materials}}` -->
{{#each patterns}}

	<h1>{{name}}</h1>

	{{#each items}}
		<h2>{{name}}</h2>
	{{/each}}

{{/each}}

Note: this will also change the built-in {{material <foo>}} helper to use the singular form of whatever is defined for the materials key. e.g. materialKey: 'patterns' -> {{pattern <foo>}}. If you set a new key for materials, you will also need to update the f-item-content.html include to use the new helper name.

options.helpers

Type: Object Default: {}

User-defined helpers. E.g.:

helpers: {
	markdown: require('helper-markdown'),
	foo: function () {
		return 'bar';
	}
}

options.logErrors

Type: Boolean Default: false

Whether or not to log errors to console. If set to false, the app will exit on error.

options.onError

Type: Function Default: null

Error handler function. Receives an error object param.

options.dest

Type: String Default: dist

Destination of compiled views (where files are saved to)

Usage

Definitions

  • Layouts: wrapper templates
  • Views: individual pages
  • Materials: partial views; registered as "partials" and "helpers" in Handlebars
  • Data: Data piped in as template context
  • Docs: Markdown files containing documentation.

Layouts

Layouts are wrappers for pages. You can define as many layouts as you want by creating .html files in your layouts folder.

Example layout:

<!doctype html>
<html lang="en">
<head>
    <title>{{title}}</title>
</head>
<body>

    {% body %}

</body>
</html>

Page content is inserted in the {% body %} placeholder.

Context can be passed from a page to the layout via front matter.

The layout a page uses is also defined in front matter:

---
layout: custom-layout
title: My Custom Layout
---

This would use custom-layout.html.

When no layout property is defined, the page uses the default layout.

Views

Views are unique pages templated using Handlebars. These are both Butter pages and user-created pages (i.e. example templates)

View example:

---
title: Document Name
name: World
---

<h1>{{home.greeting}}, {{name}}!</h1>

{{> button}}

This outputs a page that uses the default layout (since no layout was defined).

The front matter block at the top provides context to both the layout and the page itself.

Context is also piped in from data files (see below). In this example, {{home.greeting}} refers to the greeting property in home.json.

Butter pages are typically stored at the root level of the views directory and user-created views (e.g. "templates", "pages", "interfaces") should be stored in subdirectories.

Materials

Materials are partial templates; think of them as the materials used to build pages.

They are accessed as a "partial" using the > syntax in Handlebars:

{{> material-name}}

Any file in the glob defined in options.materials is turned into a partial/helper and can be accessed as such. For example, assume the components contains materials:

└── components
    ├── button.html
    └── form-toggle.html

The content within these files can be accessed as such:

{{> button}}
{{> form-toggle}}

Ordering

You can manually order materials by prefixing the file name with numbers:

01-foo.html
01.01-bar.html
02-qux.html

This defines the order in which materials will appear in the side menu or other places the materials.items context is used.

Note: The number prefixes are ignored when registering partials, so you'll still be able to access them using the material name per usual. e.g.:

{{> foo}}
{{> bar}}
{{> qux}}

The numbers are also ignored in the .name property. The materials above would list as:

Foo
Bar
Qux

Data

Data is defined as JSON or YAML.

The data folder can contain several .json or .yml files:

└── data
    ├── home.json
    └── contact.yml

home.json:

{
  "greeting": "Hello"
}

The data within each file can be accessed using dot notation:

{{home.greeting}}
{{contact.propName}}

Docs

Docs are just a generic way to capture toolkit documenation that's not specific to a material. This could be something like JavaScript architecture, accessibility guidelines, etc.

Docs are written in markdown and are stored in src/docs by default.

Hooks

Hooks allow you to intercept certain points during assembly.

beforeLayout

Allows for user injection before the layouts are parsed.

| Arguments | Description| |:----------|:-----------| |config Object | Reference to the config object. | |params Object || | - files Array | Array of file references read from options.layouts | | - layouts Object | Reference to the assembly.layouts object. |

Usage
// assembler
gulp.task('assembler', (done) => {
  assembler({
    logErrors: config.dev,
    dest: config.dest,
    hooks: {
		beforeLayout: function (options, config) {
			console.log('BEFORE LAYOUT HOOK');
			return params.files;
		}
	}
  });
  done();
});

layout

Allows user injection after the layout content is read.

| Arguments | Description| |:----------|------------| |config Object | The configuration object. | |params Object || | - content String | The content read from the file | | - files Array | Array of file references read from options.layouts. | | - id String | The id of the file | | - layouts Object | Reference to the assembly.layouts object. |

Usage
// assembler
gulp.task('assembler', (done) => {
  assembler({
    logErrors: config.dev,
    dest: config.dest,
    hooks: {
		layout: function (options, config) {
			console.log('LAYOUT HOOK:', params.id);
			return params.content;
		}
	}
  });
  done();
});

beforeLayoutIncludes

Allows user injection before the layout includes are parsed.

| Arguments | Description | |:----------|:------------| |config Object | The configuration object. | |params Object || | - files Array | Array of file references read from options.layoutIncludes. |

Usage
// assembler
gulp.task('assembler', (done) => {
  assembler({
    logErrors: config.dev,
    dest: config.dest,
    hooks: {
		beforeLayoutIncludes: function (config, params) {
			console.log('BEFORE LAYOUT INCLUDES HOOK');
			return params.files;
		}
	}
  });
  done();
});

layoutIncludes

Allows user injection after the include content is read.

| Arguments | Description | |:----------|:------------| |config Object | The configuration object. | |params Object || | - content String | The content read from the file | | - files Array | Array of file references read from options.layoutIncludes. |

Usage
// assembler
gulp.task('assembler', (done) => {
  assembler({
    logErrors: config.dev,
    dest: config.dest,
    hooks: {
		layoutIncludes: function (config, params) {
			console.log('LAYOUT INCLUDES HOOK:', params.id);
			return params.content;
		}
	}
  });
  done();
});

beforeData

Allows for user injection before the data is parsed.

| Arguments | Description | |:----------|:------------| |config Object | The configuration object. | |params Object || | - data Object | Reference to the assembly.data object. | | - files Array | Array of file references read from options.data. |

Usage
// assembler
gulp.task('assembler', (done) => {
  assembler({
    logErrors: config.dev,
    dest: config.dest,
    hooks: {
		beforeData: function (config, params) {
			console.log('BEFORE DATA HOOK');
			params.data['myCustomData'] = {
			    "something": "This is injected berore any data files are read"
			};
			return params.files;
		}
	}
  });
  done();
});

data

Allows user injection after the data is read.

| Arguments | Description | |:----------|:------------| |config Object | The configuration object. | |params Object || | - content Object | The content read from the file converted into an object. | | - data Object | Reference to the assembly.data object. | | - files Array | Array of file references read from options.data. | | - id String | The id of the file |

Usage
// assembler
gulp.task('assembler', (done) => {
  assembler({
    logErrors: config.dev,
    dest: config.dest,
    hooks: {
		data: function (config, params) {
			console.log('DATA HOOK:', params.id);
			params.content['myProperty'] = "Custom property added to this file";
			return params.content;
		}
	}
  });
  done();
});

beforeMaterials

Allows for user injection before the materials are parsed.

| Arguments | Description | |:----------|:------------| |config Object | The configuration object. | |params Object || | - files Array | Array of file references read from options.materials. | | - materials Object | Reference to the assembly.materials object. |

Usage
// assembler
gulp.task('assembler', (done) => {
  assembler({
    logErrors: config.dev,
    dest: config.dest,
    hooks: {
		beforeMaterials: function (config, params) {
			console.log('BEFORE MATERIALS HOOK');
			return params.files;
		}
	}
  });
  done();
});

materials

Allows user injection after the content is read.

| Arguments | Description | |:----------|:------------| |config Object | The configuration object. | |params Object || | - content Object | The content read from the file converted into an object. | | - files Array | Array of file references read from options.materials. | | - materialData Object | Reference to the material-name-spaced local data in template context. | | - materials Object | Reference to the assembly.materialData object. |

Usage
// assembler
gulp.task('assembler', (done) => {
  assembler({
    logErrors: config.dev,
    dest: config.dest,
    hooks: {
		materials: function (config, params) {
			console.log('MATERIALS HOOK:', params.id);
			return params.content;
		}
	}
  });
  done();
});

beforeViews

Allows for user injection before the views are parsed.

| Arguments | Description | |:----------|:------------| |config Object | The configuration object. | |params Object || | - files Array | Array of file references read from options.views. | | - views Object | Reference to the assembly.views object. |

Usage
// assembler
gulp.task('assembler', (done) => {
  assembler({
    logErrors: config.dev,
    dest: config.dest,
    hooks: {
		beforeViews: function (config, params) {
			console.log('BEFORE VIEWS HOOK');
			return params.files;
		}
	}
  });
  done();
});

views

Allows user injection after the view is read.

| Arguments | Description | |:----------|:------------| |config Object | The configuration object. | |params Object || | - fileData Object | Front-matter of the view file. | | - files Array | Array of file references read fromoptions.views. | | - views Object | Reference to theassembly.views` object. |

Usage
// assembler
gulp.task('assembler', (done) => {
  assembler({
    logErrors: config.dev,
    dest: config.dest,
    hooks: {
		views: function (config, params) {
			console.log('VIEWS HOOK:', params.id);
			return params.fileData;
		}
	}
  });
  done();
});

beforeDocs

Allows for user injection before the docs are parsed.

| Arguments | Description | |:----------|:------------| |config Object | The configuration object. | |params Object || | - docs Object | Reference to the assembly.docs object. | | - files Array | Array of file references read from options.docs. |

Usage
// assembler
gulp.task('assembler', (done) => {
  assembler({
    logErrors: config.dev,
    dest: config.dest,
    hooks: {
		beforeDocs: function (config, params) {
			console.log('BEFORE DOCS HOOK');
			return params.files;
		}
	}
  });
  done();
});

docs

Allows for user injection before the docs are parsed.

| Arguments | Description | |:----------|:------------| |config Object | The configuration object. | |params Object || | - content String | The content read from the file. | | - docs Object | Reference to the assembly.docs object. | | - files Array | Array of file references read from options.docs. |

Usage
// assembler
gulp.task('assembler', (done) => {
  assembler({
    logErrors: config.dev,
    dest: config.dest,
    hooks: {
		docs: function (config, params) {
			console.log('DOCS HOOK:', params.id);
			return params.content;
		}
	}
  });
  done();
});

assembly

Allows for user injection after the assembly process is complete.

| Arguments | Description | |:----------|:------------| |config Object | The configuration object. | |assembly Object | Reference to the assembly object. |

Usage
// assembler
gulp.task('assembler', (done) => {
  assembler({
    logErrors: config.dev,
    dest: config.dest,
    hooks: {
		assembly: function (config, params) {
			console.log('ASSEMBLY HOOK');
		}
	}
  });
  done();
});