Registrace
Bilingual (CZ / EN) event-registration platform for Diamond Way Buddhism (BDC) centres.
Public visitors register themselves and fellow participants for meditation and community
events; the app prices the stay server-side and emails a bilingual confirmation. Centre
admins manage events, registrations and exports — all scoped by role and centre.
Table of contents
What it is
Registrace is a production web application built for
Buddhismus Diamantové cesty (BDC / Diamond Way Buddhism) — a network of
Czech meditation centres. It replaces ad-hoc spreadsheets and email threads with a single
bilingual flow:
- A visitor opens a published event, fills in one form for the whole group (up to 10
participants), picks arrival/departure, meals and diet per person, and submits.
- The server recalculates every price from the event's own pricing rules (the browser
figure is informational only), writes an idempotent registration, and sends a confirmation
email carrying a human-readable registration number (e.g.
260020108).
- Centre admins review, filter, search, edit any registration in full (stay, people,
meals — re-priced by the server), mark paid, resend confirmations, and export a per-event
XLSX for the kitchen and accommodation teams — always scoped to the centres they manage. A
built-in help page and "?" hints beside the harder fields explain how events and prices work.
It is live in production at registrace.online on Vercel +
Supabase, and has been through a full internal build (B1–B8), a production-hardening pass
(P1–P8) and a multi-agent security audit, and has run real events since. This README is the
single source of orientation for anyone joining the project.
Screenshots
The registrations in these screenshots are a demo dataset — fictional families on the
RFC-2606 reserved example.* domains, never real registrants; the maintainer's throwaway
test events are left out of the events list. The organiser contact on the event page is the
maintainer's own. The admin email addresses and the audit-log IP column are blurred here on
purpose for privacy: they are shown normally to admins in the running app — only these
public screenshots hide them.
Visitor side
Admin side
This is the beginning of the README. Read the rest at the original. Read the full README ↗
