Python Insider Blog: New Home, New Workflow – Your Questions Answered
Here are answers to common questions about the migration of the Python Insider Blog, covering why the move happened, how the new system works, and what it means for contributors and readers alike.
Why did the Python Insider Blog move from Blogger?
The old Blogger platform served the blog well for years, but it had a significant drawback: contributing required a Google account and familiarity with Blogger’s editor. This created an unnecessary barrier for community members who wanted to submit guest posts or updates. The new setup removes that friction entirely. By switching to a Git-based workflow, the blog now accepts contributions through pull requests on GitHub. Anyone with a GitHub account can propose a post by editing Markdown files. This change lowers the entry point and aligns with how the Python community already collaborates on code and documentation. The move wasn’t about fixing something broken—Blogger worked—but about making the blog more inclusive and easier to maintain.
Where is the blog now, and are old URLs preserved?
The Python Insider Blog now lives at https://blog.python.org, backed by a Git repository. All 307 posts from the Blogger era have been migrated successfully. Old URLs automatically redirect to their new counterparts, so any bookmarks or links you’ve shared will still work. The RSS feed has also moved to https://blog.python.org/rss.xml. Most RSS readers should pick up the new feed automatically, but if you notice anything off, you can manually update your reader with that URL. The migration was designed to be as seamless as possible for readers—you shouldn’t need to take any action unless you’re a direct contributor.
How can I contribute a post to the blog?
Contributing is now straightforward thanks to the GitHub-centric approach. Here’s the process in a nutshell:
- Fork the repository at https://github.com/python/python-insider-blog.
- Create a new directory under
content/posts/using your post’s slug (e.g.,my-post-slug). - Inside that directory, create an
index.mdfile containing your post in Markdown. Optionally, upload images to the same folder. - Submit a pull request to the main repository.
What technology powers the new blog?
The site is built with Astro, a modern static site generator, and deployed as fully static HTML for speed and reliability. If you prefer a visual editor over raw Markdown, there is a Keystatic CMS available in development mode, but it’s entirely optional. For styling, Tailwind CSS is used to keep the design lean and responsive. The entire build and deployment pipeline runs through GitHub Actions, ensuring that every merged pull request automatically updates the live site. This setup not only modernizes the blog but also leverages the same infrastructure the Python community already trusts for code projects.
How are posts organized in the repository?
Each post lives in its own directory under content/posts/{slug}/. The main content file is always index.md, which contains the post body in Markdown and a YAML frontmatter block for metadata like the title, publication date, authors, and tags. Images are placed right next to the index.md file in the same directory—no separate assets folder. This keeps everything self-contained and easy to manage. The frontmatter fields are flexible but include the essentials, and the repo’s README documents all available options. This structure makes contributing predictable: you always know where to put your content and images.
What should I do if I find broken links or missing content?
Despite careful migration, a few glitches might have slipped through. If you spot broken links, missing images, or formatting errors, please file an issue on the repository. The maintainers welcome bug reports and are happy to fix them. Even better, if you’re comfortable with Git, you can submit a pull request directly with the correction. The community-driven ethos extends beyond just writing posts—improving the blog is a team effort. Your help in keeping the archive pristine is greatly appreciated.