Markdown blog

The ledger separates what the audit changed, what was kept on purpose, and what has not run in production yet.

1. Fixed in the templates

   • gray-matter's cache turns one bad file into a blank post, forever The highest-severity finding, live in the earlier implementation. gray-matter@4 memoizes by content string and writes its cache entry before parsing, so a file whose YAML throws leaves an empty { data: {} } behind. The module's fallback parser runs on the first parse and produces correct frontmatter; the second and every later parse of that file returns {} — no error, no frontmatter — and the fallback never runs again.
   • Translated posts silently lost their related-posts section getRelatedPosts read the current file's own related array. Relations are authored as default-locale slugs, and translators generally did not copy the block, so the section simply did not render. Measured on the earlier implementation's content: every default-locale post had related posts; most translated posts had none. No error, no empty state: the section was conditional on post.related?.length, so it vanished.
   • 71x file-read amplification at build time No memoization anywhere in the content layer. getAlternateSlugs calls getAllPosts once per locale and runs once per page in generateMetadata. Measured: every content file read about 71 times per build, each read followed by a full gray-matter parse. The cost is quadratic in post count.
   • A stray dotfile fails the entire build getPostSlugs returned every directory entry unfiltered; getPostBySlug appended .md. On any macOS checkout where Finder has opened the content folder, that is readFileSync(".DS_Store.md") → ENOENT → build failure, reported against a file the author never created.
   • Tag pages lose posts to spelling drift getTagFromSlug resolved a URL slug to the first matching label alphabetically, then posts were filtered by that exact label. Two spellings of one tag ("AI Agents" / "AI agents") slug identically, so one variant's posts were absent from the only page they belonged on — and generateStaticParams emitted duplicate params. Not triggered in the earlier implementation (checked: every locale's tag slugs, zero collisions on audit day), but the mechanism is live and hand-authored frontmatter drifts.
   Show 7 moreShow fewer

   • Every card claimed "5 min read" A literal 5 in the card component, on every post, in every language.
   • Draft visibility depended on a routing flag getPostBySlug did not filter drafts. Drafts stayed out of production only because dynamicParams = false meant an unpublished slug was never a valid route. Enabling dynamic params for any reason — a legitimate change nobody would connect to drafts — would make every draft publicly reachable.
   • Locale list declared five times ["en", "pl", "de"] appeared in the loader (twice), both blog route files, and the path helper — while a LOCALES config module existed and was used only by the sitemap. Adding a locale meant finding four other copies.
   • Untranslatable strings on the tag page The tag page carried an inline { en, pl, de } map with an English || fallback — so a fourth locale would serve English with no missing-key signal — and its meta description hardcoded English marketing copy into every locale's tag pages. Pluralization used article${n !== 1 ? "s" : ""}, an English rule in code.
   • Dates formatted as American English for German readers lang === "pl" ? "pl-PL" : "en-US". Also, the post page passed timeZone: "UTC" and the card did not, so the same date could render one day apart on the index and the article.
   • getPostBySlug threw, and callers swallowed it Every caller wrapped it in try/catch, which made a real disk error indistinguishable from a missing post and let getRelatedPosts discard misconfigured relations with catch { return null }.
   • Frontmatter regex unanchored and CRLF-intolerant /---\n([\s\S]*?)\n---\n([\s\S]*)/ matched a --- horizontal rule in the body of a file with no frontmatter, and failed outright on CRLF line endings.