Your repo should be the source of truth, not the platform

Short summary

The author argues that canonical content should live in a developer-controlled git repo rather than being locked inside publishing platforms like Ghost or Beehiiv. They are building Fmttr, a deterministic pipeline that transforms and publishes markdown to each mapped platform on git push. The post is primarily an idea-validation pitch seeking signups before the product is built.

• •Principle: keep canonical content in a git repo, not locked in publishing platforms
• •Fmttr would transform one markdown source into correctly formatted posts per platform on git push
• •Author is validating the idea before building; post is largely a signup pitch

Generated with AI, which can make mistakes.