A year of garden planning was trapped in notebooks and our heads. So I shipped it: a fast, public, version-controlled site for Zone8a gardening. Here is the method, and why it transfers to almost any knowledge worth keeping.
Most of what we know decays in place. A year of planning one garden lived in a Google Doc, a few conversations, and our own memory. None of it was searchable, none of it was easy to correct, and none of it would survive a dead laptop. That is the natural state of expertise: privately held and slowly forgotten.
So I decided to treat one season’s worth of it the way I treat production software. Not as a metaphor, but rather version control, a schema, a build step, automated deploys, and a public URL. The result is a small site, and a method I would now reach for with almost any body of knowledge worth keeping.
One bed, three crops
The content is a single raised bed in USDA Zone 8a, run as a relay across one year. Spring spinach goes in early and comes out by late spring. Summer bush beans follow and fix nitrogen, rebuilding what the spinach drew down. Then a fall and winter run of brassicas, broccoli, cabbage, kale, and collards, that inherit a bed fed twice and sweeten as the cold sets in. Each handoff is deliberate.
That is not the whole garden. Zone8a gardening starts deliberately small, and we will add the other five beds to the site.
Zone 8a Gardening Knowledge as a Product
Here is what treating it like software meant in practice.
- Version control is the source of truth. Every guide and journal entry for Zone8a gardening lives in GitHub. Every change is reviewed and traceable, so I can see what I claimed, when I claimed it, and why I revised it. History is the audit trail.
- A schema that refuses bad data. The content is typed in Markdown and validated against a schema. A missing field or a malformed date fails the build, not the reader. The structure enforces predictability for constant releases.
- A build step that does the tedious work. Photos are optimized into responsive WebP at build time, and every page is pre-rendered to static HTML. Nothing ships heavier than it needs to.
- Automated deploys. A push to the main branch rebuilds the site and ships it to Cloudflare’s global edge. There is no manual publish step, and no server to patch or pay for around the clock.
None of this is exotic. It is the ordinary stack of modern web work. The only novelty is pointing it at a body of personal knowledge instead of at an app. We are pleased that it is also very easy to view on mobile when working in the garden.
Why it transfers
The reason this is worth writing about has nothing to do with vegetables. Four things hold for any expertise you would rather not lose.
- Public beats private for anything reusable. Knowledge locked in a drive helps no one and deteriorates over time. Made public and precise, it compounds: other people correct it, extend it, and adapt it. A grower in another zone shifts the dates, and the method travels.
- Plans are not proof. A plan in your head feels finished. Written down precisely enough to repeat, it shows you its gaps. Building it against a schema and a build surfaced errors that prose alone would have hidden.
- The medium enforces the rigor. I did not have to remember to be disciplined. The build failed when I was sloppy. Good systems make the right thing the easy thing.
- It is cheap to own. Static output on a serverless edge costs almost nothing and stays fast worldwide. Owning your knowledge no longer means running infrastructure.
I will keep adding to it, through the August transplant window and into the winter harvest, and the record gets more useful as it accumulates. But the durable takeaway is the method, not the bed. Most of us are sitting on a season’s worth of hard-won knowledge in some domain we actually care about. It would be more useful to us, and to everyone who comes after, as a small, well-built, public thing than as another document no one opens.
The working example is at zone8a.com. The repo is on GitHub.
Two ways to follow what’s next
New writing lands here first, then goes out via Substack. Conversations happen by appointment.







