ADR 001: Migrate to Hugo SSG #10

New issue

Closed

opened 2026-04-20 11:33:06 +00:00 by janhalen · 1 comment

janhalen commented

2026-04-20 11:33:06 +00:00

(Migrated from github.com)

ADR 001: Migrate to Hugo SSG

Status: Proposed

Context: The current site is a Vite/React application with a Supabase backend, generated via Lovable. This architecture introduces significant maintenance overhead (NPM dependency management, backend API maintenance) and is tied into a single proprietary solution and vendor.

Decision: Migrate the Lovable site to Hugo SSG using Markdown for content and GitHub Pages for hosting.

Consequences:

➕ Positive: Eliminates backend maintenance; removes local build requirements for the maintainer via GitHub Actions; reduces hosting cost to zero; simplifies content editing to Markdown.

➖ Negative: Loss of all dynamic Supabase features (e.g., authentication, real-time updates).

0️⃣ Neutral: Shift from a dynamic app to a static website.

ADR 001: Migrate to Hugo SSG Status: Proposed Context: The current site is a Vite/React application with a Supabase backend, generated via Lovable. This architecture introduces significant maintenance overhead (NPM dependency management, backend API maintenance) and is tied into a single proprietary solution and vendor. Decision: Migrate the Lovable site to Hugo SSG using Markdown for content and GitHub Pages for hosting. Consequences: ➕ Positive: Eliminates backend maintenance; removes local build requirements for the maintainer via GitHub Actions; reduces hosting cost to zero; simplifies content editing to Markdown. ➖ Negative: Loss of all dynamic Supabase features (e.g., authentication, real-time updates). 0️⃣ Neutral: Shift from a dynamic app to a static website.

janhalen commented

2026-04-20 12:18:39 +00:00

(Migrated from github.com)

Astro was tested out first.. but the Containerized npm heavy setup was not really suited for local containerization..