Blogger Migration

[JacobCoffee]

It is time to migrate away from Blogger for all blogs (PSF, Python insider, etc.)

My proposed solution is an Astro.js site that statically renders via GitHub Pages.

Here is an example post and its Blogger equivalent

Redirects happen:

https://blog.python.org/2026/02/python-3143-and-31312-are-now-available.html ->
https://jacobcoffee.github.io/python-insider-blog/2026/02/python-3143-and-31312-are-now-available.html -> becomes https://jacobcoffee.github.io/python-insider-blog/2026/02/python-3143-and-31312-are-now-available/

Semantic structure remains mostly the same minus some small caveats:

Deduplicated python-3 slugs (Blogger reused the same autosslug for different posts):

• /2018/06/python-3.html → python-3-2
• /2018/02/python-3.html → python-3-3
• /2015/08/python-3.html → python-3-4
• /2015/03/python-3.html → python-3-5
• /2019/09/python-3.html → python-3-6

Plus the 2 posts where the month differs between Blogger's URL and the actual publishDate:

• /2014/02/python-269-is-now-available.html → /2013/10/python-269-is-now-available
• /2018/01/python-370b1-is-now-available-for.html →
  /2018/02/python-370b1-is-now-available-for

still,, all 9 are covered by redirects.

https://pythoninsider.blogspot.com/ will remain as is but not receive any updates aside from maybe a final "We're here now" post + accompanying RSS feed to update feed readers. The Blogger RSS feed path (/feeds/posts/default has a redirect set to /rss.xml. With one small thing to note: the Blogger ?alt=rss query parameter won't work as i don't think i can make it handle query params.

https://blog.python.org/ will have DNS pointed at the GitHub pages entry.

The GitHub repo will be transferred into the Python enterprise, most suitably the Python organization but it can live in the psf org if desired.

---

This is a static site generation where nothing else is needed from the contributors aside from now you write markdown (which i hope all of you will appreciate.)

Please bring your requested changes and concerns here so that we can get this migration shipped.

[hugovk]

Thank you for working on this, looks really good!

I'll be very happy to stop using the dated blogger.com UI, and pretty much any modern SSG is good. I've heard good feedback about Astro, it's also used for https://ep2026.europython.eu.

blog.python.org is mostly only used for release announcements nowadays (but the rest of the core team is also welcome to post there! Maybe a modern blog will be more encouraging!), and I write them in Markdown, which gets pasted into Discourse, and python.org/downloads (which also accepts RST/HTML/plaintext). I then use Pandoc to convert into HTML to paste into blogger because its own WYSIWIG is horrible.

So I'm already using Markdown, so it makes things easier to stick that in this SSG as well. I think the other RMs also use Markdown as much as possible.

---

Looking at https://jacobcoffee.github.io/python-insider-blog/2026/02/python-3143-and-31312-are-now-available/, I don't think we need the "Referenced in this post" section. Nor even "Originally published on Blogger", but if anyone finds it useful, I suppose it could go at the end. But do we want to send traffic there?

[JacobCoffee]

Maybe the referened in can be added to a TOC sidebar, along with sections to jump to based on markdown header sizes? and for originally published, this is purely for older posts so newer ones wouldnt have it but if we want to move it to the bottom then we could? I was mainly thinking about backlinks and SEO for these both.

[StanFromIreland]

Also, the footer has a link to the retired python-dev mailing list, that should probably be a link to the Python Discourse?

[gpshead]

https://blog.python.org/ will have DNS pointed at the GitHub pages entry.

Yay. To me this is the main thing, I just want the canonical URLs for these to be a PSF owned domain rather than the service providers.