jessecanderson / decenttea Goto Github PK

View Code? Open in Web Editor NEW

0.0 2.0 0.0 631 KB

Home of Decent Tea. The web app where you can review restaurants tea, and keep of list of your favorite ones.

Home Page: https://www.decenttea.com

License: MIT License

TypeScript 94.15% JavaScript 1.39% CSS 4.46%

decenttea's Introduction

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying pages/index.tsx. The page auto-updates as you edit the file.

API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in pages/api/hello.ts.

The pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.

Learn More

To learn more about Next.js, take a look at the following resources:

Next.js Documentation - learn about Next.js features and API.
Learn Next.js - an interactive Next.js tutorial.

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.

decenttea's People

Contributors

Watchers

decenttea's Issues

Finish create restaurant component

Finish the basics of the create restaurant component.

Adding lists of restaurants for a user

Connect the user to an array of lists. Each list will be an array of restaurants that they want to have in there.

Make sure we have API's for adding a list to a user and then updating that list with restaurants.

Create UI for List management

Allows a user to create new lists and add restaurants to that list.

Updating the map to allow a logged in user to add a restaurant directly to a list.

Update Restaurant Endpoints

Right now, we can query the DB for all stored restaurants or just by a specific ID restaurant. Need to update it to handle creation better.

Update NextJS to 12.3.0 and move everything to `app` directory

With the new 12.3 release, NextJS has started moving routing from the pages folder to a new app directory. This will migrate NextJS to the latest 12.3 and then move the pages and API routes into the app folder.

Create Users

We have endpoints for some of the restaurant stuff, but now need to work on getting a user in there and allowing them to login.

Update Home Page

Create home page for Decent Tea. Basic layout and info on the app.

Next update

Add security validation to the API endpoints

Right now, the API endpoints are just handling the CRUD operations but need to be secured so people don't try and muck with them.

Create and implement an auth plan for the endpoints. Either a JWT or some kind of API key schema for devs to hit them in Postman but also Next to auth to them (however that works).

Fix Next-Auth integrations

In one of the next updates, next-auth broke and needs to be refactored/fixed. Just to provide some kind of auth for users.

Add UI for seeing reviews for Restaurants

Make sure we can see all the wonderful reviews of tea at each restaurant when selecting that restaurant.

Create Add Restaurant component

Create a component that will add a restaurant to the DB.

Add Google AdSense to monetize app

This is a first step to make something that isn't obtrusive to the user but still allow it to start funding itself.

Add in Google AdSense and a small banner ad or advert somewhere that isn't in the way of functionality.

Connect create restaurant component to API call

Make sure that when submitting a restaurant that it actually sends to the API and saves the restaurant.

Update Search for local DB

This was originally created to query the places API from Google. Now that it is using the local DB, we need to make sure we are returning the restaurant correctly, validating any lat/long that may need to be there, and place that on the map. This will update the endpoint as well to make sure we are getting the correct lat/long if one is not already there and storing it for next time.