Skip to content

v0.3.0 — one container, forms, redirects, structured data, remote MCP

Latest

Choose a tag to compare

@hybriden hybriden released this 17 Oct 19:03
· 182 commits to main since this release
6035d7e

Four months and 340+ commits since v0.2.0. Paperboy is now one container, has forms with submissions in your own database, redirects, structured data set up in the CMS, and an MCP server remote AI clients sign in to with OAuth.

One container

  • nginx is gone. The api serves the admin SPA itself, with the same CSP, caching and gzip, so the __Host- cookie and CSRF Origin check need no proxy. ghcr.io/hybriden/paperboy-app is the only image; paperboy-admin is no longer published.
  • The image honours the platform's PORT, so it runs as-is on App Service, Container Apps, Cloud Run, Fly or Render with a managed Postgres. MCP_EMBEDDED=true runs the MCP server inside the same container.
  • apps/web (the reference frontend) is opt-in (--profile web). The website you build on is the Astro starter.

Forms, with the submissions in your database

A form is content: a Form block with one block per question. Delivery ships it as a schema, never markup. Submissions are validated against the published definition, unknown fields are rejected, errors come back per field. Honeypot and fill-time check on by default, Turnstile opt-in. Retention actually runs, IP storage is opt-in, erase-by-email is one audited action. The admin has a forms builder over the same model, with a visitor-eye preview of each question.

Redirects that keep link equity

Per-site rules under Settings → Redirects, served as one manifest and matched in the frontend with matchRedirect from the client SDK. A rename or move records a 301 automatically on publish. Targets are pages, so rules never chain. A 404 log shows what visitors actually miss.

SEO and structured data, set up in the CMS

  • A SiteSettings global typed Organization is the site's identity and is delivered as JSON-LD.
  • Content areas with a schema.org property become nested nodes, so an FAQ page delivers its Question/Answer pairs as mainEntity.
  • dateModified on every page from its last publish.
  • robots.txt, sitemap.xml, llms.txt and security.txt are generated from content and proxied by the frontend.

MCP for remote agents

  • OAuth 2.1 sign-in (discovery, dynamic registration, PKCE, refresh rotation). Consent picks the site. Revoke under Settings → Connected apps.
  • Site-scoped tokens, minted as the signed-in user; one server reaches every site, each tool takes a per-call site.
  • Upload links: an agent curls its own files to a 15-minute link instead of pushing base64 through a tool call. upload_asset takes a public URL too.
  • Globals have a home in the admin, API and MCP.

Content model

  • Parts: a block type that only ever nests inside another (nestedOnly).
  • Declared child ordering on a container: manual, name, created, or any field.
  • Type templates: a built-in library plus your own, with export/import between instances.
  • Internal links that cannot rot, and a real link editor. Slugified select values.

Admin

  • On-page editing reaches fields inside content-area blocks; dotted area outlines with an "+ Add block" chip that opens an anchored palette.
  • Shared blocks preview standalone; "Used on" shows where a block lives.
  • Installable PWA, a mobile pass for dashboard and settings, a design-system pass (light and dark), review-changes before publish, per-field validation.
  • Writing assistant: rename, undo, locale-aware prompts, pinned prompts. Any OpenAI-compatible endpoint alongside Anthropic, a searchable model picker, a reasoning-effort setting.

Webhooks and SDK

  • delivery.changed fires for every move, sort, trash or settings change, so a cache can purge on webhooks alone.
  • @paperboycms/client 0.6 ships matchRedirect and preview-token verification (WebCrypto, separate subpath). @paperboycms/preview 0.4 (from 0.1): area outlines, add-block chip, additive paperboy:add-block.

Upgrading from v0.2.0

  1. Remove the old admin container before recreating the api, or port 8090 is still taken. From the compose directory:
    docker rm -f $(docker ps -aq --filter label=com.docker.compose.service=admin --filter "label=com.docker.compose.project.working_dir=$PWD") && docker compose up -d --no-deps --force-recreate api
  2. docker compose down skips profiled services: remove a lingering <project>-web-1 by hand or with docker compose --profile web down.
  3. MFA_SECRET now goes through the placeholder guard. If yours is the compose default, set a real one and run scripts/rekey-mfa-secret.mjs.
  4. PREVIEW_SECRET must be set on both api and web; the browser never sees it. Drop any VITE_PREVIEW_SECRET.
  5. Migrations 0015–0031 run on api boot. No reseed.

Also new since v0.2.0: SECURITY.md with private vulnerability reporting, CONTRIBUTING.md, CodeQL on every PR, secret scanning and push protection, and a protected main.