Full Database and API routes Integration

.gitattributes

@@ -0,0 +1 @@
+* text=auto eol=lf

.gitignore

@@ -26,10 +26,11 @@ yarn-error.log*
 
 # local env files
 .env*.local
+.env.local
+.env
 
 # vercel
 .vercel
-
 # typescript
 *.tsbuildinfo
 next-env.d.ts

.vscode/settings.json

@@ -3,5 +3,11 @@
   "editor.formatOnSave": true,
   "editor.codeActionsOnSave": {
     "source.fixAll.eslint": "explicit"
+  },
+  "[typescriptreact]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
+  },
+  "[javascript]": {
+    "editor.defaultFormatter": "esbenp.prettier-vscode"
   }
 }

README.md

@@ -1,32 +1,58 @@
-# name of non-profit
+# hack4impact team 18 bootcamp project!
 
-{One sentence description of the project}
+a movie theater membership website we'll develop over the next few weeks!
 
-## Table of Contents
+## table of contents
 
-- [Overview](#overview)
-  - [Purpose](#purpose)
-  - [Team](#team)
-- [Getting Started And Contributing](#getting-started-and-contributing)
+- [getting started and contributing](#getting-started-and-contributing) --> start here!
+- [commits](#commit-statements)
+- [database connection](#database-connection)
+- [project board](#using-the-project-board)
+- [developer bootcamp site](#for-reference)
 
-## Overview
+## getting started and contributing
 
-### Purpose
+visit [getting-started.md](docs/getting-started.md) on info for how to set up this repo.
 
-{Short paragraph description of the non-profit mission and the purpose of this project. Who will this project help, why is it necessary. Impact of the project.}
+visit [contributing.md](docs/contributing.md) on info for how to contribute to this repo.
 
-### Team
+## commit statements
 
-The {non-profit name} team consists of {#} Cal Poly students. Over the course of about 9 months, we worked as a team to deploy this web application. The team members are listed below:
+write commit statements like you're explaining what you just did to someone who has no clue what you just did (because you are). commit statements are how you explain changes to others reviewing your code, and to your future self.
 
-- [First Last](https://www.linkedin.com/) - Project Manager
-- [First Last](https://www.linkedin.com/) - Designer
-- [First Last](https://www.linkedin.com/) - Tech Lead
-- [First Last](https://www.linkedin.com/) - Tech Lead
-- [First Last](https://www.linkedin.com/) - Software Developer
+the "action: description" template is a good place to start:
 
-## Getting Started And Contributing
+- "add: readme updates"
+- "fix: date formatting on events"
+- "add: student type interface"
 
-Visit [getting-started.md](docs/getting-started.md) on info for how to set up this repo.
+## database connection
 
-Visit [contributing.md](docs/contributing.md) on info for how to contribute to this repo.
+when we work on connecting our frontend to our backend via API endpoints, we'll want to start working with real data -- that data has to live somewhere. enter: MongoDB! MongoDB is a friendly, commonly-used database service we'll use during bootcamp. it is something we'll configure access to in milestone #2. if they don't cover it in bootcamp, I (your humble tech lead) will help you!
+
+### IMPORTANT!!!
+
+when you connect to the database, you will generate an API key, which we will refer to here as a MONGO_URI. this will go in your local repo in a .env folder. it is absolutely ESSENTIAL that this MONGO_URI does not get pushed to the remote repository (the remote repository is the one you're looking at now -- the collective and public one). to do this, ensure you have a .gitignore in your root repository, and that the .gitignore contains '.env'. if you clone the repo correctly, this should already be configured, but please double check before pushing anything.
+
+## using the project board
+
+we'll track our progress on the fancy-shmancy Github Project Board (woohoo!!! isn't that so exciting!) you can find it at "projects" along the top menu. it contains 5 task stages:
+
+- backlog: tasks we have planned but not started
+- in progress: this task is being worked on!
+- in review: tech lead is reviewing your code!
+- done: merged into the main repo = changes accepted and applied
+
+## comments
+
+commenting your code is not aaalllways necessary, but can be very helpful -- especially when you know others will read your code (which is usually the case). there are many different ways to write both good and bad code comments. [here's](https://stackoverflow.blog/2021/12/23/best-practices-for-writing-code-comments/) a helpful starter guide.
+
+## for reference
+
+in case you want to review any part of bootcamp, [here's](https://h4i.notion.site/2026-Developer-Bootcamp-3ae197abf07b80b1bfdce3009e3aa098?p=3ae197abf07b80d39037d3569e20e668&pm=s) the notion site. it may be helpful!
+
+and don't forget,
+
+# ASK QUESTIONS!
+
+it is (never, not in a million years) your job to know how to do everything already. this is, by nature, a learning experience. maybe you have a bunch of web-dev experience and can get through all your project tasks in a breeze, but that's not the expectation. the expectation is that you _make an effort_, even (especially!) when you don't know how to do something. the willingness to be uncomfortable, ask questions, and admit when you don't know something will make you both a better team member and a better developer :) so trust me, and don't be shy about questions. i can only answer because i once had the same question :)

components.json

@@ -0,0 +1,25 @@
+{
+  "$schema": "https://ui.shadcn.com/schema.json",
+  "style": "base-nova",
+  "rsc": true,
+  "tsx": true,
+  "tailwind": {
+    "config": "",
+    "css": "src/app/globals.css",
+    "baseColor": "neutral",
+    "cssVariables": true,
+    "prefix": ""
+  },
+  "iconLibrary": "lucide",
+  "rtl": false,
+  "aliases": {
+    "components": "@/components",
+    "utils": "@/lib/utils",
+    "ui": "@/components/ui",
+    "lib": "@/lib",
+    "hooks": "@/hooks"
+  },
+  "menuColor": "default",
+  "menuAccent": "subtle",
+  "registries": {}
+}