How to Access and Contribute to the New Python Insider Blog

Introduction

The official Python Insider Blog has moved to a new home! After years on Blogger, the blog now lives at https://blog.python.org, powered by a Git repository. All 307 posts from the old Blogger era have been migrated, and old URLs automatically redirect to the new ones. This guide walks you through everything you need to know—from simply reading the blog to writing and submitting your own posts.

What You Need

• A modern web browser
• A GitHub account (for contributing)
• Git installed on your computer (or you can use GitHub’s web interface)
• A text editor (e.g., VS Code, Sublime Text, or even Notepad)
• Optional: An RSS reader (e.g., Feedly) to follow the blog

Step 1: Access the New Blog

Simply visit https://blog.python.org. All old Blogger URLs automatically redirect, so any bookmarks you have will still work. If you use an RSS reader, the new feed URL is https://blog.python.org/rss.xml. Most readers should update automatically, but if you encounter issues, manually replace your old feed with this new one.

Step 2: Understand the New Publication System

The blog now runs on Astro and is deployed as static HTML. Posts are written in Markdown with YAML frontmatter. Each post lives in its own directory under content/posts/{slug}/index.md. For example, a post about Python 3.13 might be at content/posts/python-3-13-released/index.md. The frontmatter includes fields like title, date, authors, and tags. Images are placed in the same directory as the post. No special software is required—just a text editor and a GitHub account.

Step 3: Fork the Repository

Go to the official blog repository at https://github.com/python/python-insider-blog. Click the Fork button (top right) to create your own copy under your GitHub account. This gives you a personal workspace where you can make changes without affecting the main blog.

Step 4: Create Your Post Directory and Files

Inside your forked repository, navigate to content/posts/. Create a new directory named with your post’s slug (a short URL-friendly identifier, e.g., python-version-3-14-preview). Inside that directory, create a file called index.md. If you have images, place them in the same directory.

Step 4a: Add YAML Frontmatter (Optional but Recommended)

At the top of your index.md, include YAML frontmatter surrounded by ---. At minimum, include:

---
title: "Your Post Title"
date: 2025-04-01
authors: ["Your Name"]
tags: ["python", "release"]
---

Check the repository’s README.md for a full list of supported fields, such as description or thumbnail.

Step 5: Write Your Post in Markdown

Below the frontmatter, write your post using standard Markdown syntax. Use headings, lists, code blocks, and other formatting as needed. For example:

## Summary

We're thrilled to announce Python 3.14! This release includes several new features…

## New Features

- Pattern matching improvements
- Faster dict comprehensions
…

Save the file. You can also use the Keystatic CMS (available in dev mode) if you prefer a visual editor—but Markdown is all you need.

Step 6: Add Images (If Any)

Place your images in the same directory as your index.md file. In your Markdown, reference them with a relative path, e.g., ![](diagram.png). Make sure filenames are clear and avoid spaces. Images will automatically be served alongside the post.

Step 7: Preview Your Post Locally (Optional)

If you have Git and Node.js installed, you can run the blog locally to preview your changes. Clone your forked repository, install dependencies (npm install), and run npm run dev. The site will be available at http://localhost:4321. For a visual editing experience, start Keystatic with npm run dev:keystatic. However, previewing is not required—you can rely on the GitHub PR review process.

Step 8: Open a Pull Request

Once your post is ready, commit and push your changes to your forked repository. Then go to the original python/python-insider-blog repository and click New Pull Request. Select your fork and branch. Add a descriptive title and comment explaining what your post covers. The blog maintainers will review your contribution, provide feedback, and merge it.

Step 9: Report Issues

If you notice broken links, missing images, or formatting problems from the migration, open an issue on the repository. The maintainers appreciate bug reports and will fix them quickly. Pull requests for fixes are also welcome.

Tips & Best Practices

• Keep slugs short and descriptive – e.g., python-3-13-released rather than python-3-is-now-released.
• Double-check YAML frontmatter – a missing colon can break the build. Use a YAML validator if unsure.
• Follow the existing style – read a few recent posts to get a feel for tone and formatting.
• Use relative image paths – avoid absolute URLs unless referring to external images.
• Preview your post – even if you skip local preview, read your Markdown carefully; typos happen.
• Respect the community guidelines – blog posts should be about Python releases, core sprints, governance updates, or official announcements.
• Don’t worry about perfection – the reviewing process will catch any issues. Your contribution is valuable!

Now you’re all set to enjoy the new Python Insider Blog and even help shape it. Happy reading (and writing)!