Version 5.23
See the changelog of this version for a detailed list of changes.5.23.0 (2023-11-03)
Change
-
Change Wit' 0.120.0 th' author sett'ns move into th'
[params]
array 'n yerhugo.toml
. Because this collides wit' th' previous way, th' theme expected author informat'n, it now adheres t' Cap'n Hugo standards an' prints out a warning dur'n built if someth'n be wrong.Change yer previous sett'n from
hugo.[params] author = 'Hugo'
params: author: Cap'n Hugo
{ "params": { "author": "Hugo" } }
t'
hugo.[params] [params.author] name = 'Hugo'
params: author: name: Cap'n Hugo
{ "params": { "author": { "name": "Hugo" } } }
-
Change Taxonomy term planks now add th' breadcrumb fer each listed plank. If this gets too crowded fer ye, ye can turn th' breadcrumbs off 'n yer
hugo.toml
by add'ndisableTermBreadcrumbs=true
.
New
-
New Taxonomy an' term planks be now allowed t' contain rrrambl'n. This be added inbetween th' title an' th' plank list.
-
New It be now poss'ble t' print custom taxonomies anywhere 'n yer plank. See th' docs.
-
New It be now poss'ble t' adjust th' menu width fer yer whole ship. See th' docs.
-
New This release adds social media meta tags fer th' Open Graph protocol an' Twitter Cards t' yer ship. See th' docs.
-
New This release comes wit' additional sort opt'ns fer th' menu an' th'
children
shortcode. Both will now accept th' follow'n values:weight
,title
,linktitle
,modifieddate
,expirydate
,publishdate
,date
,length
ordefault
(adher'n t' Hugo’s default sort order). -
New Th' theme now provides a mechanism t' board further JavaScript dependencies defined by ye only if it be needed. This comes 'n handy if ye want t' add own shorrrtcodes that depend on additional JavaScript code t' be boarded. See th' docs.
-
New Th' theme has updated its Merrrmaid dependency t' 10.6.0. This adds support fer th' xychart type.
-
New This release adds port'ble Marrrkdown links.
Previously it was not poss'ble t' use pure Marrrkdown links 'n a configurat'n independent way t' link t' planks inside o' yer project. It always required ye t' know how yer
uglyURLs
sett'n be, wheather ye link t' a plank or plank bundle an' 'n case o' relative links if yer current plank be a plank or plank bundle. (eg.[generator](generator/index.html)
vs.[generator](generator.html)
). This be a hassle as ye have t' change these links manually once ye change yeruglyURLs
sett'n or change th' type o' a plank.Ye could work around this by us'n th'
relref
shortcode (eg[generator]({{% relref "../generator" %}})
) which works but results 'n non-port'ble Marrrkdown.Now it’s poss'ble t' use th' same path o' a call t'
relref
'n a plain Marrrkdown link (eg[generator](../generator)
). This be independent o' any configurat'n sett'ns or th' plank types involved 'n link'n. Avast, that this requires yer links t' be given without any extension, so[generator](generator/index.html)
will work as before.Th' follow'n types o' link'n be supported:
link descript'n [generator](en/configuration/branding/generator)
absolute from yer project root (multilang) [generator](/en/configuration/branding/generator)
absolute from yer project root (multilang) [generator](configuration/branding/generator)
absolute from yer current language root [generator](/configuration/branding/generator)
absolute from yer current language root [generator](./../generator)
relative from th' current plank [generator](../generator)
relative from th' current plank