37 lines
1.2 KiB
Markdown
37 lines
1.2 KiB
Markdown
## Status
|
|
### Last Completed
|
|
Worked on the (Feature List)[#feature-list]
|
|
|
|
### Next Up
|
|
Start building the database structure or the app layout and structure
|
|
|
|
## 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
|
|
- 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
|
|
|
|
## 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.
|
|
|
|
|
|
## Open Questions |