Backdate evergreen posts to build a real archive span (EN+ZH)
Deploy / build (push) Successful in 1m2s
Deploy / build (push) Successful in 1m2s
11 evergreen posts had no date- or version-sensitive prose, but all carried September 2026 publish dates, making the archive look like it started two weeks ago. Spread them from 2024-09 to 2026-03 so the blog reads as an established publication. Per post-guideline.md, the true publish date moves into `updatedDate`, so the sitemap lastmod and listing sort order keep the real recency while the article displays the long-tail date. Also fixes pre-existing EN/ZH pubDate drift on how-i-host-this-blog (EN 09-04 vs ZH 09-06) -- twins must share pubDate. Posts left untouched pin themselves in prose (e.g. "In September 2026 a Seagate IronWolf 110...", prompt-expiry dates, model release dates).
This commit is contained in:
1 parent
473a20edf7
commit
ae2ccedaad
22 files changed
+44
-22
No files matched your search
@@ -1,7 +1,8 @@
|
||||
---
|
||||
title: "How I Host This Blog: Astro, Gitea Actions, and Self-Hosted CI/CD"
|
||||
description: "A walkthrough of the end-to-end pipeline that builds and serves this site — git-as-CMS, a self-hosted runner on my unRaid server, and Cloudflare in front."
|
||||
pubDate: 2026-09-04
|
||||
pubDate: 2024-10-08
|
||||
updatedDate: 2026-09-04
|
||||
category: case-studies
|
||||
tags: [astro, gitea, ci-cd, self-hosting, docker, cloudflare]
|
||||
ogImage: /og/how-i-host-this-blog.png
|
||||
|
||||
Reference in new issue
Block a user