Could the Content folder play a part in allowing a MultiSite style of setup?
By default Hugo outputs content to the “public” folder…
// Runs default content folder to default output folder
Thanks to one of @natefinch’s many support posts, I noticed there’s a Destination flag (-d) available that allows you to override the default “public” output folder, like so…
hugo -d customOutputFolder
// Runs default content folder to custom output folder
So in the same manner as the Destination flag, could there be a Content flag (-c) that allows you to set a custom content folder which overrides the default “content” folder?
hugo -c customContentFolder
// Runs custom content folder to default output folder
This would allow content for entirely separate websites to sit inside a single Hugo install. The “content” folder could remain the default content folder for when no -c flag is run (just as “public” is the default output folder when -d is not run), and additional content folders could just be named accordingly.
hugo -c website1Content -d website1Output
hugo -c website2Content -d website2Output
hugo -c website3Content -d website3Output
// Runs custom "content" folders to custom output folders
It’s probably not that simple, but who knows. And while most folk probably aren’t trying to run multiple websites with Hugo, requiring one Hugo install per website is a real barrier. And when you’re using the same theme for all those websites, requiring one Hugo install per website is a real pain in the arse. If there could be a way to house separate content in a single Hugo install that would make Hugo even greater than it already is.
Especially when you could then easily run any website content to any output folder via any theme…
hugo -c website1Content -t allHailHugo -d website1Output
// Runs custom "content" folder to custom output folder