Garden Planner Requirements

veggie.farm should eventually help gardeners plan a garden, not only read about gardening.

The planning tool should connect bed layout, crop data, local climate, plant spacing, rotation history, succession planting, and field notes. It should feel like a practical notebook with useful calculations, not a decorative design toy.

Feature roadmap

Product principles

The planner should help gardeners make better decisions:

• how many plants fit in a bed;
• when to sow, transplant, protect, and harvest;
• which bed should avoid a crop family this year;
• where trellises, paths, water, and shade create constraints;
• which crops can follow early crops;
• what actually happened compared with the plan.

Data before interface

The interface should not outrun the data. A spacing tool requires reliable spacing data. A planting calendar requires frost dates, crop tolerance, days to maturity, and local adjustment. Companion planting recommendations require source evidence and clear limits.

Suggested build order

1. Bed and crop data model.
2. Static bed layout and crop placement.
3. Spacing warnings.
4. Planting calendar by frost date.
5. Crop family rotation memory.
6. Journal entries linked to beds and crops.
7. Succession and harvest reports.
8. Companion and ecology recommendations.

Field notes

The planner should preserve uncertainty. Gardeners need useful starting points and visible assumptions, not false precision.