where it all began...

[matthandlersux]

let's start small, and figure out a way to take a few opinions/structures from existing projects we liked, and wrap that up in something that feels like create react app, but has some extra built in functionality. the guiding AC here is:

for the next chief-like project we have, we want to run create-originate-app name-of-company and save ourselves a few weeks of development time by building in a bunch of innocuous and generally agreed upon configuration/functionality

feels like create react app

this means that we have a couple of built in commands, like create-originate-app my-app-name and then cding into that folder you can yarn start. the goal here is to make it easy to start up a new project that most people at originate can be happy and productive on, and we save ourselves a 1-4 weeks of development.

extra built in functionality

...to me, means a couple of opinions that we pull from existing projects (i think: https://github.com/originate/vibecheq is a good one to reference, which has patterns tested with random devs on the dashboard and nps, which were then built into that project).

we should discuss these probably:

• typescript is default
• the project is set up for yarn workspaces, with a frontend/backend/lib workspace, and typescript is set up with --build and references sections appropriately embedded into the sub-project tsconfig.json files
• easy testing infrastructure
• circle config
• heroku deployment set up
• a good readme

additional things that we might want to build in

we should discuss these maybe:

• postgres/knex setup built in?
• frontend/backend env setup
• docker/docker-compose
• dependency injection on the backend
• an opinion on frontend/backend data validation (we use io-ts on vibecheq and it works well)
• separation of logic between service and DOA layer
• frontend
  • router/page management
  • folder structure
  • redux/reducer/state management patterns
  • async/api access patterns
  • grid layout/design patterns
  • storybook/design iteration patterns
• linter configuration
• absolute imports
• a way to tie types and endpoint names (/api/v1/my/endpoint) together between backend/frontend (see the "routes" workspace in vibecheq, which should feel familiar from the dashboard)
• sentry.io integration? other useful integrations?
• mixpanel/segment/GA integration?
• user auth, model, login pages, built in?
• end to end testing configuration available out of the box

food for thought: in general, it feels like in order to solve this, we need to find a good way to make a generic version of CRA with any opinions built in. a "create-create-react-app" if you will. if you solve that, that could be a very cool open source project for us, because we could use it internally, but other consulting companies would probably enjoy creating their specific flavor of CRA too. this isn't to say this should be our goal, because getting something usable for us, first, is the goal.

[hlian]

ticket 1 seems more or less done

to test

• npx github:Originate/create-originate-app test
• cd test
• yarn dev verify localhost:8080 works
  • react-refresh should be present (hot module reloading 2.0)
• git push [github remote] verify that github ci works

i'll do this before tomorrow

• ./vendor/heroku [heroku remote] verify that heroku remote works