-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tech Stack #15
Comments
Here are some suggestions to look into:
|
Current - react, node, next.js (goes on top of react/node to make things easier) express/mongo could be added into existing code easily - essentially you would override next.js routing, takes maybe 15 lines of new code (we couldn't use static hosting but that's a tradeoff of server logic) If you ever want to do accounts/auth, I'd recommend auth0, which can be used standalone or with passport - whichever works for you |
Will add Mongo / Express into current stack. Incremental changes to website will be made. Next task: See what changes need to be done to the website. One person will take lead on making the changes |
Example of adding express into next.js/react/node Mongo (I recommend mongoose in particular) is done as normal |
Learn about which tech stack you would like to use before our next meeting. Next Monday at 5:10pm
The text was updated successfully, but these errors were encountered: