Continuing the discussion from Making a website: talkgroup:
Before I can move forward with any making actions, I need to get my repos in order. Until now I’ve always saved everything into a single repo, but that was never the plan. I’d like to keep content and the site configuration separate, at the very least. But also I think all kinds of content might have better stewardship if I can dice it up and hand it out.
Thesis: there will be advanced sharing scenarios where this makes sense.
So how shall I slice this? Hmmm…
For interi I created an org on allthe.codes: interi - allthe.codes
I’ll likely start with a configuration or build repo, and then add content, themes and components, and anything else I might need, one repo at a time. For content I plan to add each section as a git submodule. I want this to repo to be one that can quickly pull down all the parts of the HTTPS web version. For other versions, they’ll have their own build/config repos.