Data-Driven Publishing Platform — Go Rebuild

An unlaunched Go rebuild of my publishing platform, using PostgreSQL for application data and background jobs, React for administration and Astro for public websites. It includes source processing, publishing checks and migration tools for the existing sites.

Data-Driven Publishing Platform — Go Rebuild

About Data-Driven Publishing Platform — Go Rebuild

This is the Go rebuild of my Data-Driven Publishing Platform. The original Laravel application runs four domains. This version has never launched.

The rebuild separates the application into clearer responsibilities. Go handles source imports, data processing, publishing rules, scheduling and background work. React and TypeScript provide the administration interface. Astro builds the public websites from exported page data.

PostgreSQL stores the application records and the durable job queue. Workers claim jobs, track their progress and handle retries, cancellation and recovery after interruptions. Valkey is available for caching, rate limits and short-lived locks.

The source history remains central to the application. Imported records retain their versions and observations, and the administration interface lets me inspect changes, investigate failures and reprocess data.

New information can also be checked before it replaces what visitors currently see. A refreshed page can remain pending while the previously approved version stays public. The rules differ by site: software pricing needs a separate review, while travel-plan pricing needs sufficiently complete and recent source evidence.

Generated summaries are tied to the facts used to produce them. If those facts change, the application can identify when a summary needs regenerating instead of carrying old wording forward alongside new data.

Publishing the static sites brings another set of checks. Builds validate that sitemap entries correspond to generated pages. Releases are kept in separate versioned directories, with an activation step and a rollback path.

There is considerable migration work here too: importing the Laravel data, comparing page output, preserving URLs and deciding which old routes should remain, redirect or be retired. Individual sites can be held in a read-only or shadow state while those checks run.

The project includes implementations for vehicle recalls, software comparisons, public procurement, token data and travel eSIM plans. It also carries over the search-monitoring integrations and operational tools from the original platform.

It reached a substantial implementation, but it never took over the live sites. The screenshots and description document the rebuild as it stands, with the production migration still unfinished.

Release history

Version 0.226.2