Thanks for the suggestion. It’s the kind of thing I’m hoping to avoid, because I feel the same way about it - it’s a bit of a smell to create two separate files and two separate folders to be able to have /about be my /about/index.html page.
That said, if there isn’t a way to do this cleanly, I’ll go ahead and do that to make it work (though, will pages that aren’t the top-level homepage have access to all of the variables for the rest of the postings & taxonomies as well?)
It would be nice though, if you could define a list of files in the config.yaml that you’d like processed in addition to the index.html that represents your homepage, and that they’d be treated in a similar fashion, but could have different paths/names. So, for example, I might provide this in the config.yaml:
mainPages :
“index.html” = “/index.html”
“about/index.html” = “/about/index.html”
“contact/index.html” = “/contact/index.html”
Hugo would see this and realize it needs to not only run against my /layout/index.html, but also against /layout/about/index.html and /layout/contact/index.html and where to put the resultant files.