Using alerts as a arbitrary block level fabricators, to make complex legends/figcaptions

tips & tricks
1

Hi,
This alert system is really the gift that keeps on living.
A few years ago when I started hugo I had to struggle with getting complex layouts while keeping myself to markdown and as much as possible to one single scheme with templates, avoiding shortcodes. It was difficult because markdown was limited.
Now it covers semantically natively a lot more than before with all those extensions, and when it doesn’t, render-hooks have become the powerful generalist constructors for both block and inline elements. Everytime I want some functionality I’m amazed at how straightforward the code is. Much less hacky than before.
Last invention: getting complex, multilines/multi-paragraph legends (science papers come to mind) or figcaptions was difficult inside the .Title attribute, and ugly visually.
Now I use this before the image:

> [!LEGEND] path/filename.jpg
> legends with arbitrary description and inside
> 1. list
> 1. [णȪ link](to_wherever.com)
>
> and **paragrpahs**

which goes through {{ .Page.Store.Set .AlertTitle .Text }}
then fetched by the images:

{{- with .Title -}}<figure>{{- end -}}
<img src="{{ $path | relURL }}" {{with .Attributes.class}}class="{{.}}"{{end}}  alt='{{ default "image illustrative" (.Text | htmlUnescape) }}'>
{{- with .Title -}}<figcaption>{{.}}</figcaption>{{- else with (.Page.Store.Get .Destination) }}{{.}}</figcaption>{{- end -}}</figure>

alerts make this kind of thing much, much more elegant than before :heart_eyes:

2

I use “links” similarly to create arbitrary inline containers not covered with other markups. For instance [link](V) makes <span class="bascule">link</span>, [link]([V,P,COLOR] "red") becomes <span class="bascule prepositin" style="color:red">link</span> and more.
In another project they made buttons and iframes instead of links. After all, from an hypertext point of view, it is the same.
Very powerful !