2.0 KiB
Status
Last Completed
Changed the path of the generated prisma files becasue it was incorrect on init. Started writing the server file to begin the process of hooking the frontend up to db.
Next Up
Choose auth provider and hook that up. Need to hash passwords with auth provider.
Feature List
Must Haves
- Events
- Event guests (related to Guests)
- Related guest (for +1s)
- RSVP status
- To Do list
- Event Vendor (related to Vendors)
- Event Venue (related to Venues)
- General Notes
- Event guests (related to Guests)
- Guests (address book)
- Vendors
- Contact info
- Contracts
- Venues
- Contact info
- Contracts
Eventual Features
- Registry (related to Events)
- Ability to upload any url
- Redirects
- Convert url to
BASE_URL.com/[EVENT_SLUG]/registry/[item123]which redirects to actually link
- Ability to upload any url
Decisions Log
At the top level the guest book will contain "Households". Every guest will belong to a household even if they are alone. This will allow for Guests to RSVP for everyone in their household.
For guests that are given a +1, there will be a placeholder name added as a Guest "Guest of [NAME]". And a flag will be added to that guest entry. When responding to the RSVP, there will be an option to fill in the +1's name.
The (app) directory will be for all pages that need to have authentication. These will be the pages that the couple or planner will have access to. Publically facing pages will be in the (public) directory (things like the landing page and login page). This will also allow for a "wedding website" option that is publically accessible.
Decided to make Venues part of the Vendor model since they are practically the same, and contain most of the same behavior. People can "shop around" for venues just like they can with any other vendor.
Open Questions
I would like to have a general AllowList for the urls in the registry but give users the option to add more to the AllowList if they would like.