Det kunne være godt at have TailwindCSS til at hjælpe os med layout delen - og spare os for en masse besvær/gætterier

Husk - her er en ganske fin beskrivelse af hvordan dette issue løses

In the meantime, I'll be setup up Wallaby for us to do integration tests

I'm taking a stab at it - and this is the first draft

DB design

This is where we're sketching out the information which Ticket
will persist for us.

As a user [contact with credentials] I would like to see what tickets [events] my coworkers [contacts belonging to contact] and I have.

As a participating scout [contact with credentials] I'd like to be able to comment [post belonging to a post] on a comment [post] where someone [contact] suggests that I [contact belonging to event] should accept responsibility [with role "delegated_to"] for a ticket labeled 'Åbningslejrbål' [event]

Core Elements

• event
• contact
• post

We could totally abstract this away by adding

• event

  • id
  • resource_id
  • ...

• contact

  • id
  • resource_id
  • ...

• post

  • id
  • resource_id
  • ...

• resource

  • id
  • ancestors

• resource_events

  • resource_id
  • event_id

• resource_contacts

  • resource_id
  • contact_id

• resource_posts

  • resource_id
  • post_id

@JacobArrow - er du frisk på at se, hvad der er galt?

😆