mAi
9274cca8c0
Adds `form_definition.locale` (default 'de'). When set to 'en', every
hardcoded German participant string flips to English: closed banner,
name field label + placeholder, summary card title/subtitle/term, all
banner copy, submit + chat send buttons (both default and in-flight),
chat empty state, chat placeholder, results section heading, validation
error prefixes ("Bitte beantworte" / "Please answer"), rate-limit
errors, and the boolean Yes/No labels in the per-type input component.
Shape:
- `lib/i18n.ts` exports `tr(locale, de, en)` — a tiny inline-strings
helper, no central catalog. New strings = inline both at call site.
- Components read the active locale via Svelte context
(`setLocale`/`useLocale`) so per-question-type inputs don't need a
new prop on `ParticipantInputProps`.
- `submit_label` override still wins over the localized default — so
forms that already set submit_label keep their custom text.
In-scope for this commit: participant page (`/f/<slug>`) only. Admin,
FormBuilder, FormBuilder type picker, builder-side strings ("Inhalt
(Markdown)", etc.) all still German. Per m/fdbck#3 the participant
surface was the most-visible audience; admin can follow in a separate
shift.
Motivation: upc-session-2026-5 is an English-audience form; chat is
enabled per m's intent so suppressing strings per-instance wasn't an
option. Per-instance locale was the right shape.
fdbck.msbls.de
Per-link feedback forms and live-chat masks. Anonymous, slug-gated, no auth required for participants.
Spun out from m/flexsiebels.de issue #63 — full design at docs/plans/feedback-feature.md.
Stack
SvelteKit 5 + Svelte 5 + bun + @sveltejs/adapter-node. Postgres + Supabase auth. Schema: fdbck.feedback_{instances,submissions,posts} on supa.flexsiebels.de (msupabase).
Run locally
cp .env.example .env # fill SUPABASE_*
bun install
bun run dev
Test + check
bun run test # rate-limit + public-scope unit tests
bun run check # svelte-check (type errors / a11y)
bun run build # adapter-node production build → ./build
Deploy
Dockerfile uses oven/bun:latest. Dokploy app: fdbck.msbls.de. DNS via Hostinger (handled out of band).
Structure
src/
hooks.server.ts — auth + public-scope policy gate
lib/server/
auth.ts — cookie JWT + Supabase refresh
fdb.ts — Postgres `fdbck` schema accessor
feedback.ts — slug generator + DB helpers + rate-limit constants
public-scope.ts — anonymous-DB-access fail-closed gate
rate-limit.ts — in-memory token bucket
schemas.ts — Zod request validation
supabase.ts — admin + anon client singletons
routes/
+page.svelte — landing
f/[slug]/ — public participant page (form + live chat)
admin/feedback/ — m's admin (list + detail + create)
api/
auth/ — sign-in / sign-out
public/feedback/ — anonymous slug-gated endpoints
admin/feedback/ — owner-scoped admin endpoints
Data model (canonical: design doc §5)
fdbck.feedback_instances— slug, title, description, owner_user_id, form_definition (jsonb), chat_enabled, status (open|closed), closed_atfdbck.feedback_submissions— instance_id, display_name (nullable = anonymous), client_session_id, answers (jsonb), client_ip, user_agentfdbck.feedback_posts— instance_id, display_name, client_session_id, body, hidden (m soft-moderate), client_ip, user_agent
Anti-abuse layers
- 32-char base62 slugs (~190 bits entropy)
- in-memory rate-limit (30 posts / 5 min, 10 submits / 5 min, per IP+slug)
- honeypot field on forms + chat (silently dropped)
- body length caps + closing kill-switch
- noindex meta +
robots.txtDisallow: /
Out of scope (v1)
Drag-drop form-builder · post reactions · realtime/SSE · CAPTCHA · trusted-tier owner sharing · branding/theming · auto-notifications. All have a clean upgrade path on the existing schema.
Issue origin
m/flexsiebels.de#63 — m PWA-voice 2026-05-05: "Im Wesentlichen quasi Microsoft Forms und Teams-Feedback in einem auf einer Webseite."