A fullstack MEN application (MongoDB, Express.js, Node.js) with fully functional CRUD capability to help organize and plan Potluck Parties. This app includes the use of Passport and Google OAuth2 for authentication and authorization granting specific permissions to each profile, and uses Mongoose models and schemas to organize data structures. The app is deployed on Heroku and can be found here.
Potluck Planner was created with the intention to make use of Create, Read, Update, Delete (CRUD) functionality with storing and embedding/referencing data in mind. With the ability to login and view relevant information for a get together where many pieces of information need to be tracked, saved, and shared, any potluck would be able to benefit with this app being leveraged for planning purposes!
Also, potlucks are cost-friendly, social, and can hold a lot of history from the participants. It's my hope that with the stretch goal features being built in and refactored into the app, we can have more potlucks, more getting-to-know-each-others, more social connections, and more good food go around.
The following technologies were used to build this stack:
My initial wireframe was the conception of a rather complicated backend routing architecture which I have placed in my stretch goals. I've re-routed most of it to create this initial MVP working version at the bottom, which cuts down on a separate Model for the dishes and cross-functional user interactions. I used Trello to keep track of my progress and notes.
The app requires a Google OAuth2 login - once you are logged in, you can go to "All Potlucks" and create a new potluck, and start adding guests and what they're bringing to the party! The app also includes a menu feature to see what's in store for the day.
Ideally I'd like the app to be an entire ecosystem of a potluck loving community. I'd like to refactor the data modeling and the entity relationships to allow the dishes to have their own profiles owned by a specific user, where others can comment and add feedback/leave reviews. This also allows information such as addresses and allergens to be saved and automated into the planning process, making all potentially releavnt information be available to all.
This was the initial conception of an ERD I was coming up with but required a lot more backend architecture and routing complications that was a bit beyond a half week project.
I'd also love to add some API's like Google Maps, Recipe API's, and even an Instagram API to add images from the party.
- Favicon is from Icons8
- Badges for technologies were take from Ileriayo's GH repo using shields.io
- I followed Kyle's open modal tutorial to create the expanding menu - really helpful tutorial!
- My best friends for any learning project:
