Your Guide to Publishing on the Python Insider Blog (New Home)

Introduction

The Python Insider Blog has relocated to blog.python.org, and with the move comes a streamlined contribution process. No longer do you need a Google account or the Blogger editor—now anyone with GitHub skills can submit a post. All 307 previous entries have been migrated, old URLs redirect seamlessly, and your RSS feed still works (new feed URL). This guide walks you through the exact steps to write and publish your own article on the official Python blog.

What You Need

Before you start, make sure you have these prerequisites ready:

• A GitHub account (free tier works).
• Basic understanding of Markdown (headings, lists, links, etc.).
• A text editor – any plain-text editor will do (like VS Code, Notepad++, or even a simple text editor).
• Familiarity with pull requests on GitHub (optional but helpful).
• Optional: Git installed locally for previewing your post.

Step-by-Step Guide

Step 1: Fork the Repository

Go to the official repository: python/python-insider-blog. Click the Fork button at the top-right to create your own copy under your GitHub account. This is where you'll make all your changes.

Step 2: Create Your Post Directory

Inside the content/posts/ directory, create a new folder named with a short, descriptive slug for your post (e.g., my-article-slug). This folder will hold your Markdown file and any images. The slug will become part of the final URL, so choose something clear and without spaces.

Step 3: Write Your Blog Post in Markdown

Inside your slug folder, create a file called index.md. Open it in your text editor and start with the required YAML frontmatter at the very top. The frontmatter fields are:

• title: Your post title (use quotes if it contains special characters).
• date: The publication date in YYYY-MM-DD format.
• authors: A list of author GitHub usernames (e.g., ['ghuser1', 'ghuser2']).
• tags: A list of tags, like ['release', 'news'].

After the frontmatter, write your content in Markdown. Use headings, paragraphs, lists, code blocks, and links just like any Markdown document. Refer to the README on the repo for a complete list of optional fields and formatting tips.

Step 4: Add Images (Optional)

If your post includes images, place them in the same directory as your index.md file. Use relative paths in your Markdown, such as ![alt text](image.png). The build system will handle the rest. No special tooling required.

Step 5: Open a Pull Request

Once your markdown file is ready, commit your changes to your forked repository (or work directly on the GitHub web interface if you prefer). Navigate back to the original repository—it will show a banner offering to compare & pull request. Click that button, write a brief description of your post (e.g., 'New article about Python 3.13'), and submit the PR. The blog maintainers will review and merge it.

Optional: Preview Locally

If you want to see how your post will look before submitting, you can run the site locally. The blog is built with Astro and deployed as static HTML. Clone your fork, install dependencies (npm install), then run npm run dev to start a local server. There's also a Keystatic CMS available in development mode for a visual editor—check the local development section in the README for instructions.

Tips for a Successful Contribution

• Keep it relevant: The blog covers Python releases, core sprints, governance updates, and community news. Avoid generic tutorials unless they relate directly to Python’s development.
• Use plain language: Write for a broad audience of Python enthusiasts. Explain acronyms and avoid unnecessary jargon.
• Check your images: Make sure file names match and that images are properly sized (use responsive images if needed—Astro handles optimization).
• Test your links: Verify that any external URLs work and that internal references (like anchor links) are correct.
• Respect the community guidelines: Follow Python’s Code of Conduct in your writing and comments.
• Be patient: The blog team will review your PR. If they suggest changes, they’ll provide feedback—it’s all part of the collaborative process.
• Use the RSS feed: Once your post is live, subscribers using the feed https://blog.python.org/rss.xml will see it automatically. No action needed on your part.
• Report issues: If you spot broken links, missing images, or formatting problems from the migration, file an issue on the repo. Pull requests are welcome too.

Now you have everything you need to contribute to the Python Insider Blog. Happy writing!