KnowTheYard is built as a structured publishing system. This page explains how route ownership, content contracts, and review-lane attribution work in the live app.
We do not treat content quality as a last-mile cleanup step. On KnowTheYard, weak trust claims, guessed links, and raw rendering artifacts are considered upstream defects.
The site currently publishes 555 public pages, including 230 plant profiles. Public review-lane totals are generated from the live content repository, not copied into pages by hand.
Each published page type has its own contract. Plant profiles, guides, comparisons, and problem pages are not interchangeable templates; the renderer and the content shape need to agree on what each route can display.
That contract-first approach is what lets us count live content accurately, render internal links predictably, and prevent trust pages from drifting away from runtime reality.
Zone-aware content matters only when the route is real and the link destination exists. We therefore prefer explicit category-qualified links and known slug maps over guessed destinations that can silently create soft-404 behavior.
The same principle applies to trust pages: the source of truth for counts and review-lane attribution belongs in code and content, not in freehand copy.
Plant profiles, guides, comparisons, and problem pages each follow an owner-specific content shape.
Links should resolve to published routes only. Unknown slugs are treated as defects instead of being guessed at render time.
Public review totals are derived from the `reviewedBy` field in live content files rather than separate marketing counters.
Raw artifacts, stale claims, and broken CTAs are fixed in the owning page or source file first.
Report broken links, raw content artifacts, or factual errors through the contact page.