8 Key Changes You Need to Know About the Python Insider Blog Migration

The Python Insider blog has undergone a major transformation. After years on Blogger, it now lives at blog.python.org, powered by a Git repository. This move isn’t just a new address—it’s a complete overhaul of how content is created, managed, and contributed. Whether you’re a regular reader, a contributor, or just curious, here are the eight most important things you need to know about this exciting shift.

1. A Fresh Home for Python Insider

The entire blog has been relocated to blog.python.org. All 307 posts from the Blogger era have been migrated to this new site. No need to update your browser bookmarks—old URLs automatically redirect to the new ones. Your RSS feed also moves: if you use a reader, it should pick up the new feed without any manual intervention. But just in case, the new feed URL is https://blog.python.org/rss.xml.

8 Key Changes You Need to Know About the Python Insider Blog Migration

2. Why They Left Blogger Behind

Blogger worked well for a long time, but it had a significant barrier: contributing required a Google account and familiarity with Blogger’s editor. That’s a higher bar than the Python community needs. The new setup is much simpler—now, posts are just Markdown files in a Git repository. If you can open a pull request, you can write a post. This change aligns with the open-source ethos of Python itself, making it easier for anyone to contribute.

3. The New Publishing Workflow

Every blog post lives in content/posts/{slug}/index.md with YAML frontmatter for title, date, authors, and tags. Images go into the same directory as the post. No special tooling is required beyond a text editor. This structure is clean, portable, and developer-friendly. You can even preview your post locally before submitting—the repository’s README has all the details on frontmatter fields and local development.

4. How You Can Contribute Now

Want to write about a Python release, core sprint, governance update, or anything else that belongs on the official Python blog? The process is straightforward:

Fork the repository at github.com/python/python-insider-blog.
Create a new directory under content/posts/ with your post’s slug.
Add an index.md file with your content (you can also upload images to the same folder).
Open a pull request.

That’s all it takes to get your contribution reviewed and published.

5. Under the Hood: Tech Stack

The site is built with Astro and deployed as fully static HTML. During development, a Keystatic CMS is available if you prefer a visual editor over raw Markdown—but it’s entirely optional. Tailwind handles the styling. The entire build and deployment pipeline runs through GitHub Actions, ensuring fast, reliable updates. This modern stack makes the blog fast and easy to maintain.

6. Seamless Migration with Automatic Redirects

One of the best parts of this move is that all 307 posts from the old Blogger site have been migrated without breaking existing links. Old URLs automatically redirect to the new ones, so your deep links to specific articles still work. No broken bookmarks, no frustration—just a smooth transition.

7. Help Improve the Blog

If you spot broken links, missing images, or formatting issues that slipped through the migration, you can help. Simply file an issue on the repository. Pull requests with fixes are also welcome. This is a community-driven blog, and your contributions—whether as a writer or a bug hunter—are valued.

8. Quick Links to Remember

Here are the essential URLs you’ll want to bookmark:

New site: blog.python.org
Repository: github.com/python/python-insider-blog
RSS feed: blog.python.org/rss.xml
Issue tracker: github.com/python/python-insider-blog/issues

These links will keep you connected to the latest Python news and give you the tools to join the conversation.

The Python Insider blog’s migration marks a new chapter for the community’s official voice. By lowering the barrier to contribution, adopting a modern tech stack, and ensuring a seamless reader experience, this move makes the blog more open and sustainable. Whether you’re a long-time reader or a first-time contributor, now is the perfect time to get involved—check out the new site, update your RSS feed, and maybe even write your first post.