A small publishing surface built around practical continuity.
MerceMay Archive is not a product catalog and not a personal diary. It sits in the middle: a maintained static site for working notes, project records, reading trails, and field observations.
The site exists to hold material that should remain readable without a login.
The archive emphasizes direct files, stable links, lightweight dependencies, and content that remains useful when revisited months later. That means fewer moving parts, less abstract framing, and more attention to concrete decisions.
- Write in formats that can be served and copied directly
- Prefer archive depth over one-page polish
- Keep operational context near the visible output
Each update follows the same cycle from observation to publication.
Observe
Collect friction points, recurring questions, and patterns noticed during actual work.
Test
Try the smallest viable fix first, then record what changed and what stayed noisy.
Publish
Turn the experiment into an entry, guide, or case file with enough context to reuse.
Maintain
Revisit pages, repair links, and keep the archive from becoming a pile of abandoned drafts.
Useful archives look inhabited.
A believable static site needs multiple kinds of pages, not just a marketing front. That means summaries, dense notes, FAQs, case files, and library pages that support different reading speeds.