Introduction
If you’ve been following the official Python blog, you might have noticed a fresh change: the Python Insider has moved to a new address. The blog now lives at blog.python.org, backed by a modern Git repository. This shift isn’t just about a new URL—it’s a fundamental overhaul of how the blog is managed and how you can contribute. All 307 posts from the old Blogger platform have been successfully migrated, and old URLs automatically redirect to the new ones. Your RSS feed should update without any manual intervention, but if you encounter issues, the new feed URL is blog.python.org/rss.xml.
Why We Moved
Blogger served the Python community well for many years, but it came with limitations. To contribute a post, you needed a Google account and familiarity with Blogger’s editor—a barrier that discouraged potential authors. The new setup eliminates those hurdles entirely. Now, the blog is built from plain Markdown files stored in a Git repository. If you can open a pull request on GitHub, you can write a post. No special tooling beyond a text editor is required.
Posts reside in the directory structure content/posts/{slug}/index.md, with YAML frontmatter defining the title, date, authors, and tags. Images are placed right next to the post’s Markdown file, keeping everything organized. This approach makes the blog more accessible, flexible, and transparent.
How to Contribute
Want to write about a Python release, core sprint, governance update, or any other topic that belongs on the official Python blog? Here’s the short version:
- Fork the repository at github.com/python/python-insider-blog.
- Create a new directory under
content/posts/with your chosen post slug (e.g.,my-new-post). - Add an
index.mdfile inside that directory with your content in Markdown. Optionally, upload any images into the same folder. - Open a pull request (PR) against the main repository.
The repository’s README provides more detail on frontmatter fields and local development if you want to preview your post before submitting. The bar for contributing is now very low—anyone with a GitHub account can propose a blog post.
What’s Under the Hood
The new site is built with Astro, a modern static-site generator, and deployed as fully static HTML for speed and reliability. During development, a Keystatic CMS is available if you prefer a visual editor over raw Markdown, but it’s entirely optional. Tailwind CSS handles styling, giving the blog a clean, responsive design. The entire build and deployment process is automated through GitHub Actions, ensuring that every merged pull request goes live quickly and consistently.
This technical stack was chosen for simplicity and maintainability. Astro compiles pages into static assets, so the blog loads fast without requiring a database or server-side processing. The use of Markdown and Git makes version control natural—every change is tracked, and contributions are easy to review.
What This Means for Readers
For regular readers, the experience remains largely the same. The blog is still the go-to place for official Python news, release announcements, and community updates. The migration has preserved all 307 historical posts, and old links automatically redirect to the new URLs. If you spot broken links, missing images, or formatting issues from the migration, please file an issue on the repository. PRs to fix such issues are also welcome.
The RSS feed has been updated, but existing feed readers should pick up the new feed automatically. If yours doesn’t, simply point it to blog.python.org/rss.xml. The transition should be seamless for most users.
Links and Resources
- New site: blog.python.org
- Repository: github.com/python/python-insider-blog
- RSS feed: blog.python.org/rss.xml
Conclusion
The move of the Python Insider Blog from Blogger to a Git-based workflow is a significant step forward. It lowers the barrier for community contributions, modernizes the technical stack, and ensures the blog remains a reliable source of official Python news. Whether you’re a long-time reader or a prospective author, the new setup is designed to serve you better. We look forward to seeing your pull requests and ideas for future posts.