We're thrilled to share that the Python Insider blog has officially moved to a new home. The blog now lives at https://blog.python.org, powered by a Git repository for easier collaboration. All 307 posts from the old Blogger era have been migrated, and existing URLs automatically redirect to the new location. Your RSS feed should update seamlessly, but if needed, the new feed URL is https://blog.python.org/rss.xml. Below we answer common questions about the move and what it means for readers and contributors.
Where did the Python Insider blog move to?
The blog has moved from the old Blogger platform to a brand-new site at https://blog.python.org. This new site is built with Astro and deployed as fully static HTML, backed by a Git repository hosted on GitHub. Every single post from the previous era—all 307 of them—has been transferred, and any existing URLs will automatically redirect to their new counterparts. If you were subscribed to the old RSS feed, your reader should pick up the new feed without any action. However, the direct feed URL is now https://blog.python.org/rss.xml in case you need to update it manually.
Why did the team leave Blogger?
Blogger served the Python community well for many years, but contributing to the blog required a Google account and familiarity with Blogger's editor. That created an unnecessary barrier for potential authors. The new setup lowers the entry threshold: anyone who can open a pull request on GitHub can now write a post. Instead of a proprietary editor, you simply create Markdown files in a Git repository. This change makes the blog more accessible to the broader Python community, encouraging contributions from people who might not have a Google account or who prefer working with standard development tools.
How are posts structured in the new system?
Each blog post lives in its own directory under content/posts/, following the pattern {slug}/index.md. The Markdown file includes YAML frontmatter that defines the title, date, authors, and tags. Images are placed right next to the post file in the same directory, so no external image hosting is required. You can write a post using any text editor—no special tooling is needed. If you prefer a visual editor over raw Markdown, the site includes a Keystatic CMS that can be activated in development mode, but using it is entirely optional. This structure keeps everything tidy and makes collaboration straightforward via Git.
How can I contribute a post to the blog?
Contributing is now easier than ever. Here's the short process: First, fork the repository at https://github.com/python/python-insider-blog. Next, create a new directory under content/posts/ with a slug for your post. Inside that directory, add an index.md file containing your content and optionally upload any images. Then open a pull request against the main repository. The repo's README provides additional details about frontmatter fields and local development, including how to preview your post before submitting. This workflow mirrors how many open source projects operate, making it natural for developers familiar with Git and GitHub.
What technology powers the new site?
The new blog is built with Astro, a modern static site generator that produces fully static HTML. For styling, the team uses Tailwind CSS. The entire build and deployment process is automated through GitHub Actions—whenever changes are merged to the main branch, the site rebuilds and deploys automatically. During local development, you can optionally use Keystatic CMS for a visual editing experience, but all content remains as Markdown files in the repository. This tech stack ensures fast page loads, easy maintenance, and a low barrier for anyone wanting to contribute or fix issues.
What happens to old links and RSS feeds?
All old URLs from the Blogger era now redirect automatically to the corresponding posts on the new site. You don't need to update bookmarks manually. The RSS feed has changed to https://blog.python.org/rss.xml. Most RSS readers will detect the new feed automatically because the old feed URL redirects, but if you experience any issues, you can update your reader to use the new link directly. If you spot any broken links, missing images, or formatting issues that resulted from the migration, please file an issue on the GitHub repository. Pull requests to fix these issues are also welcome.
Where can I report problems or suggest improvements?
If you encounter any problems—such as broken links, missing images, or formatting glitches—head over to the repository at https://github.com/python/python-insider-blog and open an issue. The team encourages community participation, so feel free to submit a pull request if you'd like to fix an issue yourself. Whether it's a typo, an outdated reference, or a suggestion for a new feature, contributions are welcome. The blog's new Git-based workflow makes it easy for anyone to help keep the official Python blog accurate and up-to-date.