Joe Mooring

Functionally this is great! Thank you. The next step is a review by bep.

> /categories/a/_index.md and /categories/b/_index.md Both filenames are _index.md. Not sure why you would want to do this. Seems like you want this instead: ``` [permalinks.term] categories = '/:slug/' ```

https://github.com/gohugoio/hugo/blob/68e95327f7be941c44c256d2dac74ea96e731674/resources/page/permalinks.go#L265-L277 Examining the above, the `:filename` token is limited to kind `page`. Before leaf bundles were introduced, "filename" was an accurate description. Then we introduced leaf bundles, and "filename" became...

> I'm not sure that introducing :contentbasename is necessary 1. Changing the meaning of `:filename` may change some sites. I've been bitten by the "doesn't seem likely to me" assumption...

While updating to match current behavior, adding exceptions to the documentation is clumsy and a bit convoluted (e.g., "This applies to xxx but not to yyy."). I think we should:...

Is this template function for convenience, instead of doing this in site configuration or on term page (e.g., content/authors/jmooring/_index.md)? ```text params: - social: handle: '@jmooring' url: https://github.com/jmooring/ - social: handle:...

I would say you can't get **some** users to input structured data. Whether or not "some" represents a majority is debatable.

Thinking about this more, adding the ability to set markdown attributes on `dt` elements is probably the best way to handle this. For example: ``` Term A {#foo} : Description...

I don't really care one way or the other. My only thought is, do we even want a published schema for this? The first thing I did after switching to...

markdown ``` {{< a >}}{{< b >}} ``` layouts/shortcodes/a.html ```text a\n ``` layouts/shortcodes/b.html ```text b\n ``` rendered in browser (what you see): ```text a b ``` So, after the proposed...