Python Insider Blog Relocated to GitHub: New Features and How to Contribute

We have some exciting updates about the official Python blog. The Python Insider blog has moved to a new home at blog.python.org, powered by a Git repository. This change makes it easier for community members to contribute and ensures a more streamlined workflow. In this Q&A, we’ll answer common questions about the migration, how to write for the blog, and what’s under the hood.

Why did the Python Insider blog move from Blogger to a Git-based platform?

The primary motivation was to lower the barrier for contributors. Previously, writing for the blog required a Google account and familiarity with Blogger’s editor, which limited who could participate. The new setup uses plain Markdown files stored in a Git repository. Anyone who can open a pull request can now propose a blog post. This change aligns with the open-source spirit of Python and encourages broader community involvement.

Where is the blog now, and what happened to the old posts?

The blog now lives at blog.python.org. All 307 posts from the original Blogger era were successfully migrated to the new site. Old URLs automatically redirect to their new counterparts, so existing bookmarks and links should still work. The RSS feed has also been updated; you can find it at blog.python.org/rss.xml. Most RSS readers will detect the change automatically, but if you encounter issues, you can manually update your subscription to the new feed URL.

How can I submit a blog post to Python Insider now?

Contributing is straightforward. Begin by forking the repository at github.com/python/python-insider-blog. Inside the content/posts/ directory, create a new folder using your post’s slug (e.g., content/posts/my-new-post/). Add an index.md file that includes your content, with YAML frontmatter for the title, date, authors, and tags. If you need images, place them in the same folder. Once ready, open a pull request against the main repository. The README on GitHub provides further details on frontmatter fields and local preview options.

What technology is behind the new blog?

The blog is built with Astro, a modern static site generator, and deployed as purely static HTML. For styling, it uses Tailwind CSS. If you prefer a visual editor over raw Markdown, there is an optional Keystatic CMS available in development mode. The entire build and deployment process runs through GitHub Actions, ensuring that any approved changes are automatically published. This tech stack was chosen for its performance, simplicity, and alignment with the Git-based workflow.

What about the old Python Insider blog URLs and RSS feed?

All old URLs from the Blogger era automatically redirect to the corresponding pages on the new site, so you don’t need to update any links manually. The RSS feed has moved to blog.python.org/rss.xml. Most RSS readers will pick up the new feed seamlessly, but if yours doesn’t, simply replace the old feed URL with the new one. If you encounter any broken links, missing images, or formatting issues from the migration, please file an issue on the GitHub repository. Pull requests are also welcome to fix any problems.

Do I need special tools or accounts to write for the blog?

No special tooling is required. All you need is a text editor and a GitHub account to open a pull request. Posts are written in plain Markdown, with YAML frontmatter for metadata. Even images are simple: just drop them in the same directory as your post’s index.md file. The goal is to make it as easy as possible for anyone in the Python community to contribute. If you want to preview your post locally before submitting, the repository’s README includes instructions for setting up a development environment.