Code & Tech

Recovered article archive

Article records and their categories/tags are loaded from JSON files recovered from an old WordPress database. The current app does not depend on a running WordPress API.

Reading and browsing

Articles have their own routes. Listing, category, tag and interview views use the archived post and taxonomy data.

Search and suggestions

Search matches article titles, excerpts and HTML content in the local archive. The suggestions endpoint checks a smaller post subset alongside categories and tags.

Metadata and feeds

Article routes build titles, descriptions and social metadata. RSS and sitemap routes enumerate archived posts with canonical blog URLs.

Projects and contact

The projects route requests data from the portfolio API and falls back to example records. The contact page displays contact information; the current code does not implement an active Resend contact-form endpoint.

Static JSON content provider

src/lib/wordpress.ts keeps the WordPress-shaped types but reads archived post and taxonomy JSON. It returns those records for listings, article pages and text search.

Safe rendering of archived HTML

The article layout sanitizes recovered HTML before inserting it into the page, and rewrites links to recovered same-site articles at render time.

App Router and metadata

Individual article pages build route metadata; sitemap and RSS handlers generate feed entries from the archived post catalog.

Autocomplete and search

The search UI debounces requests to a local suggestions endpoint. Full results filter a local archive using text matches and route parameters.

Keep old articles after the CMS went away

Problem: The WordPress database backup retained posts and taxonomies but not the uploaded media.

Solution: The app serves the recovered articles from JSON and omits missing original featured images; the restored article content still needs editorial verification.

Keep historical article links useful

Problem: Imported HTML points to the previous host and includes old WordPress paths.

Solution: The content adapter rewrites known same-site links to recovered article routes when rendering, without altering the archived source JSON.

Avoid executing arbitrary recovered HTML

Problem: Archived WordPress article markup cannot be treated as automatically safe frontend HTML.

Solution: The article component sanitizes the rendered HTML before inserting it into the page.