State of the Nation and next steps 2025-10-23

Nobody has claimed this yet.

- [ ] Clarify the current state. Establish a clear understanding of the existing migration system and its moving parts.
- [ ] Do a code walkthrough: identify each script’s role (e.g. image renaming, upload, content creation).

### 2. Create minimal functional tests

* **Goal:** Verify that the migration *actually works* for basic cases.
* **Action:**

* Write a small set of automated tests (pytest or similar) that check key invariants:

* A post successfully created in WordPress.
* Content and images appear as expected.
* Slug and metadata integrity.
* Start with a “single-page migration” script as your simplest working example.
* Use that as a reference baseline before scaling up.

### 3. Separate pre-migration refactors

* **Goal:** Improve input data quality *before* migration to reduce complexity later.
* **Action:**

* Do the **image naming refactor** directly in the source Markdown repo (SEO-friendly, consistent).
* Optionally run link rewriting or metadata normalization there too.
* Commit these as clean preparatory steps so the migration scripts deal only with already-clean data.

Start by walking through the migration scripts and documenting each role, including image renaming, uploads, and content creation. Use the single-page migration as the baseline, then add minimal pytest coverage for WordPress post creation, content and image output, slug, and metadata integrity. Done means the basic migration is verified and preparatory image naming or link and metadata cleanup is committed separately.

Written by the indexing model from the issue text.