CROP Documentation

Centralized reference for the CROP front-end. Every guide below reflects the current Next.js 16 + React 19 implementation that powers the parts catalog experience.

Table of contents

• Architecture overview
• Feature specs
  • Parts search bar
• Component notes
  • Experimental product components
• Data drops
  • McHale media manifests
• Tooling
  • Moby design system validation scripts
• Testing & Quality
  • Testing Strategy - Comprehensive testing guidelines

Usage

• Keep product docs in this folder (sub-directories encouraged for structure).
• When adding a new feature, create a docs/<area>/<feature>.md entry and link it here.
• Folder-level READMEs inside components/, data/, etc. are no longer allowed—link back to this index instead.

Updating the docs

1. Make a focused change alongside the feature code.
2. Run bun run lint to ensure markdown linting (Biome) passes.
3. Mention the doc updates in your PR description.

The root README.md now only summarizes quick-start steps; the living documentation stays here.