Rake tasks behind Wax 🐝
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


wax_tasks 🐝

Gem Version License PRs Welcome docs

Build Status Maintainability Test Coverage

wax_tasks is gem-packaged set of Rake tasks for creating minimal exhibition sites with Jekyll, IIIF, and ElasticLunr.js.

It can be used to generate collection markdown pages from a data file (wax:pagemaster), generate a client-side search index (wax:lunr), generate IIIF-compliant derivatives (both Image + Presentation API) from local image files (wax:iiif), and more.

Looking for a Jekyll theme that works with wax_tasks? Check out minicomp/wax.

NOTE >> wax_tasks is being developed rapidly. it will be relatively
        volatile leading up to the beta release (v0.5.0).

Getting Started


You'll need Ruby >= 2.3 with bundler installed. Check your versions with:

$ ruby -v
  ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-darwin15]

$ bundler -v
  Bundler version 1.16.1

To use the IIIF task, you will also need to have ImageMagick installed and functional. You can check to see if you have ImageMagick by running:

$ convert -version
  Version: ImageMagick 6.9.9-20 Q16 x86_64 2017-10-15 http://www.imagemagick.org
  Copyright: Š 1999-2017 ImageMagick Studio LLC
  License: http://www.imagemagick.org/script/license.php
  Features: Cipher DPC Modules
  Delegates (built-in): bzlib freetype jng jpeg ltdl lzma png tiff xml zlib

Next, you'll need a Jekyll site. You can clone the minicomp/wax demo site or start a site from scratch with:

$ gem install jekyll
$ jekyll new wax && cd wax


Add wax_tasks to your Jekyll site's Gemfile:

gem 'wax_tasks'

... and install with bundler:

$ bundle install

Create a Rakefile with the following:

spec = Gem::Specification.find_by_name 'wax_tasks'
Dir.glob("#{spec.gem_dir}/lib/tasks/*.rake").each { |r| load r }


After following the installation instructions above, you will have access to the Rake tasks in your shell by running $ bundle exec rake wax:taskname in the root directory of your Jekyll site.

Sample site _config.yml file:

# basic settings
title: Wax.
description: a jekyll theme for minimal exhibitions
url: ''
baseurl: '/wax'

# build settings
permalink: pretty # optional, creates `/page/` link instead of `page.html` link
collections_dir: '' # optional, allows you to tidy up and keep collections
                       # (see below) inside a directory (as of jekyll 3.7)

# wax collection settings
  objects: # << the collection name, which will be the directory pagemaster makes
    source: objects.csv # ^^ it will also be used in creating permalinks for the pages
    layout: iiif-image-page
    output: true # this must be true for your .md pages to be built to html!
      content: false # whether or not to index the markdown page content (below the YAML)
      fields: # the metadata fields to index
        - title
        - artist
        - location
        - _date
        - object_type
        - current_location
        label: title
        location: current_location
        # in this example, `label` will be the metadata field in the IIIF manifest,
        # and it will be populated by the `title` column from objects.csv;
        # likewise, `location` will pull from the `current_location` field.

The above example includes a single collection objects that comprises:

  1. a CSV source file (objects.csv), and
  2. a directory of images files.

wax_tasks will expect to find the source file in the _data directory, i.e., at _data/objects.csv. It will also expect to find the source images in a directory named after the collection within _data/iiif, i.e., _data/iiif/objects/*.jpg. Some tasks will require you to invoke the collection by name, e.g., $ bundle exec rake wax:pagemaster objects and $ bundle exec rake wax:iiif objects.

For more information on configuring Jekyll collections for wax_tasks, check out the minicomp/wax wiki and https://jekyllrb.com/docs/collections/.

Running the tasks


Takes a CSV, JSON, or YAML file of collection metadata and generates a markdown page for each record to a directory using a specified layout. Read More.

$ bundle exec rake wax:pagemaster collection-name


Generates a client-side JSON search index of your site for use with ElasticLunr.js. Read More.

$ bundle exec rake wax:lunr

NOTE >> wax_lunr will also generate a default lunr UI to use if you run:
        $ bundle exec rake wax:lunr UI=true


Takes a local directory of images and generates tiles and data that work with a IIIF compliant image viewer like OpenSeaDragon, Mirador, or Leaflet IIIF. Read More.

$ bundle exec rake wax:iiif collection-name


Runs htmlproofer on your compiled site to look for broken links, HTML errors, and accessibility concerns. Runs Rspec tests if a .rspec file is present. Read More.

$ bundle exec rake wax:test


Fork/clone the repository. After making code changes, run the tests ($ bundle exec rubocop and $ bundle exec rspec) before submitting a pull request. You can enable verbose tests with $ DEBUG=true bundle exec rspec.

Note: The cannonical repository is minicomp/wax_tasks. Please submit all issues and pull requests to the minicomp/wax_tasks repo.

NOTE >> The cannonical repository is minicomp/wax_tasks.
        Please submit all issues and pull requests to the cannonical repo.

minicomp/wax_tasks ~>


The gem is available as open source under the terms of the MIT License.