Welcome to the new era of the Python Insider blog! We've packed up our digital bags and moved to a shiny new home. Below, you'll find answers to the most common questions about this transition—from why we moved to how you can start contributing. Happy reading!
Why did the Python Insider blog move from Blogger?
The old Blogger platform served us well for years, but it had a significant barrier to entry: contributors needed a Google account and had to use Blogger's own editor. This made it unnecessarily hard for community members to pitch in. The new setup is built around a Git repository hosted on GitHub. Now, writing a post is as simple as creating a Markdown file and opening a pull request. No special accounts, no heavy tools—just commit, push, and review. This shift lowers the bar to contribution and aligns with the Python community's love for open-source workflows. If you can fork a repo and write in Markdown, you can help shape the official voice of Python.
What exactly changed with the blog's structure and URLs?
The blog now lives at https://blog.python.org instead of its old Blogger address. All 307 posts from the Blogger era have been safely migrated and redirected, so any old links will automatically take visitors to the correct new pages. Your RSS feed remains intact—just update to https://blog.python.org/rss.xml if your reader needs a manual tweak. The content is stored as plain Markdown files inside a Git repository. Each post is a directory under content/posts/{slug}/ with an index.md file containing YAML frontmatter (title, date, authors, tags) and the body. Images sit in the same directory, making them easy to manage.
How can I contribute a post to the Python Insider blog?
Contributing is now easier than ever. Head over to the repository at https://github.com/python/python-insider-blog and fork it. Create a new directory under content/posts/ named after your post's slug. Inside, add an index.md file with your post content—don't forget the YAML frontmatter for metadata. If you have images, drop them in the same directory. Then open a pull request against the main repository. That's it! For detailed instructions on frontmatter fields and local development (including how to preview your post before submitting), check the README in the repository. The process is designed to be as lightweight as possible.
What technology powers the new blog?
The site is built with Astro, a modern static site generator. It produces fully static HTML files, which means fast loading and simple hosting. Optionally, while developing locally, you can use Keystatic CMS if you prefer a visual editor over raw Markdown—but it's entirely optional and not required. The styling is handled by Tailwind CSS, giving the blog a clean, responsive design out of the box. To streamline operations, the entire build and deployment pipeline runs through GitHub Actions. So when you open a pull request, automated checks and previews can happen before anything goes live. This modern stack keeps maintenance low and flexibility high.
Where can I report issues like broken links or formatting problems?
We did our best to migrate all 307 posts smoothly, but a few hiccups are always possible. If you spot a broken link, a missing image, or any formatting glitch, please file an issue on the repository at https://github.com/python/python-insider-blog. We also welcome pull requests to fix such issues—so if you're comfortable, feel free to submit a correction directly. The community's help is invaluable in polishing the blog. And if you have ideas for new content, writing a post is only a PR away. Check out the new site, grab your favorite editor, and join us in shaping the official Python blog.