Joe Mooring
Joe Mooring
Closing in favor of https://github.com/gohugoio/hugo/issues/13401.
This would be another opinionated change to one of Hugo's embedded templates; I am not in favor of doing this. If it were up to me I would remove Hugo's...
I'm saying that this should be implemented at the theme or site level.
In my view many of the embedded templates are, at best, opinionated examples, and _should_ be overwritten by theme authors to achieve the desired outcome. Over the years I've examined...
> but a mapping of each authors fediverse id Yet another reason for handling this at the theme or site level.
Support `extension.WithFootnoteIDPrefix` (aka `footnoteAnchorPrefix` for Blackfriday) for `goldmark`
There are at least two use cases when rendering a list page, and each use case requires a different `href` attribute. ### Example 1 ```text {{ range site.RegularPages.ByTitle }} {{...
Support `extension.WithFootnoteIDPrefix` (aka `footnoteAnchorPrefix` for Blackfriday) for `goldmark`
Another approach, if you want to render the content and not just the summary, is to create a list shortcode. ### Example 3 ```text {{ range site.RegularPages.ByTitle }} ## [{{...
Support `extension.WithFootnoteIDPrefix` (aka `footnoteAnchorPrefix` for Blackfriday) for `goldmark`
Your particular use case corresponds to both Example 1 and Example 3 above. Both examples have the same footnote number for each item on the list, which doesn't make any...
Support `extension.WithFootnoteIDPrefix` (aka `footnoteAnchorPrefix` for Blackfriday) for `goldmark`
> previously, with blackfriday, we could achieve example 1 with correct links Out of curiosity, was this handled via a front matter field unique to each page, or something else?
Support `extension.WithFootnoteIDPrefix` (aka `footnoteAnchorPrefix` for Blackfriday) for `goldmark`
> [!note] > This approach does not support pagination. If each footnote reference within a given page collection is unique, use the approach shown in Example 3 above. Try it:...