Your Guide to the New Python Insider Blog: From Blogger to GitHub

The official Python Insider blog has undergone a major transformation. We’ve packed up all 307 posts from the old Blogger home and moved them to a fresh, modern platform at blog.python.org. The move isn’t just a new address—it’s a complete shift in how the blog works, making it easier than ever for the Python community to contribute. Here’s everything you need to know.

Why Did Python Insider Leave Blogger?

Blogger served us well for years, but it came with unnecessary hurdles. Writing a post required a Google account and using Blogger’s editor—a barrier for many contributors. The new setup eliminates that friction entirely. Now, content is written as simple Markdown files stored in a Git repository. If you know how to open a pull request, you can write a post. No special accounts or tools needed; just a text editor and a GitHub fork. This change lowers the bar for contribution, aligning with Python’s open-source spirit.

How Can I Contribute a Post to the New Blog?

Contributing is straightforward. First, fork the repository at github.com/python/python-insider-blog. Inside your fork, create a new directory under content/posts/ named with your post slug (e.g., my-awesome-update). Add an index.md file—that’s your post content. For images, simply drop them into the same directory. Finally, open a pull request from your fork to the main repository. The repo’s README includes extra details on frontmatter fields (title, date, authors, tags) and how to preview your post locally using Astro’s dev server.

What Happened to All the Old Blogger Posts?

Every single one of the 307 posts from the Blogger era has been migrated to the new platform. We made sure that old URLs automatically redirect to their new locations, so any bookmarks or links you’ve shared will still work. If you encounter a broken link or a missing image, please file an issue on the repository—we welcome pull requests to fix any migration glitches. The content is preserved exactly, but now lives in a more maintainable, version-controlled format.

Do I Need to Update My RSS Reader?

For most readers, no action is required. The old RSS feed should redirect to the new one automatically. However, if your reader seems off, point it to the official new feed URL: https://blog.python.org/rss.xml. That feed is generated from the Git repository, so it’s always up-to-date with the latest posts. We recommend confirming the switch if you rely heavily on RSS for Python updates.

What Technology Powers the New Blog?

The site is built with Astro, a static-site generator that produces fully static HTML—fast and secure. During development, you can use Keystatic CMS if you prefer a visual editor over raw Markdown, but it’s entirely optional. Styling comes from Tailwind CSS, keeping the design clean and responsive. The entire build and deployment pipeline runs through GitHub Actions: whenever a pull request is merged, the site rebuilds automatically and goes live. This setup combines modern developer experience with community accessibility.

What Is the Structure of a Post File?

Each post lives in content/posts/{slug}/index.md. The file starts with YAML frontmatter (between --- markers) containing the title, date, authors, and tags. After the frontmatter, you write the body in standard Markdown. Images are stored in the same directory as the index.md file, so you can reference them with relative paths. No special database or plugin is required—just a text editor and basic Markdown knowledge. This simplicity is a key reason we chose the Git-based workflow.

Where Can I Find More Details or Report Issues?

All the important links are right here: the new blog lives at blog.python.org, the repository is github.com/python/python-insider-blog, and the RSS feed is blog.python.org/rss.xml. If you spot formatting issues, broken links, or missing images from the migration, file an issue on GitHub. And if you’re feeling ambitious, open a pull request to fix it yourself—community contributions are very welcome.