There are a couple of previous posts on here from 2016 about this, and it doesn’t appear that the documentation has ever been updated. I found some (unpublished?) documentation inside the Github repo for Hugo by searching for “author” that shines some light on this, but it’s still not clear to me how this should be utilized.
Let’s assume I’m willing to create the scaffolding of per-author profiles, and I use the authors[] array in post front matter to reference these identifiers. I am not understanding where the per-author profiles get their layout templating from?
This is important to my purpose as I’m working on adapting an existing theme I’ve been using to support h-entry and h-card microformats. I originally approached this from the perspective of single-authorship sites where /about would be an h-card and the site config would provide a fallback if front matter wasn’t present in the post, but I think expanding this to support multi-authorship is worthwhile and Hugo seems to have some of the necessary pieces already in place. In order to fully implement this though, I need to ensure that the components of an author are marked up correctly when rendered.
Based on my dive in the source code, the best I can gather is that .Site.Author is a map which contains a set of identifiers which should match to TOML files in data/_authors. Each of the files should contain values which map to Author struct in page_author.go.
Is there any plan to publish complete documentation or how authorship is intended to work in Hugo? Preferably there would be a clean fallback so that single-authorship sites (like my own) don’t have to have the extra front matter and scaffolding, but that it’s possible to support multi-authorship in the same theme.