The official Python Insider Blog has undergone a major upgrade. We’ve moved the blog to a new home that makes contributing easier than ever before. If you’ve ever wanted to write about Python releases, core sprints, governance updates, or anything else that belongs on the official Python blog, the new setup is built for you. Below, we answer the most common questions about the move, the new contribution workflow, and what’s under the hood. Whether you’re a regular reader or a prospective author, you’ll find everything you need to get started.
What’s the biggest change for the Python Insider Blog?
The most significant change is that the Python Insider Blog now lives at https://blog.python.org, backed by a Git repository instead of Blogger. All 307 posts from the Blogger era have been migrated, and old URLs automatically redirect to the new ones. Previously, contributing required a Google account and the Blogger editor. Now, the site is built entirely from Markdown files stored in a public Git repository. This shift makes the blog more open and accessible: if you can open a pull request, you can submit a post. The repository is hosted on GitHub at https://github.com/python/python-insider-blog, and the whole site is built with Astro and deployed as static HTML via GitHub Actions.
Where can I find the new blog and does the old URL still work?
The new official home of the Python Insider Blog is https://blog.python.org. All old Blogger URLs automatically redirect to the new ones, so any bookmarks or links you have should continue to work. The blog posts live in a Git repository under content/posts/{slug}/index.md with YAML frontmatter for the title, date, authors, and tags. Images are stored in the same directory as the post. No special tooling is needed beyond a simple text editor. If you’re a long-time reader, you can simply update your bookmarks and continue enjoying the same content in a faster, more modern environment.
How has the contribution process changed?
Contributing to the Python Insider Blog is now easier and more transparent. Instead of needing a Google account and using Blogger’s editor, you only need a GitHub account and a basic understanding of Markdown. To submit a post, you fork the repository at https://github.com/python/python-insider-blog, create a new directory under content/posts/ with your desired URL slug, add an index.md file with your content (and optionally upload images), and open a pull request. The repository’s README provides detailed instructions on frontmatter fields and local development if you want to preview your post before submitting. This open pull-request workflow lowers the barrier to entry and invites more community contributions.
What’s the technical stack behind the new blog?
The new Python Insider Blog is built with Astro, a modern static site generator, and deployed as fully static HTML. For styling, it uses Tailwind CSS. There is also an optional Keystatic CMS available in development mode for those who prefer a visual editor over raw Markdown, but it’s entirely optional and not required for contributing. The entire build and deployment process runs through GitHub Actions, ensuring that every pull request merged automatically triggers a rebuild of the site. This stack provides a fast, secure, and maintainable foundation for the blog, and because everything is static, it loads quickly for readers worldwide.
How can I write a guest post for the official Python blog?
Writing a guest post for the Python Insider Blog is straightforward. First, identify a topic that fits the blog – for example, a Python release announcement, a core sprint summary, a governance update, or any other Python-related news. Then, follow these steps:
- Fork the repository at https://github.com/python/python-insider-blog.
- Create a new directory under
content/posts/with your chosen URL slug (e.g.,my-post-slug). - Inside that directory, create an
index.mdfile containing your post in Markdown, with YAML frontmatter specifying the title, date, authors, and tags. - (Optional) Place any images you need in the same directory.
- Open a pull request against the main repository.
Once your pull request is reviewed and merged, the blog will be automatically rebuilt and deployed. The README in the repository offers more detailed guidance on frontmatter fields and local preview options.
I use an RSS reader – do I need to update my feed?
Most RSS readers should automatically pick up the new feed without any action on your part. However, if you notice that your reader is not updating correctly, the new RSS feed URL is https://blog.python.org/rss.xml. You can manually add or update this URL in your reader. The old Blogger feed is no longer active, so switching to the new feed ensures you won’t miss any future posts. The migration preserved all 307 past posts, so your reader will also catch up with the full history once it syncs with the new feed.
What should I do if I find any issues after the migration?
If you encounter broken links, missing images, formatting issues, or any other problems resulting from the migration, please help the community by reporting them. You can file an issue directly on the repository at https://github.com/python/python-insider-blog. Pull requests that fix these issues are also welcome. The team appreciates any help improving the blog, and because the site is now managed through a public Git repository, corrections can be made quickly and transparently. Your contributions help make the Python Insider Blog better for everyone.