> The Markdown spec says that `*`, `**` and `~~` output `<em>`, `<strong>` and `<del>` tags respectively, which I think is [semantically incorrect](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/b#usage_notes) in HTML.
>
> Sadly, both of Jekyll's Markdown parsers output those tags directly, with no way to change their behaviour.
>
> Therefore, I don't see any usefulness in using Jekyll with Bluelib, so continuing this project would be pointless.
Default is the simplest layout of the three, and creates the page root, containing only **the Bluelib rulesets** sourced from [UNPKG](https://unpkg.com/), and an **empty body**.
To set up your environment to develop this theme, run `bundle install`.
Your theme is setup just like a normal Jekyll site! To test your theme, run `bundle exec jekyll serve` and open your browser at `http://localhost:4000`. This starts a Jekyll server using your theme. Add pages, documents, data, etc. like normal to test your theme's contents. As you make modifications to your theme and to your content, your site will regenerate and you should see the changes in the browser after a refresh, just like normal.
When your theme is released, only the files in `_layouts`, `_includes`, `_sass` and `assets` tracked with Git will be bundled.
To add a custom directory to your theme-gem, please edit the regexp in `jekyll-theme-bluelib.gemspec` accordingly.