The Python Insider Blog Moves to GitHub: A Contributor's How-To Guide

Introduction

The official Python Insider Blog has relocated from Blogger to a new home at blog.python.org. This move isn't just a URL change—it's a complete overhaul of how the blog is managed and how you can contribute. All 307 historical posts have been migrated, and old Blogger URLs automatically redirect to the new ones. If you're an RSS subscriber, your feed will update seamlessly to the new feed at https://blog.python.org/rss.xml. The biggest improvement? The blog is now powered by a Git repository using plain Markdown files. That means anyone with a GitHub account and a text editor can propose new posts via pull requests. This guide will walk you through everything you need to know—from updating your reader to writing your first contribution.

What You Need

• A GitHub account — required for forking the repository and submitting pull requests.
• A text editor — any editor that handles Markdown (e.g., VS Code, Atom, Notepad++, or even a simple text editor).
• Basic familiarity with Markdown — though not mandatory, knowing how to format headers, lists, and links will help.
• Optionally, Git installed locally for previewing the site (but you can also use GitHub's web interface).
• An idea for a post — something related to Python releases, core sprints, governance updates, or other official topics.

Step-by-Step Guide

Step 1: Understand the New Platform

The new site is built with Astro and deployed as fully static HTML. Styling uses Tailwind CSS, and the entire build and deployment process runs through GitHub Actions. Posts live as Markdown files inside the repository at content/posts/{slug}/index.md. Each post has YAML frontmatter that includes the title, date, author(s), and tags. Images are stored in the same directory as the post. There's also an optional Keystatic CMS available in development mode if you prefer a visual editor over raw Markdown, but it's entirely optional.

Step 2: Update Your RSS Reader

If you previously subscribed to the Blogger feed, your reader should automatically pick up the new feed at https://blog.python.org/rss.xml. However, if you notice any issues, manually replace the old feed URL with the new one. No other changes are required.

Step 3: Fork the Repository

Go to the official repository at github.com/python/python-insider-blog. Click the Fork button in the top-right corner to create a copy under your GitHub account. This will be your working copy where you'll make changes.

Step 4: Create Your Post Directory

Inside your forked repository, navigate to content/posts/. Create a new directory using a slug that represents your post title (e.g., my-awesome-python-tip). The slug should be URL-friendly with hyphens.

Step 5: Write Your Post in Markdown

Inside that directory, create a file named index.md. The file must start with YAML frontmatter. Here's a minimal example:

---
title: "My Awesome Python Tip"
date: "2025-03-15"
authors:
  - "Your Name"
tags:
  - "python"
  - "tips"
---

Your Markdown content goes here...

Refer to the repository's README for a full list of supported frontmatter fields. After the frontmatter, write the body of your post using standard Markdown. You can include headings, lists, code blocks, and links as needed.

Step 6: Add Images

Place any images in the same directory as index.md. In your Markdown, reference them with relative paths like ![alt text](./image.png). No special tooling is required beyond your text editor.

Step 7: Preview Your Post (Optional)

If you have Astro installed locally, you can run the development server to see how your post will look. The repository's README contains instructions for local preview. Alternatively, you can launch the Keystatic CMS in dev mode for a WYSIWYG experience. If you're not comfortable with command line tools, you can skip this step and submit your pull request directly—the maintainers will review the formatting.

Step 8: Open a Pull Request

Once you've committed your changes to your fork, go to the original repository and click New Pull Request. Ensure your fork's branch contains your new post. Provide a clear title and description explaining what your post covers. The Python team will review your submission, suggest changes if needed, and eventually merge it.

Step 9: Report Issues

If you spot broken links, missing images, or formatting issues from the migration, please file an issue on the repository's issue tracker. Pull requests with fixes are also welcome.

Tips for Success

• Double-check your frontmatter — incorrect YAML syntax can prevent your post from being built. Validate with online tools if needed.
• Keep images small — large files slow down the site. Optimize them before uploading.
• Read the existing posts — get a feel for the tone and style of the Python Insider Blog before writing.
• Use the Keystatic CMS if you prefer a visual editor — but remember that final submissions must be in Markdown.
• Don't forget to update your RSS reader manually if the automatic switch doesn't happen.
• Be patient — the team may take a few days to review your pull request, especially during busy periods.