app structure
This commit is contained in:
@@ -1,9 +1,9 @@
|
||||
## Status
|
||||
### Last Completed
|
||||
Worked on the (Feature List)[#feature-list]
|
||||
Started building out the app structure and putting in placeholders for unique rsvp token pages
|
||||
|
||||
### Next Up
|
||||
Start building the database structure or the app layout and structure
|
||||
Continue to build on app structure
|
||||
|
||||
## Feature List
|
||||
### Must Haves
|
||||
@@ -33,5 +33,7 @@ At the top level the guest book will contain "Households". Every guest will belo
|
||||
|
||||
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.
|
||||
|
||||
|
||||
## Open Questions
|
||||
Reference in New Issue
Block a user