Build one for your farm Fork, edit the JSON, redeploy. That is the whole loop.

This site is a static folder of HTML, CSS, and one JavaScript file. No framework, no build step, no backend, no SaaS. The equipment list is a JSON file. The tool renders outputs from it in the browser. The whole site is yours the moment you copy the folder.

Three ways to run it locally

1. Open the file in a browser

Download the folder, double-click index.html. The site opens in your default browser. The case study works. The maintenance tool works. You are done.

2. Edit the equipment list and reload

Open case-maintenance.html in a text editor (Notepad, TextEdit, vim, whatever you have). Find the DEMO_JSON near the top of the <script> block. Replace the three machines with yours. Save. Reload. The outputs re-render with your data. The Download JSON button on the page lets you save your edited list as a separate file for safekeeping.

3. Host it on a USB stick in a farm shed

Copy the folder onto a USB stick. Plug it into any computer with a browser. Open index.html. The site works offline. The Google Fonts load will fail (and degrade gracefully to system fonts), but everything else is local. This is the right to repair move: the tool works when the wifi does not.

What the folder looks like

vibe-coding-agroecology/
├── index.html              ← the framing page
├── case-maintenance.html   ← the case study and the tool
├── process.html            ← how M3 and the owner built this
├── contribute.html         ← this page
├── style.css               ← one stylesheet, zine aesthetic
├── README.md               ← license, structure, contributing
└── equipment-list.json     ← the canonical equipment data (optional, or inline)

What to change first

If you are forking this for your own farm, the order of edits is roughly:

Replace the three machines in the DEMO_JSON with yours. Edit the values, keep the structure.
Adjust the service interval templates in the INTERVALS object if your machines need different schedules. The categories are tractor, utility, and excavator — add yours if you have a different machine type.
Edit the parts templates in the PARTS object to match the actual fluids, filters, and consumables you use.
Edit the masthead in index.html, case-maintenance.html, process.html, and contribute.html to your own farm name, location, and edition number.
Replace the styling in style.css if you want. The variables at the top (--color-terracotta, --color-ochre, etc.) are the only things you need to change for a different palette.

You do not need to understand the JavaScript to use the tool. The JSON structure is documented in the file itself. Start with the demo and modify.

What's next

Cases that could be built with M3 next, using the same structure (zine aesthetic, plain HTML, file-based, no SaaS):

Companion planting planner — a tool for intercropping layouts and succession timing, with the agroecological framing of polyculture vs. monoculture made visible in the output.
Soil amendment log — track compost, lime, manure, cover crop rotations, and pH/OM trends across seasons. The data is a JSON file. The chart is generated in the browser.
Seed starting and succession calendar — frost dates, last/first frost windows, succession intervals. Operator-specific, farm-specific.
Pasture / grazing rotation planner — paddock sizes, rest periods, stocking density. Useful for silvopasture and rotational grazing operations.
Compost facility log — for food waste diversion operations (grocery store diversion, on-farm composting). C:N ratios, temperatures, turn schedule.
Farm map / plot layout — annotated SVG of fields, plots, infrastructure. Static file, no GIS platform.
Cost-of-ownership tracker — purchase price, fuel, maintenance, repairs, residual value. Useful for right to repair advocacy: the data shows the OEM service cost vs. the operator-maintained cost.

The framing is the same for all of them: concept → structured intake → executable artifact, with the agroecological and right to repair vocabulary intact in the output.

Tell us what you built

The honest feedback path is the GitHub Issues page for this project. Open an issue titled with your farm name and the tool you built. Include: your equipment list (or whatever data structure you used), what you changed from the demo, and what the tool enabled for you that the off-the-shelf ag software did not.

There is no analytics on this site, no newsletter signup, no SaaS feedback form. Sovereignty by design means the feedback loop is on the farmer's terms, not the platform's.