blog.hichee.com (Astro Migration)

Migration target for blog.hichee.com, moving from WordPress to Astro + Cloudflare Pages.

Decisions

• Repository remains private during migration.
• WordPress drafts are migrated as unpublished content under src/content/drafts/.
• We create one GitHub issue per unpublished draft (draft-review label) so nothing gets lost.
• Media strategy defaults to object storage/CDN (Cloudflare R2), not repository storage, unless final measured media size is small enough.

Local Setup

yarn install
yarn dev

Deployment Setup (Cloudflare Pages)

Project: blog-hichee-com Current Pages URL: https://blog-hichee-com-git.pages.dev Current staging/cutover URL: https://newblog.hichee.com

This project is connected to GitHub (shakacode/blog.hichee.com) in Cloudflare Pages.

• Pushes to main trigger production deployments in Cloudflare.
• Pull requests trigger preview deployments in Cloudflare.

No custom GitHub deploy workflow is required for Pages deploys.

Migration Workflow

1. Extract WordPress content through authenticated REST API (requires WP login):

yarn migrate:download:rest

2. Convert REST export to Astro content collections:

node scripts/convert-rest-to-content.mjs --input data/raw/wp-rest-export-YYYY-MM-DDTHH-mm-ss-sssZ.json

3. Build media manifest + size estimate:

node scripts/build-media-manifest.mjs --with-head

4. Create GitHub issues for drafts:

# dry run
node scripts/create-draft-issues.mjs

# create issues
node scripts/create-draft-issues.mjs --apply

Staging and Cutover Plan

• newblog.hichee.com is the Cloudflare Pages staging site.
• Run QA checklist (links, SEO, images, page templates, redirects, performance) against newblog.hichee.com and the current live WordPress site at blog.hichee.com.
• Freeze WordPress edits, run final delta sync, then switch blog.hichee.com.
• Do not switch blog.hichee.com until the old WordPress origin has a backup hostname and LEGACY_MEDIA_ORIGIN is set to that hostname in the Pages production environment.