Janek's Computers

MVP requirements:

• root link shows all guests
• make gl component
• pass guests into it
• ability to add guests
• ability to edit?

• from a root link you can create a link that gets put in a db

• x

Side things:

• nextjs tutorial

• use layout.tsx

• fix “hydration” bug

• connect DB first
• use example from the Todo list app

• tutorials: nextjs standard and also the other thing

• we lock: one org, one event for now

• create a link id manually from DB for each event

• going to guestlist.turbulence.berlin/9dvabfd opens a table
• looks like notion groupby?

• let’s avoid auth for now - all links are public
• main link shows a list of guests

X

• example link: guestlist.turbulence.berlin/9dvabfd
• no login, just links
• root list can
• create new spots
• delegate existing spots
• put names in
• change names
• name organisations they delegate to
• write GL policy
• sublists can
• do anything root list allows them to

• should scan either name or QR

Elements / flow

Input

• links to a web app

• (telegram)

• app (the same that scans QRs)

• share as image with QR

Display

• web app

• mobile app

Data

• delete after event?

Verification

• export somewhere? not really, needs to be update’able

• sync to something - more likely

Super simple start

• db schema worth it anyway?

• what’s the quickest we can do?

For Turbulence (Feb 2024)

• we currently don’t have a guestlist solution and need one

• hack: use the ticketing system for it (a contingent of free tickets)

• “we have to be able to send a link to an artist that they then edit”

• there’s no need for recursive links, but consider for the future

• for scanning, consider importing into pretix or something

Archive