Skip to content

Latest commit

 

History

History
24 lines (17 loc) · 1.84 KB

devlog.md

File metadata and controls

24 lines (17 loc) · 1.84 KB

Development log

All of the steps I'm taking to build this app, from start to finish.

Day 1: Concept and tech

It's Friday 5/13, and we have decided to come up with a new example app.

We wrote down all of the stuff we want to demonstrate about building an app with Apollo.

I've also made a list of technology choices:

  • Apollo server - to put a nice unified API on top of our GitHub and local data
  • Apollo client - to load that data declaratively into our UI
  • React - it's a great way to build UIs, and has the best integration with Apollo and Redux
  • React router - it seems to be the most popular React router today, and has some great hooks and techniques for SSR. It seems like James Baxley has had some success with implementing this stuff already with React Router.
  • Webpack - the Meteor build system is by far the most convenient, but comes with a dependency on mongo, its own account system, etc. Since we want to learn how Apollo works without all of these things, we're going to not use it even though it would reduce the complexity of the code.
  • Babel - to compile our server code.
  • Redux - to manage client side data, perhaps we can also use Redux Form to manage the submission form, but we'll see when we get there.
  • Passport.js for login - this seems to be the most common login solution for Express/Node, and has a great GitHub login solution. Jonas has already written a tutorial for using that with GraphQL.
  • SQL for local data - We'll use SQLite for dev, and Postgres for production. TBD - should we use Sequelize or some other ORM? Or just Knex for query building?
  • Bootstrap for styling - I already know how to use it, and I don't want the styling to be the focus of the app. Let's keep it as simple as possible.

I drew a quick mockup of the desired UI. It's quite simple, and should be easy to implement in bootstrap.