Python Insider Blog: A New Home on GitHub

Welcome to the new era of the Python Insider Blog! We've moved to a new home at blog.python.org, powered by a Git repository. This change makes it easier for the community to contribute and keeps the blog modern and maintainable. Below we answer the most common questions about this transition.

Where has the Python Insider Blog moved to, and how does the new setup work?

The blog now lives at https://blog.python.org. All 307 posts from the old Blogger platform have been migrated and old URLs automatically redirect to the new ones. The site is backed by a public Git repository. Each post is stored as a Markdown file under content/posts/{slug}/index.md with YAML frontmatter for metadata. Images are placed alongside the post in the same directory. This means no special tools are required beyond a text editor. The new RSS feed URL is https://blog.python.org/rss.xml. Most RSS readers will pick up the new feed automatically, but if yours doesn't, simply update it with that address.

Why did the Python blog move away from Blogger?

Blogger served us well for many years, but it had a limitation: contributing to the blog required a Google account and using Blogger's editor. That created an unnecessary barrier. The new Git-based workflow lowers the bar significantly. Anyone who can fork a repository, create a Markdown file, and open a pull request can now submit a post. This aligns with the open-source ethos of the Python community. By removing the need for special accounts or proprietary editors, we encourage more contributors and make the process transparent. The editorial team can review and merge contributions just like code changes.

How can I contribute a post to the Python Insider Blog?

Contributing is straightforward:

1. Fork the repository at github.com/python/python-insider-blog.
2. Create a new directory under content/posts/ named with your post slug (e.g., my-python-post).
3. Add an index.md file inside that directory with your content, including YAML frontmatter for title, date, authors, and tags.
4. Optionally upload images to the same directory.
5. Open a pull request with your changes.

The repo's README provides detailed instructions on frontmatter fields and how to preview your post locally before submitting. Whether you're writing about a Python release, a core sprint, governance updates, or anything relevant to the official Python blog, we welcome your input.

What technology stack powers the new blog?

The site is built with Astro, a modern static site generator, and deployed as fully static HTML. For those who prefer a visual editor over raw Markdown, a Keystatic CMS is available in development mode—it's entirely optional. The styling is handled by Tailwind CSS, providing a clean, responsive design. The entire build and deployment process runs through GitHub Actions, triggered automatically on pushes to the main branch. This setup ensures fast load times, easy maintenance, and a clear separation of content from code.

What should I do if I find issues from the migration?

During the migration from Blogger, we took care to preserve all content, but some issues might have slipped through. If you spot broken links, missing images, or formatting glitches, please file an issue on the repository. We also welcome pull requests to fix any problems you find—just like contributing a post, you can submit a PR with the correction. The community's help in refining the migrated content is greatly appreciated.

Will my RSS reader still work?

Most RSS readers should automatically detect the new feed location using the permanent redirect from the old URLs. However, if your reader does not update automatically, simply change the feed URL to https://blog.python.org/rss.xml. After that, you'll continue receiving updates as before. The feed includes all future blog posts, so you won't miss any announcements about Python releases, sprints, or community news.

How many posts were migrated, and are old links still valid?

All 307 posts from the Blogger era have been migrated to the new site. Every old URL now redirects automatically to its new corresponding post. This means any bookmarks, shared links, or embedded references will still work—no need to update them. If you encounter a broken redirect, please let us know via the issues tracker. The goal was to make the transition seamless for readers while laying a foundation for easier future contributions.