Hugo `0.32` features **Page Bundles and Image Processing** by [@bep](https://github.com/bep), which is very cool and useful on so many levels. Read about it in more detail in the [Hugo documentation](https://gohugo.io/about/new-in-032/), but some of the highlights include:
Automatic bundling of a content page with its resources. Resources can be anything: Images, JSON files … and also other content pages.
A Resource will have its RelPermalink and Permalink relative to the “owning page”. This makes the complete article with both text and images portable (just send a ZIP file with a folder to your editor), and it can be previewed directly on GitHub.
Powerful and simple to use image processing with the new .Resize, .Fill, and .Fit methods on the new Image resource.
Full support for symbolic links inside /content, both for regular files and directories.
The built-in benchmarks in Hugo show that this is also the fastest and most memory effective Hugo version to date. But note that the build time total reported in the console is now adjusted to be the real total, including the copy of static files. So, if it reports more milliseconds, it is still most likely faster …
This release represents 30 contributions by 7 contributors to the main Hugo code base.
@bep leads the Hugo development with a significant amount of contributions, but also a big shoutout to @betaveros, @chaseadamsio, and @kropp. And as always big thanks to @digitalcraftsman for his relentless work on keeping the documentation and the themes site in pristine condition.
Many have also been busy writing and fixing the documentation in hugoDocs,
which has received 17 contributions by 7 contributors. A special thanks to @bep, @felicianotech, @maiki, and @carlchengli for their work on the documentation site.
Today is New Year’s Eve. It is the last day of 2017, a year that have seen a string of pearls of Hugo releases, making Hugo the top choice for website development:
0.32, December 2017: Page Bundles and Image Processing edition.
0.31, November 2017: The Language Multihost Edition! with one baseURL per language.
0.30, October 2017: The Race Car Edition with the Fast Render Mode.
0.29, September 2017: Added Template Metrics.
0.28, September 2017: Blistering fast and native syntax highlighting from Chroma.
0.27, September 2017: Fast and flexible Related Content.
0.26, August 2017: The Language Style Edition with AP Style or Chicago Style Title Case and « French Guillemets ».
0.25, July 2017: The Kinder Surprise edition added, among other cool things, hugo server --navigateToChanged which navigates to the content page you start editing.
0.24, June 2017: Was The Revival of the Archetypes! Now archetype files, i.e. the content file templates, can include template syntax with all of Hugo’s functions and variables.
0.23, June 2017: Hugo moved to it’s own GitHub organization, gohugoio.
0.22, June 2017: Added nested sections, a long sought after feature.
0.21, May 2017: Full support for shortcodes per output format (think AMP).
0.20, April 2017: Was all about Custom Output Formats.
0.19, February 2017: Native Emacs Org-mode content support and lots of internal upgrades.
The build total in the console is now the … total (i.e. it now includes both the copy of the static files and the Hugo build). So if your Hugo site seems to build slightly slower, it is in reality probably slightly faster than before this release.
Images and other static resources in folders with “_index.md” will have its RelPermalink relative to its page.
Images and other static resources in or below “index.md” folders will have its RelPermalink relative to its page (respecting permalink settings etc.)
Content pages in or below “index.md” will not get their own URL, but will be part of the .Resources collection of its page.
.Site.Files is deprecated.
Hugo no longer minfies CSS files inside /content. This was an undocumented “proof of concept feature”. We may revisit the “assets handling” in a future release.
Page.GetParamdoes not lowercase your result anymore. If you really want to lowercase your params, do it with .GetParam "myparam" | lower or similar.