Useful links: Docsy releases & tags. Jump to the latest release.
For a list of issues targeted for the next release, see the 23Q2 milestone.
0.8.0 - next major release (unpublished yet)
New:
Breaking changes:
Other changes:
Followup changes to Bootstrap (BS) 5.2 upgrade (#470):
td-blog-posts-list__item
andtd-blog-posts-list__body
replace the.media
and.media-body
classes, dropped by BS 5 #1560.- Docsy test for Bootstrap version has been made more robust, and can be disabled. For details, see #1579.
New:
- Click to copy button for Chroma-highlighted code blocks: If you already implemented this functionality on your website, you can disable it. For details see Chroma highlighting docs.
Breaking changes:
- Hugo release 0.110.0 or later is required.
- Upgraded Bootstrap (#470) to v5.2. For a list of Bootstrap's breaking changes, see the Bootstrap migration page. Docsy-specific changes:
- Shortcodes:
- Now using Hugo's native support for processing HTML & markdown, not file extension testing. (#906)
- Dropped support for pre-Hugo-0.54.x behavior of
{{% %}}
. (#939) blocks/section
: default and accepted values of thetype
argument have changed! For details see blocks/section (#1472).- Card shortcodes (#1376)]:
- Renamed CSS class
td-card-deck
totd-card-group
. card
,card-code
: markup of inner content (HTML/markdown) now depends on the syntax of the calling shortcode, not on extension of page file any more #906.card-code
is deprecated; usecard
with named parametercode=true
instead.
- Renamed CSS class
- Detection of draw.io diagrams is now disabled by default #1185
Other changes:
$list-inline-padding
is increased in support of footer icons (#1523). If this global adjustment is a problem for your project, let us know and we can contextualize the adjustment to the footer.- Non-breaking changes that result from the Bootstrap v5 upgrade:
- Draw.io diagram edit button: replaced custom colors by BS's outline primary.
For the full list of the changes found in this release, see the release notes.
With this release we declare a feature freeze while we migrate to the newest Bootstrap version. See the announcement for more information.
New:
-
Simplified use of mermaid diagrams: when using a
mermaid
code block on your page, mermaid is now automatically enabled (needs hugo version >= 0.93.0). For existing sites build with hugo 0.93.0+, parametermermaid.enable
can be removed from site config. -
Add render hook for chem code blocks: add auto-activation of
math
andchem
blocks via KateX and mhchem. Support for formula rendering activation on individual pages only. Hugo version >= 0.93.0 required.
For the full list of the changes found in this release, see the release notes. BREAKING CHANGES are documented below.
After you update your project's Docsy:
- Update your project setup (see 0.4.0) if you haven't already.
- Run
npm install
.
New:
- Projects can now install and use Docsy as an NPM package.
Breaking changes:
- Tabbed panes, text display. By default, the content of a tab inside a
tabbed pane is shown as code. As of version 0.4 of the shortcode, you can add
the parameter
code=false
to yourtabpane
ortab
shortcode in order to render tab content(s) as text (markdown or html). As of version 0.5 the name of this parameter was changed, we now usetext=true
in order to mark content as text. - Display logo by default. Most projects show their logo in the navbar. In support of this majority, Docsy now displays a logo by default. For details on how to hide the logo (or your brand name), see Styling your project logo and name.
- Upgraded Bootstrap to v4.6.2 from v4.6.1, resulting in some style changes
(such as an adjustment in the size of
small
). For details, see v4.6.2 release notes. - Upgraded FontAwesome to v6 from v5. While many icons were renamed, the v5 names still work. For details about icon renames and more, see What's changed.
- Search-box: the HTML structure and class names have changed, due to the Font Awesome upgrade, for both online and offline search. This may affect your project if you have overridden search styling or scripts.
Other changes:
- By default, Docsy now uses the gtag.js analytics library for all site tags. For details, see Adding Analytics > Setup.
Unpublished.
For a full list of the changes to this release, see the release notes. Potential BREAKING CHANGES are documented below.
After you update your project's Docsy, run npm install
.
If your project uses Docsy as follows:
- Hugo Module, then this change doesn't impact you.
- For other Docsy setups, this is a BREAKING CHANGE -- read on.
Docsy now fetches Bootstrap and FontAwesome as NPM packages rather than git submodules. This has an impact on your project-build setup. To migrate your site, follow these steps (execute commands from your project's root directory):
- Delete obsolete Docsy Git submodules:
These commands remove the submodules from Git's tracking, from the
git rm themes/docsy/assets/vendor/Font-Awesome git rm themes/docsy/assets/vendor/bootstrap
.gitmodules
file, and deletes the submodule files underthemes/docsy/assets/vendor
. - Get Docsy dependencies:
(cd themes/docsy && npm install)
- Update your build scripts to fetch Docsy dependencies automatically. For
example, if your site build uses NPM scripts, consider getting Docsy
dependencies via a prepare script as follows:
{ "name": "my-website", "scripts": { "prepare": "cd themes/docsy && npm install", "...": "..." }, "...": "..." }
- (Optional) Build script cleanup. If your project uses Docsy as a git
submodule, Docsy updates no longer require the
--recursive
flag when runninggit submodule update
. Consider dropping the flag if you have no other recursive git submodules.
Proceed as usual to build or serve your site.
For a full list of the changes to this release, see the release notes.
Breaking changes:
- Upgrade to Algolia DocSearch v3. If your site uses the deprecated DocSearch v2, you must update your DocSearch code.
- (Edit) PR #1009 inadvertently changed the base Bootstrap styles for
cards, as well as the Docsy
highlight
style. For details, see issue #1154. Release 0.5.0 includes a fix.
New:
-
Add official Docsy support for Hugo modules. Many thanks to the dedicated and patient efforts of @deining, who researched, experimented, and implemented this feature. Thanks to @deining and @LisaFC for the doc updates.
For details, see Migrate to Hugo Modules.
Details:
- For a full list of the changes to this release, see the release notes
0.X.Y - next planned release (unpublished yet)
For a full list of the changes to this release, see the release notes.
Breaking changes:
- ...