Python Insider Blog Embraces Git-Based Workflow with New Home

The Python Insider Blog has officially moved to a new location at https://blog.python.org, powered by a Git repository. This change simplifies contributions, improves version control, and makes it easier for anyone to help write posts about Python releases, core sprints, governance updates, and more. All 307 posts from the old Blogger platform have been migrated, and old URLs automatically redirect. Your RSS feed should update automatically, but if not, the new feed URL is https://blog.python.org/rss.xml. Below, we answer common questions about the move.

Why Did the Python Insider Blog Move?

The decision to relocate the blog stemmed from a desire to lower the barrier for community contributors. Previously, contributing required a Google account and familiarity with Blogger’s editor—a steep hurdle for many. The new setup is built around a Git repository hosted on GitHub. Now, anyone comfortable with Markdown and pull requests can submit a post. The entire blog lives as a collection of Markdown files, making version control, collaboration, and review much more streamlined. This change also future-proofs the blog against platform dependencies and opens up automated workflows for deployment and testing.

How Can I Contribute a Post to the New Python Insider Blog?

Contributing is straightforward. First, fork the repository at https://github.com/python/python-insider-blog. Next, create a new directory under content/posts/ using your desired post slug. Inside that directory, add an index.md file—this is your post. You can also include images by placing them in the same directory. Finally, open a pull request with your changes. The repository’s README offers further details on frontmatter fields and local preview setup if you’d like to check your formatting before submitting. That’s it—no special tools beyond a text editor and Git.

What Structure Does a Blog Post Follow in the New System?

Each post lives in its own folder: content/posts/{slug}/index.md. The Markdown file includes YAML frontmatter at the top that defines the title, publication date, author(s), and tags. The post content follows in standard Markdown. Images are stored alongside the index.md file in the same directory. This flat structure makes it easy to bundle all assets for a post together. No special CMS or file upload interface is needed—just a text editor will do. For those who prefer a visual editor, a Keystatic CMS is available during local development, but it’s entirely optional.

What Technology Powers the New Blog?

The site is built with Astro, a modern static site generator, and deployed as fully static HTML for fast performance. Styling is handled by Tailwind CSS. The entire build and deployment pipeline runs through GitHub Actions, so every pull request automatically triggers a preview and production update. For contributors who prefer a GUI, a Keystatic CMS can be activated in development mode. This tech stack ensures the blog is maintainable, scalable, and easy to contribute to without heavy infrastructure.

What Happens to the Old RSS Feed and Blog URLs?

All 307 posts from the Blogger era have been successfully migrated to the new site. Old URLs automatically redirect to their new counterparts, so existing links won’t break. The RSS feed has changed; the new feed URL is https://blog.python.org/rss.xml. Most RSS readers should detect the new feed automatically. If yours doesn’t, simply update the subscription to the new URL. The feed follows the same standard format, so you’ll continue receiving updates as before.

Where Can I Find the New Blog and Repository?

The new home of the Python Insider Blog is https://blog.python.org. All source code and content live in a public GitHub repository at https://github.com/python/python-insider-blog. If you encounter any broken links, missing images, or formatting issues caused by the migration, please file an issue on the repository. Pull requests to fix problems are also very welcome. The community’s help is invaluable for polishing the migrated content and improving the blog experience.