Pedro Palau

This one is very important, because in today's frontend world everything is needed to be customizable.

Create multiple test cases to check the code works correctly.

Add some new demos of `how-to` and check is something is missing in the documentation.

Check if this library works properly in the server and if not, implement it.

Separate CSS styles from the source code

1

This library is using an imported `CSS` file in the main `JS` file. The idea is to separate the `CSS` file from the `JS` so that anyone can import it...

Make the integration with Travis to publish this library in `npm` after any update, and also, update the demo using `gh-pages`.

Possibility to use imports processed by other plugins like `postcss-scss`

5

In the following line the `@import` directive is always treated as a file with the `.css` extension, but the plugins support now the `".css", ".scss", ".sass"` extensions. https://github.com/mhanberg/jekyll-postcss/blob/acc941e01ab182552fc91ddce93560245f502b04/lib/jekyll/converters/postcss.rb#L56 Should we...