Great news for the Python community! The official Python Insider blog has undergone a major upgrade. It has moved from Blogger to a brand-new home at blog.python.org, now powered by a Git repository. This change makes it easier than ever for community members to contribute, and all 307 previous posts have been seamlessly migrated. Below, we answer your top questions about the move.
Why did the blog move away from Blogger?
Blogger served the Python blog well for years, but it had a significant drawback: anyone wishing to contribute needed a Google account and had to use Blogger's editor. That barrier kept many talented community members from sharing their insights. The new setup eliminates these hurdles entirely by using Markdown files stored in a Git repository. Now, if you can open a pull request, you can write a post. No special accounts or proprietary tools required — just a text editor and a GitHub account.
How are posts organized in the new system?
Every blog post lives in its own directory under content/posts/. The structure is simple: content/posts/{slug}/index.md. Each Markdown file includes YAML frontmatter that defines the title, date, authors, and tags. Images are placed right next to the post in the same folder, so referencing them is straightforward. No complex databases or CMS quirks — just plain files that are easy to manage and version control.
How can I write a post for the Python blog?
Contributing is now a breeze. Here's the short version:
- Fork the repository at github.com/python/python-insider-blog.
- Create a new directory under
content/posts/using your chosen post slug (e.g.,my-awesome-post). - Inside that directory, add an
index.mdfile with your Markdown content and (optionally) upload your images. - Open a pull request against the main branch.
The repository's README contains full details on frontmatter fields and how to preview your post locally. It's open to anyone who wants to write about Python releases, core sprints, governance updates, or anything relevant to the official Python blog.
What technology powers the new blog?
The site is built with Astro, a modern static site generator, and deployed as fully static HTML for speed and reliability. For contributors who prefer a visual editor over raw Markdown, there's an optional Keystatic CMS available in development mode. Tailwind CSS handles all the styling, making the blog responsive and clean. The entire build and deployment process runs automatically through GitHub Actions, so updates go live without manual intervention.
What happened to old posts and RSS feeds?
Every single one of the 307 posts from the Blogger era has been migrated to the new site. Old URLs automatically redirect to their new locations, so existing bookmarks and links still work. Your RSS reader should pick up the new feed at blog.python.org/rss.xml without any action on your part. If your reader doesn't update automatically, simply point it to that URL.
Where can I report problems or suggest improvements?
If you come across broken links, missing images, formatting glitches, or any other issues from the migration, the team welcomes your help. Simply file an issue on the repository at github.com/python/python-insider-blog/issues. Pull requests with fixes are also encouraged. Every contribution helps make the official Python blog better for the whole community.