Add a readme to everyone of the plugins and cover

• Installation
• Usage

Add tests to cover all plugin functionality

Currently the way the plugin works is it reloads the file in node-vibrant this is because that is the only documented way to do it. However you can actual directly load a buffer into node-vibrant.

i..e

const palette = await colors.from(<BUFFER>).getPalette();

This would be an improvement as we would already have the file contents in a Buffer from Metalsmith. This would remove the need for disk IO completely when getting the colors (no double loading)

For this to work as intended the last argument (which is always the context for some reason) needs to be popped off. if that is not done the arguments that are specified by the user , instead of been undefined as expected will be the metalsmith context.

It can be fixed by adding a line like

const ctx = args.pop()

This has to happen before the line referenced in line 51 (As seen above)

There is a bug where when you change the image contents but not the name of that file image colors will not notice after the first run and the cache is built. This is because the cache currently uses a very simple way to workout if a file has changed. Basically it looks to see if there are more files than the last time , then it checks each filename to makes sure it is in the cache. So new files are scanned but not files that changes contents but not there name.

I don't think much can be done about the initial image color build as it just has to look at every image and determine the colors. However we could make it so that a user can pass it some GLOBS to scan rather than every image file.

The bigger improvement would be to redesign the cache routines so that when an image is added or changes only that image is rescanned. Currently it just ignores the cache and starts the rescan again rebuilding the cache.

Rename the project to Ghostline and also change the logo.