Site Evaluation and Roadmap
veggie.farm has the beginning of a useful structure: Markdown articles, section routing, Observable Framework navigation, light and dark theme support, and a small set of original garden illustrations.
The larger problem is content depth. Many pages still read like seed notes: useful direction, but not yet enough explanation, context, data, or practical decision support. A strong gardening reference needs to help a reader decide what to do in a specific bed, climate, season, and soil condition.
Current state: structurally sound, visually calm, and ready for expansion.
Main gap: most articles need stronger narrative, specific growing guidance, tables, and decision points.
Long-term goal: a data-driven field guide for planning gardens, improving yields, understanding soil, and choosing crops by climate and space.
What is working
The site now has a clear editorial direction. The voice is quiet and practical, which is the right foundation for a reference site. The section structure also makes sense: garden practice, vegetables, fruits, herbs, soil, compost, wildlife, calendar, reference, and field notes.
The illustration style is also directionally useful. Images should support the page, not replace the page. For technical information, captions and tables should carry the exact meaning while images provide orientation.
What needs improvement
The current content is uneven. Some pages have a good starting voice, while others repeat generic paragraphs. Crop pages often share the same sections without enough crop-specific detail. Soil pages should be more distinct from one another. Section landing pages need to become useful indexes rather than short introductions.
The data layer is also early. The site should eventually know enough about a plant to support filters, comparison tables, planting calendars, rotation planning, and spacing tools. That requires structured data, not only prose.
Editorial model
Each article should eventually answer five questions:
- What is this page really about?
- What decisions does the gardener need to make?
- What conditions change the answer?
- What observations should the gardener record?
- What nearby pages or data help complete the decision?
For crop pages, that means timing, spacing, soil, water, harvest, common problems, and field notes. For soil pages, it means diagnosis, practical tests, what to change, what not to change, and how to observe improvement over time.
Data model
The first structured data files should support:
| Data file | Purpose |
|---|---|
vegetables.json |
Crop family, season, frost tolerance, planting window, spacing, maturity, and rotation notes |
fruits.json |
Fruit type, establishment time, bearing age, and main care practices |
herbs.json |
Herb season, use, and care pattern |
pests.json |
Symptoms, favored conditions, and first response |
beneficial-insects.json |
Ecological role, pest relationships, and habitat |
Later, the site should add zone-aware planting windows, soil test interpretation, bed-planning dimensions, crop succession rules, and harvest windows.
Content batches
The work should proceed in batches rather than trying to perfect every page at once.
| Batch | Work |
|---|---|
| Foundation | Expand soil testing, plant spacing, seasonal calendar, beneficial insects, and section landing pages |
| Core crops | Rewrite tomatoes, peppers, lettuce, carrots, beans, cucumbers, potatoes, peas, and garlic as full crop guides |
| Soil system | Rewrite clay soil, sandy soil, mulch, compost as soil practice, and building healthy soil with distinct roles |
| Perennial food | Expand fruit pages with establishment, pruning, harvest, and long-term care |
| Planning tools | Add crop filters, spacing tables, rotation groups, seed-starting timelines, frost date helpers, and zone-aware calendars |
Quality bar
A finished page should not feel like a generic gardening blog post. It should feel like something a gardener can return to during the season.
Each finished article should include:
- a clear opening argument;
- a practical summary table;
- crop- or topic-specific guidance;
- one or more decision tables where useful;
- a field notes section;
- related links;
- accurate alt text for images;
- readable light and dark mode rendering.
Field notes
The site should keep its notebook character. Field notes are not decorative. They are where the article becomes practical: what to watch, what to record, and what changes the next decision.