The latest articles on DEV Community by Cornel Cristian Filip (@cornellfilip). https://dev.to/cornellfilip https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F345443%2F598874f0-840d-4b4c-a2b9-b44e14f10877.png https://dev.to/cornellfilip en Cornel Cristian Filip Tue, 14 Jul 2026 22:07:16 +0000 https://dev.to/cornellfilip/your-repo-should-be-the-source-of-truth-not-the-platform-4pk https://dev.to/cornellfilip/your-repo-should-be-the-source-of-truth-not-the-platform-4pk <p>Here is a principle I keep coming back to: the canonical version of everything I write should live in a git repo I control, in plain markdown, not locked inside Ghost or Beehiiv or Dev.to. Platforms come and go. The repo outlives them.</p> <p>The problem is the last mile. Once the markdown is in the repo, getting it onto each platform means reformatting by hand, because every channel treats headings, fenced code blocks, and images differently. It is the least interesting work in the whole pipeline, and I do it over and over.</p> <p>I want to fix that with Fmttr: your repo stays the source of truth, and a deterministic pipeline transforms and publishes each post to the channel it is mapped to on git push. Correct formatting per platform, from one markdown source.</p> <p>I am validating the idea before writing the product. If your repo is already your source of truth and the publishing step is the annoying part, tell me: <a href="https://fmttr.dev/?utm_source=devto" rel="noopener noreferrer">https://fmttr.dev/?utm_source=devto</a></p> <p>Building in public on X: x.com/cornellfilip</p> writing markdown productivity buildinpublic