@ryanchenkie
Founder @ CourseLift
@ryanchenkie
@ryanchenkie
Repetitive, manual work
No good front end/backend author-time integration
Bespoke, potentially brittle solutions
Unclear how to separate a project into modules
@ryanchenkie
Nearly all technical points have been improved
Adoption has grown and stabilized
@ryanchenkie
The learning loop can be challenging
New GraphQL developers might still be left confused
@ryanchenkie
If we want more developers to try and adopt GraphQL, we need a better way to get them started
@ryanchenkie
Have a way to handle everything that other conventions do without needing think about it
Automatically be informed about the GraphQL schema across the stack
Have the benefits of the client-server relationship that GraphQL gives without needing to think about the mechanics
@ryanchenkie
@ryanchenkie
@ryanchenkie
@ryanchenkie
@ryanchenkie
@ryanchenkie
@ryanchenkie
yarn redwood generate component my-component
@ryanchenkie
yarn redwood generate page my-page
@ryanchenkie
yarn redwood generate layout my-layout
@ryanchenkie
@ryanchenkie
yarn redwood generate sdl my-resource
@ryanchenkie
@ryanchenkie
@ryanchenkie
Founder @ CourseLift