All Versions
52
Latest Version
Avg Release Cycle
35 days
Latest Release
44 days ago

Changelog History
Page 4

  • v0.15.0.beta1

    May 29, 2020
  • v0.14.1 Changes

    May 23, 2020
    • ๐Ÿ“ฆ Patch to fix PluginManager yarn add bug when there is no dependencies key in package.json
  • v0.14.0 Changes

    May 17, 2020

    ๐Ÿš€ Release Notes

    โšก๏ธ You can update your Gemfile to remove the line pointing to the Liquid fork under jaredcwhite, it's no longer necessary.

    โšก๏ธ There's also an update to start.js you can copy from the repository here.

    ๐Ÿš€ More general information available in a blog post here.

    ๐Ÿ”„ Changes

    • ๐Ÿšš Use liquid-render-tag backport gem and remove references to temporary GitHub fork of Liquid #52 (jaredcwhite)
    • โ™ป๏ธ Refactor Bridgetown::Site into multiple Concerns #51 (jaredcwhite)
    • ๐Ÿ›  Fix for start.js to eliminate junk terminal characters (jaredcwhite)
    • ๐Ÿ†• New Unified Plugins API with Builders, Source Manifests, and Autoreload #41 (jaredcwhite)
    • โž• Add a Posts page to the new site template #39 (andrewmcodes)
    • โž• Add titleize Liquid filter and improve slugify filter description #38 (jaredcwhite)
    • โž• Add Bundler cache to the build GH action to improve test speed #40 (andrewmcodes)
    • โฌ†๏ธ Bump minimum Node requirement to 10.13 (jaredcwhite)
  • v0.13.0 Changes

    May 05, 2020
    • ๐Ÿ”ง 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 Changes

    May 01, 2020
    • โšก๏ธ Update the minimum Ruby version requirement to 2.5
  • v0.12.0 Changes

    April 27, 2020

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

  • v0.11.2 Changes

    April 24, 2020

    ๐Ÿ›  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
  • v0.11.1 Changes

    April 24, 2020
    • โž• 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
  • v0.11.0 Changes

    April 21, 2020

    ๐Ÿš€ 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: defaulttitle: Posts in category :prototype-termprototype: 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 Changes

    April 19, 2020

    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" =\> "[email protected]#{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