Quarantine Bad Content, Don't Crash the Build
· 1 min read
An n8n workflow commits MDX to this repository. That makes frontmatter an integration contract rather than a personal convention, and it means bad input is a matter of when, not if.
Strict builds are the wrong default here
If a malformed push fails the build, a pipeline glitch at 2am blocks an unrelated bugfix deploy at 9am. The blast radius of one bad file becomes the entire site.
Quarantine instead
Each file is parsed and validated on its own. Failures are skipped and logged; everything valid ships. A separate strict CI job fails loudly, so the degradation is visible within a minute.
The trade-off is explicit: a broken push loses one article, never the site.