brian/planner
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

built out schema

Browse Source
This commit is contained in:
Brian Nelson
2026-10-07 11:13:44 -04:00
parent 4e9c5d3355
commit 8d25f34738
4 changed files with 312 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
PROJECT.md
View File

@@ -1,9 +1,9 @@
## Status
### Last Completed
Continued working on the app structure, more specifically started playing around with redirects and created an example registry to see how that would work.
Built out the schema for the most part
### Next Up
Continue to build on app structure
Actually apply the schema and play around with adding data in studio
## Feature List
### Must Haves
@@ -35,6 +35,8 @@ For guests that are given a +1, there will be a placeholder name added as a Gues
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.