davide
49c42ecc96
Strapi + Postgres are gone in favor of PocketBase: a single Go binary with embedded SQLite, built-in admin UI and per-collection API rules. No content existed yet, so this is a clean swap with no data migration. Collections and rules are defined as code in pocketbase/pb_migrations/ and applied automatically on first boot. Draft & Publish has no native PocketBase equivalent, so it's reproduced with a nullable `publishedAt` field enforced by listRule/viewRule, matching the old Strapi semantics. Routing flips: PocketBase's admin UI and REST/file API are hardwired to `/_/` and `/api/*` at the domain root (its own dashboard assets and API calls reference those paths directly, so a stripped path prefix like `/admin/*` would break them). `/api` is therefore reserved for PocketBase now, and the frontend's Nitro endpoints move to `/content/*` (frontend/server/routes/content/, not server/api/). A `/admin` vanity route in Nitro (not Caddy) redirects to `/_/`, so it works the same in dev, where Caddy isn't part of the stack, and in production. frontend/server/utils/strapi.ts becomes pocketbase.ts; queries.ts is rewritten for PocketBase's filter/sort/fields/expand query syntax. StrapiImage becomes MediaImage (no width/height — PocketBase file fields don't store dimensions, and the cover images already reserve their aspect ratio via CSS, so this is not a regression). docs/*.md, CLAUDE.md and README.md are updated in the same commit.
1.2 KiB
1.2 KiB
Documentation
Technical documentation for this repository. For setup, deployment and day-to-day commands, see the root README.md; for coding conventions and constraints, see CLAUDE.md. These docs explain the structure and behavior of the system in more depth than either of those.
- architecture.md — services, routing, request flow, environment variables.
- content-model.md — PocketBase collections, admin panel, permissions, editorial workflow.
- frontend.md — Nuxt routes, server (Nitro) endpoints, data flow, SEO.
What this repository is
A blog website with two faces:
- Public site — anonymous visitors read articles and browse categories. Fully server-rendered, no login, no client-side calls to the CMS.
- Admin panel — the site owner logs into PocketBase's admin UI (
/admin, redirects to/_/) to write, edit and publish articles and categories. This is the only way content changes; there is no other CMS and no public user accounts.
One codebase, two runtime components (Nuxt frontend, PocketBase — CMS and database in one process), fronted by a single Caddy reverse proxy on one domain.