Make tech stack decisions

lacyjpr / media

1 stars 0 forks source link

Make tech stack decisions #15

Closed matty22 closed 6 years ago

matty22 commented 6 years ago

I started listing some things we know for sure/discussed earlier today. Lots of unknowns here still:

Client
1. FE JS Framework: React
2. SCSS with BEM
3. Testing: Jest? Enzyme
4. Bundler/Build tool: CRA/Webpack
5. WYSIWYG editor: SlateJS
Server
1. Express
2. Node
3. Other needs TBD
Database
1. PostgreSQL
2. pg
3. Other needs TBD
Hosting
1. Heroku
Miscellaneous
1. CI/CD: Travis CI
2. Authentication: Passport.js
3. Diagramming: Draw.io

lacyjpr commented 6 years ago

CRA vs Kornil's Simple React App

lacyjpr commented 6 years ago

Hosting? https://devcenter.heroku.com/categories/heroku-postgres

matty22 commented 6 years ago

I've never used AWS or Azure. Might be cool to consider using one of those for hosting to learn how to do it.

P1xt commented 6 years ago

You might also consider Travis CI for auto-deploy no matter where you eventually decide to host. Having it run your tests and lints and whatnot then just deploy when you push/merge to master is a massive help in the development process, not just because you just merge-gogettea, also because it ensures that only good builds get deployed.

lacyjpr commented 6 years ago

Cookies vs JWTs

lacyjpr commented 6 years ago

Prettier?

matty22 commented 6 years ago

Some sort of diagramming tool to keep a flowchart of database relationships in visual form?

lacyjpr commented 6 years ago

SCSS or CSS

matty22 commented 6 years ago

On the topic of CSS:

CSS modules
CSS in JS
Trying to keep namespaced CSS organized