(same comment I made on the GitHub issue… not sure where it belonged)
I’m a big believer in the KISS principle. I think Hugo should stick to one function, that is to transform source content (provided in as simply specified as possible structure of files) into a set of static web pages.
Editing or syncing source content from multiple devices should be solved elsewhere. There are many other avenues to address this. For example:
- One each device use an editor that can write to the single contentDirs. For example there are editors on all devices that can edit GitHub files, or DropBox files. So pick one location and then choose the editors that work with that. For example on iOS you can use Editorial + WorkingCopy to edit and publish Markdown your mobile device.
git inti --separate-git-dir or
git clone --separate-git-dirso that your
contentDir working tree is in DropBox but your repository (
.git dir) is not (to avoid syncing all the repo data, and to avoid allowing DropBox sync to corrupt it.). Edits made via your mobile device will be automatically seen on your main computer, from which you can commit the changes into the repo (and push into GitHub).
- Us a syncing tool. For example, one that pushes new content from DropBox into GitHub.
I personally use the first two options. They both work well. The first option for when I have to get something published immediately from my mobile device, and the second for when I’m simply doing authoring on my mobile device that can be published later, via my laptop.
I also think the OP’s specific use case is problematic and misguided. The whole point of using git or GitHub for the contentDir is so that the source content is all under source control with full history and change tracking.