Treating blog posts like production code

When I start a new project, I immediately set up a repository, linters, tests, git hooks, and CI. Not because I'm forced to, but because fast feedback loops make me a better developer. When I decided to start this blog, I asked myself: why should writing be any different? Repository setup Go to your GitHub account (https://github.com/<YOUR_ACCOUNT>?tab=repositories) and create a new repository named blog (for example). Then, set it up with the following commands: mkdir blog cd blog echo "# blog" >> README.md git init git branch -M main git add README.md git commit -m "Initial commit" git remote add origin https://github.com/davidjulien/blog.git git push -u origin main Linters Linters ensure that articles are well-formatted and consistent. Here are the linters I set up: markdownlint to check Markdown files and flag style issues. vale for writing style. ltex-ls-plus to check for grammar and spelling mistakes. lychee to check that the links in my articles are valid. Checking M