Uncategorised decision
Tech Forum
A competent technical user can reproduce the core public-facing site (static articles, RSS, search, deploy) in about a week; you would lose the publication's brand, editorial resources, and scale.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$50one-off24 h to build
$0/mo1 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Author publishes articles -> site builds and publishes static pages and RSS -> readers browse and search articles
What it still won’t have
- Established brand recognition and trust
- Editorial team, ongoing reporting and newsroom workflow
- Scale, timeliness, and SEO authority of an existing publication
- Any proprietary CMS or analytics the site currently uses
What remains hard
- Brand trust
Tech Forum — Canada's independent technology publication.
First-year cost
No published price
Tech Forum does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a self-hosted static technology news site using Hugo (Go) for the site generator, Netlify CMS (Git-backed) for editing, and Netlify/Vercel for CI/CD and hosting. Core features in scope: article content type with metadata (author, date, categories, tags), responsive templates for list and article pages, generation of RSS and sitemap, client-side full-text search with Lunr.js, image asset handling, and a migration script (Python) to convert existing HTML/CSV articles into Markdown. Out of scope: recreating the existing brand and editorial staff, paywalls, sophisticated analytics, user accounts, or comments. Include build and deploy scripts, basic automated tests for the migration script and templates, and error handling for failed builds and missing images.
How we checked
How the score was reached
- Build verdict base78
- Evidence score78
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 1
Every page the run actually retrieved.
- official productTech Forum | Canadian technology news and innovation
Integrity checks
What held up, and what did not.
