- their worktrees will become stale, and I need to add somewhat automated checking how far behind they are
- their stale worktree will have conflicts, and dealing with merge conflicts in a pedagogical way is a big task
- working on multiple things at once is possible, but introducing "committed" on top of "draft" + "publish" adds mental gymnastics
- using the filesystem as a database makes deployment to Kubernetes less trivial because you need persistent storage
One thing you get "for free", though, is authentic preview: Since the final site is a static site, I can just run the generator when the user wants to see a preview.