Python Insider now lives at blog.python.org, backed by a Git repository. All 307 posts from the Blogger era have been migrated over, and old URLs redirect to the new ones automatically. Your RSS readers should pick up the new feed without any action on your part, but if something looks off, the new feed URL is blog.python.org/rss.xml.
Blogger worked fine for a long time, but contributing to the blog meant having a Google account and using Blogger’s editor. That’s a higher bar than it needs to be. The new setup is just Markdown files in a Git repo. If you can open a pull request, you can write a post.
Posts live in content/posts/{slug}/index.md with YAML frontmatter for the title, date, authors, and tags. Images go right next to the post in the same directory. No special tooling required beyond a text editor.
Want to write about a Python release, core sprint, governance update, or anything else that belongs on the official Python blog? Here’s the short version:
content/posts/ with your post slugindex.md with your content (and optionally upload your images)The repo README has more detail on frontmatter fields and local development if you want to preview your post before submitting.
Beyond the content itself, the new site has a few features the old Blogger setup never had. Here’s a live look:
All posts are browsable with pagination, a year filter, and a tag sidebar. Click any tag or year to narrow things down.
See who’s been writing, how much they’ve contributed, and browse their posts individually.
Every tag across the archive, ranked by how often it appears. Great for finding all the release announcements or security updates in one place.
Hit Ctrl+K (or Cmd+K on Mac) from any page to open the command palette. It searches across all 307+ posts by title, author, tags, and description. There are also keyboard chord shortcuts for quick navigation.
The site is built with Astro and deployed as fully static HTML. There’s a Keystatic CMS available in dev mode if you prefer a visual editor over raw Markdown, but it’s entirely optional. Tailwind handles the styling. The whole thing builds and deploys through GitHub Actions.
If you spot broken links, missing images, or formatting issues from the migration, file an issue on the repo. PRs are welcome too.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。