v0.13.0 "Klickitat"

• Configurable setting to allow executable Ruby code in Front Matter #9
• Honor the configured site encoding when loading Liquid components #33
• Allow configuration file as well as site metadata file to pull YAML options out of an environment specific block #34
• Add Faraday to the default set of gems that get installed with Bridgetown #30
• Add blank favicon.ico file to prevent error when generating a new site for the first time #32 (jaredmoody)

v0.12.1

• Update the minimum Ruby version requirement to 2.5

v0.12.0 "Lovejoy"

Happy Monday! Some much-needed improvements to the CLI experience of Bridgetown in this release. From the changelog:

• Add Concurrently and Browsersync for live reload, plus add new Yarn scripts #21. Take a look at the updated documentation [here](https://www.bridgetownrb.com/docs/#quick-instructions] and here.
• Add some color to terminal output
• Add code name for minor SemVer version updates

v0.11.2

A handy little collection of bug fixes and improvements.

• Add components source folder to sass-loader include paths
• Add a git init step to bridgetown new command #18
• Update sass-loader webpack config to support .sass #14 (jaredmoody)
• Add customizable permalinks to Prototype Pages (aka /path/to/:term/and/beyond). Use hooks and in-memory caching to speed up Pagination. Inspired by use cases like this… #12

v.0.11.0

The release that's getting promoted to a broader audience now!

From the changelog:

Prototype Pages

You can now create a page, say categories/category.html, and add a prototype config
to the Front Matter:

layout: default
title: Posts in category :prototype-term
prototype:
  term: category

And then all the site's different categories will have archives pages at this location
(e.g. categories/awesome-movies, categories/my-cool-vacation, etc.) It enables
pagination automatically, so you'd just use paginator.documents to loop through the
posts. See the docs here.

#11

v0.10.2

0.10.2 / 2020-04-19

Automatic Yarn Step for New Plugins

Now with Gem-based plugins for Bridgetown, all you need to do is add yarn-add
metadata matching the NPM package name and keep the version the same as the Gem
version. For example:

  spec.metadata = { "yarn-add" => "my-awesome-plugin@#{MyAwesomePlugin::VERSION}" }

With that bit of metadata, Bridgetown will know always to look for that package in
the users' package.json file when they load Bridgetown, and it will trigger a
yarn add command if the package and exact version number isn't present.

#8

0.10.1 / 2020-04-18

Add {% webpack_path [js|css] } tag which pulls in the Webpack manifest and finds
the hashed output bundles. Also works in concert with the Watcher so every time
Webpack rebuilds the bundles, Bridgetown regenerates the site.

#6

v0.10.0

Switch gears on experimental component functionality.

Going with a new rendercontent tag instead of component. It is based on
Shopify's new Render tag which recently got introduced to Liquid. Note that the
feature hasn't been officially released via the Liquid gem, so we need to use the
master branch that's been forked on GitHub with a higher version number).

#5

v0.9.0

This one is a doozy! Lots to look through:

• Update table styling in Documentation
• Now showing the plugins_dir in log output if it's present
• With the Posts Reader changes, now you can add a Front Matter Default of
  _posts/drafts having published: false, put a bunch of draft posts in
  _posts/drafts and you're done!
• New -U flag makes it easier to specify generating published: false docs.
• The Posts Reader has been reworked so that files with valid front matter can
  be read in even if there's no YYYY-MM-DD- at the beginning. In addition, static
  files are also supported, which means if you can create a folder (inlinefiles),
  drop a post in along with a bunch of images, and use ![alt](some-image.jpg)
  relative paths, it'll work! Big improvement to Markdown authoring. (You'll need
  to use a permalink in a specific manner though, e.g.
  permalink: /inlinefiles/:title:output_ext)
  If you need a static file not to get copied to the destination, just add an
  _ at the beginning and it'll get ignored.
• Collections no longer allow displaying a full server file path via Liquid.
• {{ page.collection }} now returns a CollectionDrop, not the label of
  the collection. Using the jsonify filter on a document however still returns
  just the label for the collection key.
• Add favicon to website
• Add mobile improvements to website
• Add back working feature tests for basic pagination
• Convert to Ruby 1.9+ symbol: value hash syntax
• Add Swup to website for some slick transitions
• Add "where_query" feature to Paginate. For example. specify where_query: [author, sandy] in the pagination YAML to filter by that front matter key.
• Update the Jamstack page in the docs.

Testing Release Feature

Getting started with GitHub's release feature. It'll be a little "Wild West" here for a bit, but as we get closer to an official stable 1.0, we'll be using releases in a more disciplined fashion.