davide
33b49c5dbb
PocketBase gains optional, manually-authored English fields on articles and categories (same record, same slug), and the frontend serves an /en counterpart of every dynamic route via thin page wrappers around shared view components — no i18n library, consistent with the project's existing minimalism stance for a two-locale site with ~20 UI strings. An article/category with no translation 404s cleanly on its own /en detail page and is filtered out of /en listings, and the header's language-switch link falls back to the English blog index rather than a dead link; resolving that requires a global route middleware, since the layout's header renders before the page content in document order and so can't react to state a page component sets during its own async setup.
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.