I think we can cross some of these bridges when we get to them… we have some nice automation set up to auto-publish docs.farmos.org right now via GitHub Actions, so I’d want to make sure we have the same level of ease in a Gatsby-aggregated approach.
How do we want to orchestrate moving docs for the Aggregator and Field Kit into their respective repos, similar to how @mstenta has done for the farmOS docs?
The Aggregator docs are already in their own repo (just in a README.md now):
We do need to figure out the User Guide… which currently has both farmOS and Field Kit info in it.
At what point do we want to move the User Guide into a separate repo? (plus lots of other related considerations around the maintenance of that repo)
This needs more dedicated thought. We will have a 1.x User Guide, which I think we can just set up as a legacy site on 1x.farmos.org or something… and we will have a 2.x User Guide, which we are talking about building directly into farmOS itself: Inline user guides
That doesn’t include “contrib module” user guides, though, nor does it include Field Kit. So perhaps we should think about ways in which we can pull a “master” user guide together from multiple sources. This could include user guides from ALL modules (and other repos), whereas the “inline” guide would only have content for the modules that are enabled.