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

The Python Insider Blog has officially moved to a new home, and we're here to answer your most pressing questions. Our migration from Blogger to a Git-backed site at blog.python.org brings better performance, simpler contributions, and a more modern workflow. Below, we cover the key changes, how you can get involved, and what to expect from the new setup.

What happened to the Python Insider Blog?

The official Python blog has relocated from Blogger to a new, self-hosted site at blog.python.org. This move includes all 307 historical posts from the Blogger era, which have been fully migrated. Old URLs automatically redirect to the new ones, so you won't encounter broken bookmarks. The new site is powered by a Git repository, meaning content is now written in Markdown files rather than through Blogger's editor. This change paves the way for a more open and accessible contribution process.

Why did the blog leave Blogger?

Blogger served the Python community well for many years, but it had a significant limitation: to contribute a post, you needed a Google account and familiarity with Blogger's proprietary editor. That created an unnecessary barrier for community members who wanted to share updates on Python releases, core sprints, governance changes, or other official news. The new approach uses plain Markdown files stored in a Git repository. Now anyone comfortable with a text editor and Git can propose a post by opening a pull request. This lowers the barrier to entry and encourages more contributions from the global Python community.

How can I contribute a post to the new blog?

Contributing is straightforward. First, fork the repository at github.com/python/python-insider-blog. Inside the content/posts/ directory, create a new folder named with your post slug (e.g., my-post-title). Within that folder, add an index.md file containing your content in Markdown, with YAML frontmatter that includes title, date, authors, and tags. Images can be placed right alongside the post file. Once everything is ready, open a pull request. The repository's README provides full details on frontmatter fields and local development (including a preview option). That's all there is to it—no special tools required beyond a text editor and a Git client.

What technology powers the new blog?

The site is built using Astro, a modern static site generator. All pages are pre-rendered as static HTML for fast load times. For those who prefer a visual editor over raw Markdown, a Keystatic CMS is available in development mode—though it's entirely optional. Styling is handled by Tailwind CSS, ensuring a clean and responsive design. The entire build and deployment process runs automatically via GitHub Actions, so any merged pull request triggers an update to the live site within minutes. This stack was chosen for its simplicity, performance, and developer-friendly workflow.

Will my RSS reader still work? What about old links?

Yes, your RSS feed should update automatically. The new feed URL is blog.python.org/rss.xml. In most cases, your reader will pick up the new feed without any manual intervention. However, if you notice any issues—like missing posts or broken entries—you can manually update your reader to the new feed URL. All old URLs from the Blogger version automatically redirect to the corresponding posts on the new site, so bookmarks and external links remain valid. No action is required to preserve access to previous content.

What should I do if I find a broken link or formatting issue?

Despite careful migration, a few glitches might have slipped through. If you encounter broken links, missing images, or formatting problems, please help us improve by filing an issue on the GitHub repository at github.com/python/python-insider-blog/issues. Pull requests that fix these issues are also very welcome. The community-driven nature of the new setup means that anyone can contribute directly to maintaining the blog's quality. Simply click the "New issue" button and describe the problem—include the affected URL if possible—and we'll address it promptly.

Can I also help with the blog's development or design?

Absolutely. The entire site—including its codebase, styling, and configuration—lives in the public repository. If you have ideas for improving the Astro setup, Tailwind themes, or build pipeline, feel free to open an issue to discuss your suggestion or submit a pull request with your changes. We welcome contributions that enhance the blog's usability, performance, or appearance. The repository's README includes instructions for local development, so you can test modifications before submitting. Whether you're fixing a small CSS glitch or proposing a new feature, your input is valued.