The Python Insider blog has a new home! We're excited to announce that the official Python blog has moved from Blogger to a modern, Git-based platform at blog.python.org. All 307 posts from the Blogger era have been seamlessly migrated, and old URLs automatically redirect to the new ones. Your RSS readers should pick up the new feed without any action on your part, but if something looks off, the new feed URL is https://blog.python.org/rss.xml. This migration isn't just a cosmetic change—it's a fundamental shift in how the blog is managed, making it easier for the Python community to contribute. Below are five things you need to know about this exciting update.
1. The Blog Has Moved to blog.python.org
The most significant change is the new domain: blog.python.org. Previously hosted on Blogger with a blogspot.com address, the official Python Insider blog now lives on its own dedicated subdomain. All 307 historical posts have been migrated without loss, and incoming links to old URLs are automatically forwarded to the correct new location. This ensures that bookmarks, search results, and internal references continue to work. The RSS feed also has a new permanent address: https://blog.python.org/rss.xml. Your RSS reader should update automatically, but if it doesn't, simply point it to this new URL. The migration was carefully tested to preserve content integrity, so you can browse the blog's history as before—just with a cleaner, more modern setup.
2. Why the Shift from Blogger to Git
Blogger served the Python community well for many years, but it had limitations. Contributing to the blog required a Google account and familiarity with Blogger's editor—a barrier that discouraged potential authors. The new system is built around a Git repository hosted on GitHub. Posts are now simple Markdown files stored under content/posts/{slug}/index.md with YAML frontmatter for metadata like title, date, authors, and tags. Images are placed in the same directory as the post. No special tooling is needed beyond a text editor; anyone comfortable with Git and Markdown can write a post. This lowers the contribution bar significantly, inviting more community members to share updates about Python releases, sprints, governance, and more. The shift also introduces version control, collaboration via pull requests, and easy previewing before publication.
3. How to Contribute a Post (Step-by-Step)
Want to write for the official Python blog? The process is now simpler than ever. Here's the short version:
- Fork the repository at github.com/python/python-insider-blog.
- Create a new directory under
content/posts/with a slug for your post (e.g.,content/posts/my-post-title/). - Add an
index.mdfile inside that directory with your content. You can also upload images to the same directory. - Open a pull request to the main repository.
The repository README contains detailed instructions on frontmatter fields and local development, including how to preview your post before submission. You don't need to be a web developer—just basic Markdown knowledge and a GitHub account. This open contribution model encourages more voices from the Python community to be heard, covering topics like releases, core development sprints, governance updates, and community events.
4. The Technical Stack Behind the New Blog
Under the hood, the new blog is built with Astro, a modern static site generator that produces fully static HTML. This ensures fast load times and reliable hosting. Deployments are handled automatically through GitHub Actions after each merge to the main branch. For styling, the site uses Tailwind CSS, offering a clean, responsive design. Additionally, a Keystatic CMS is available in development mode for those who prefer a visual editor over raw Markdown. However, the CMS is entirely optional—you can work directly with Markdown files if you prefer. The combination of Astro, Tailwind, and GitHub Actions means the blog is easy to maintain, scalable, and community-driven. All source code is open in the repository, so anyone can inspect or suggest improvements to the build process.
5. What to Do If You Spot Issues
While the migration aimed for perfection, a few glitches may have slipped through. If you encounter broken links, missing images, formatting errors, or any other issues, the team encourages you to file an issue on the GitHub repository at github.com/python/python-insider-blog/issues. Pull requests with fixes are also welcome—the project is completely open source. This collaborative approach ensures that the blog remains accurate and functional for all readers. By reporting problems or contributing fixes, you help maintain the quality of the official Python blog. Whether it's a typo in a post or a missing redirect from the old site, your input is valuable. The community-driven nature of this migration means that everyone can play a part in its ongoing success.
In summary, the Python Insider blog has evolved into a more flexible, inclusive platform. With a new home at blog.python.org, Git-based contributions, and a modern static site generator, it's never been easier to write for or engage with the official Python blog. Old URLs redirect, RSS feeds update automatically, and the community is invited to contribute both content and bug fixes. Check out the new site, explore the repository, and consider sharing your own Python insights. Welcome to the new era of Python Insider!