Trio Icon
Trio v5.0.0

The Trio Blog

  1. Latest
  2. Releases
  3. Tutorials

Trio v5.0.0: Dart SASS

Trio v5.0.0

It is with great pleasure that I announce the release of Trio v5.0.0.

Trio is now using Dart Sass as its Sass Compiler

Trio is no longer using Node Sass as it and Lib Sass have been deprecated. Please note that this is a breaking change that could impact your stylesheets (Please see https://sass-lang.com/blog/libsass-is-deprecated#how-do-i-migrate for more information).

Trio v4.2.0: Improved Developer Experience

Trio v4.2.0

It is with great pleasure that I announce the release of Trio v4.2.0.

Trio now ignores and reports fragments that do not have front matter defined.

Prior to v4.2.0, fragment files that did not have front matter generated errors that were confusing and unnecessary (as far as the user is concerned). These fragments are now reported to the console but otherwise ignored during the build process.

Trio v4.1.0: Tag-Based Callbacks

Trio v4.1.0

It is with great pleasure that I announce the release of Trio v4.1.0.

Trio now supports callbacks declared on tags that are replaced by include and fragment content.

Prior to v4.1.0, tag-based callbacks declared on tags that are replaced by an include's or a fragment's content are never registered and therefore never called. Trio V4.1.0 corrects this omission and now supports tag-based callbacks on these tags.

Support for these callbacks will allows you to directly target these tags in your tag-based callbacks using the callback's $tag parameter.

Please note that this new behavior doesn't impact how Trio outputs these tags for development and release builds. As always, when building for development, Trio will still comment out these tags in the generated HTML document, and when building for release, Trio will not output these tags in the generated HTML document.

What's Coming In Trio v4.1.0

While you are enjoying the recently released Trio v4.0.0 we want you to know that Trio v4.1.0 is already in the testing phase and will be released shortly.

Although it wasn't explicitly stated in the documentation, tag-based callbacks that are declared on tags that are replaced by an include's or a fragment's content are never registered and therefore never called. Trio V4.1.0 corrects this omission and now supports tag-based callbacks on these tags.

Support for these callbacks will allows you to directly target these tags in your tag-based callbacks using the callback's $tag parameter.

Please note that this new behavior doesn't impact how Trio outputs these tags for development and release builds. As always, when building for development, Trio will still comment out these tags in the generated HTML document, and when building for release, Trio will not output these tags in the generated HTML document.

If you would like to be notified when Trio v4.1.0 drops then please consider following @gettriossg on Twitter.

Trio v4.0.0: The Commitment Remains The Developer Experience

Trio v4.0.0: Staying True To The Cause.

Back in January, when I released Trio v3.0.0, I made a personal commitment that for the foreseeable future my focus would remain improving the developer experience. Today I am releasing Trio v4.0.0 that continues to deliver on that commitment.

Trio v3.1.0: Improved Developer Experience

Two New Features To Improve The Developer Experience.

Preserved include and fragment target tags and auto detection of new version.

Trio v3.0.0: Permalinkns And Other Goodies

Lots of goodies for you in this release.

New features make this the most productive release of Trio yet, and major bug fixes make this the most stable release of Trio to date!

Trio v2.0.0: The One With Collections

Collections are a big deal!

Collections are groups of pages that are dynamically generated by Trio that you would otherwise have to manually create yourself.

Trio v1.1.1 (IKIGAI)

Broken Dependency Resolution For Tag-based Callbacks Resolved

This is a maintenance release only and includes 1 bug fix. Please see the changelog for details.

Trio v1.1.0 (IKIGAI)

Better Reporting For Unresolved Assets

This release addresses 1 enhancement and 1 bug fix. Please see the changelog for details.