Content Audit and Knowledge Normalization Plan¶
Purpose¶
This page defines how NoMad's Farm separates universal knowledge from active projects, field observations and personal reflection.
The goal is to prevent the site from becoming tied to one greenhouse, one balcony or one field site.
The site should function as:
Practical Handbook
+
Project Documentation System
+
Field Observation Archive
+
Personal Journal
Core Rule¶
Knowledge Base = universal principles and practical handbook
Projects = current applications and active work streams
Journal = dated observations and records
Zen = personal reflection and photo essays
This means pages such as Soil, Water, Site Assessment, Crop Matrix and Plant Profiles should not be written only around one active location.
They should explain what to observe, why it matters and how to apply it across different projects.
Content Types¶
| Type | Purpose | Examples |
|---|---|---|
| Knowledge | Universal practices, concepts and methods | Soil health, water management, plant profiles |
| Project | Active work stream generating data and experience | Sprout Lab, Greenhouse 2026, Gaitanevo 2026 |
| Journal | Dated observations and records | Field notes, crop results, failures |
| Reference | Source hierarchy and external materials | USDA, NRCS, JIRCAS, extension publications |
| Zen | Personal reflection and visual story | Notes, images, lessons, philosophy |
Knowledge Base Direction¶
The Knowledge Base should become a practical field manual.
Primary source families:
- USDA;
- NRCS;
- JIRCAS;
- university extension publications;
- peer-reviewed research;
- NoMad's Farm observations.
NoMad's Farm observations should support and refine the handbook, not replace source hierarchy.
Page Classification¶
| Current Page | Target Role | Notes |
|---|---|---|
| Source Hierarchy | Reference | Defines trusted source order |
| Soil Ecological Processes | Knowledge | Universal soil biology and function |
| Soil Improvement Strategy | Knowledge | Practical soil management handbook |
| Site Assessment | Knowledge | Universal field/site assessment checklist |
| Plant Profiles | Knowledge | Crop and species reference |
| Functional Groups | Knowledge | Ecological and production roles |
| Crop Matrix | Knowledge / Decision Support | Universal comparison tool |
| Water Systems | Knowledge | General water planning and management |
| Infrastructure | Knowledge | Practical infrastructure concepts |
| Monitoring & Automation | Knowledge | General measurement and control systems |
| Sprout Lab | Project | Active indoor production system |
| Microclimate Lab | Project | Active/planned monitoring system |
| Balcony Pot House | Project | Active balcony container system |
| Greenhouse 2026 | Project | Active protected cultivation project |
| Gaitanevo 2026 | Project | Active field program |
| No-Maintenance Squash Trial | Project / Trial | Seasonal trial across scattered pits |
| Field Journal | Journal | Dated observations |
| Zen | Zen | Personal reflections |
Universal Knowledge Page Template¶
Use this structure for handbook pages:
Overview
Core Concepts
What to Observe
Field Indicators
Common Problems
Management Practices
Practical Checklist
Source Notes
NoMad's Farm Notes
The key section is What to Observe.
The site should teach what to look for in soil, plants, water, climate and infrastructure before prescribing action.
Project Page Template¶
Use this structure for active project pages:
Overview
Status
Location
Type
Objectives
Current State
Metrics
Methods
Observations
Related Knowledge
Related Journal Entries
Next Actions
Projects feed data into the Knowledge Base, Plant Profiles, Crop Matrix and Field Journal.
Source Hierarchy¶
Recommended hierarchy:
Tier 1: USDA / NRCS / JIRCAS
Tier 2: University extension publications
Tier 3: Peer-reviewed research
Tier 4: experienced grower reports and case studies
Tier 5: NoMad's Farm observations
The local project data is valuable because it is specific to our conditions.
It should still be marked clearly as observation, not universal fact.
Site Assessment Direction¶
Site Assessment should become universal.
It should answer:
- what to observe before working a site;
- how to describe access, slope, water and exposure;
- how to record soil condition;
- how to identify risks;
- how to compare locations;
- how to connect a location to active projects.
It should not be written only for one greenhouse or one field.
Soil Direction¶
Soil pages should become a practical soil health guide.
Core topics:
- soil structure;
- organic matter;
- compaction;
- infiltration;
- biological activity;
- cover crops;
- mulch;
- compost;
- root systems;
- field diagnostics.
Plant Profiles Direction¶
Plant profiles should remain universal.
Each profile should eventually include:
Scientific classification
Ecological role
Climate range
Soil requirements
Water requirements
Human use
Seed production
Management
Companion use
Risks
References
NoMad's Farm Notes
The final section is where project-specific observations belong.
Crop Matrix Direction¶
The Crop Matrix remains a universal decision tool.
Project observations can refine scores over time, but the matrix should not become specific to only Gaitanevo, Baylovo, the balcony or the indoor lab.
Next Actions¶
- Normalize Site Assessment into a universal checklist.
- Normalize Soil pages into a field handbook.
- Add source notes using USDA / NRCS / JIRCAS structure.
- Add project metadata blocks to project pages.
- Add
NoMad's Farm Notessections to Plant Profiles. - Keep URLs stable until migration is clearly needed.
Migration Principle¶
Do not delete categories, crops, matrix data or existing pages during normalization.
Add structure first.
Move content only when the target structure is clear.
This avoids turning the documentation into compost before it has produced any harvest.