Publish UXDB for 2026 tickets

Where we are

The public catalogue is live and crawlable at /uxdb/. Rollout is still dogfooding (not in primary nav). Goal: sell UX Brighton 2026 tickets. Bombay parent: publish-uxdb-fitness-audit.md.

To do

Login visibility — signed-in team database at /uxdbpro/

Bombay: uxdb-login-visibility-under-uxdb.md. Two URL namespaces (public /uxdb/, private /uxdbpro/); public pages stay sponsor-free. Hub moved; internal entity sponsor pages still optional follow-up.

Dogfooding checklist — public surface

Open the catalogue hub

Local: http://uxbri.local/uxdb/ · Live: https://uxbri.org/uxdb/

Open a speaker, event and session page

Try Emma Boulton, UX Brighton 2012 and Deep Interaction.

Confirm entity pages have no in-page conference promo

Speaker, event, session and method pages should not show the Get 2026 tickets card. Ticket promotion stays on the site-wide footer / countdown — e.g. Deep Interaction.

Dogfooding checklist — private boundary

Confirm the public page has only three tabs

Speakers, Sessions and Events. No podcasts, sponsors, methods or tools.

Open the internal database

Local: http://uxbri.local/uxdbpro/. Production stays behind Lab login. Canonical home: /uxdbpro/ (not under public /uxdb/).

Confirm raw internal JSON is not public

/uxdb/data/sponsors.json should not be a public file. Public data is /uxdb/public/manifest.json.

Dogfooding checklist — before wider rollout

Read the privacy note

dpia.md and /uxdb/about/.

Regenerate the public export after data edits

From the repo: npm run uxdb:public.

To do

Login visibility — signed-in team database at /uxdbpro/

Make the UX Brighton 2026 event page ticket-ready

Exclude hollow events from the public export

Clarify Get tickets means UX Brighton 2026

Add internal links from talks to UXDB speakers

Measure promo clicks through to tickets

Advance rollout past dogfooding

Later: enrich speaker photos and known_for

Later: primary nav link to /uxdb/