Your Guide to the New Python Insider Blog: A Q&A

Welcome to the new home of the Python Insider blog! We've made an exciting transition from Blogger to a modern, open-source platform. This Q&A covers everything you need to know about the move, how to contribute, and what's changed. Dive in to explore the details.

1. Where has the Python Insider blog moved to and what's new about it?

The Python Insider blog has relocated to blog.python.org. Behind the scenes, it's now backed by a public Git repository hosted on GitHub. All 307 historical posts from the Blogger era have been seamlessly migrated, and every old URL now redirects automatically to its new home. The biggest change is that the blog is built from Markdown files stored in a Git repo, making it far easier for community members to propose new content. You can browse the source, submit a pull request, or simply enjoy the familiar RSS feed at blog.python.org/rss.xml.

Your Guide to the New Python Insider Blog: A Q&A

2. Why did the Python team decide to leave Blogger?

Blogger served us well for many years, but it had a high barrier to contribution. Writing a post required a Google account and the use of Blogger's editor—which many found cumbersome. The new setup eliminates all that. Now, anyone with basic Markdown knowledge and a GitHub account can propose a post. There's no special tooling needed beyond a text editor and Git. By moving to a Git-based workflow, we lowered the entry point and made the blog truly community-driven. Additionally, the new platform (Astro, static HTML, Tailwind) is faster and more maintainable, ensuring the blog stays modern for years to come.

3. How can I contribute a post to the new Python Insider blog?

Contributing is simpler than ever! Here's the short version:

Fork the repository at github.com/python/python-insider-blog.
Create a new directory under content/posts/ using your desired post slug (e.g., my-post).
Inside that directory, place an index.md file containing your content in Markdown with YAML frontmatter (title, date, authors, tags).
You can also upload images directly into the same directory—no extra steps needed.
Finally, open a pull request (PR) against the main branch. The repo README explains frontmatter fields and local development for previewing. That's it!

4. What technology stack powers the new blog?

The blog is built on Astro, a modern static site generator, and deployed as fully static HTML for speed and reliability. In development mode, there's an optional Keystatic CMS for those who prefer a visual editor over raw Markdown. Styling is handled by Tailwind CSS. The entire build and deployment pipeline runs through GitHub Actions, ensuring every PR is automatically built before going live. This stack is lightweight, developer-friendly, and ensures the blog is fast and easy to manage. No database, no server-side processing—just static files served directly.

5. Will my existing RSS feed continue to work?

Yes, with no action required on your part. Our old RSS feed URLs have been redirected to the new one, and all subscribers should be automatically updated. However, if your reader doesn't pick up the change, you can manually update the feed URL to blog.python.org/rss.xml. The new feed includes all migrated posts and new ones as they are published. We recommend checking your feed reader after a few days to ensure everything is syncing correctly. If you encounter issues, please let us know by filing an issue on the repository.

6. What happens to old URLs and migrated content?

Every post from the Blogger era—all 307 of them—has been migrated to the new site. Old URLs automatically redirect to the new locations via HTTP 301 redirects, so if you had a bookmark or link, it still works. The content itself is preserved with the same information and facts. While we've done our best to ensure a smooth transition, there may be occasional broken links, missing images, or formatting issues. If you find any, please file an issue on the GitHub repo. Pull requests with fixes are also very welcome!

7. How are posts organized inside the Git repository?

Each post lives in its own directory under content/posts/—specifically content/posts/{slug}/index.md. The slug is the URL-friendly name (e.g., python-insider-blog-moved). The Markdown file includes YAML frontmatter for metadata like title, publication date, author(s), and tags. Images and other assets are placed in the same directory as the post, which keeps everything organized. No special folder structures or external image hosting required—just a text editor and Git. This simplicity makes it easy for anyone to contribute, review, or maintain the blog.