anything I should look out for?

Hey, I assume you have read basics of Prisma and understand how to bootstrap the project (

prisma init

). I would also recommend looking into all the boilerplates (basics and advanced) and try to understand what each file does, at least the idea. Maybe check out a tutorial with a walkthrough and build basic project yourself just to get the taste of your tools. In case you are trying to build a more sophisticated app with advanced logic and more complex datamodel, reading this article is a must. https://blog.graph.cool/graphql-schema-stitching-explained-schema-delegation-4c6caf468405?source=linkShare-9058c3a48f07-1516718405 (read the first part first and follow along with succeeding parts. In the end read this article. You can also ping me and I’ll help you) Usually, I start with datamodel migration. Since this is the only part of our app that is going to stay the same it’s a solid place to scale from. After that I usually look at all the queries my client has used and try making a list of queries, mutations and subscriptions I would like to implement. Using the list I write the app schema and implement the folder structure of my project. In the end I write resolvers for each function, which is usually just modifying existing client queries since they’ve been moved from client to proxy. TIP: try thinking of security when designing the model. Majority of restrictions can be implemented with the right implementation of the model. Hope this helps you 🙂

@matic thanks for that. super helpful. I've already migrated my schema into the datamodel and starting to look to implement all my auth (I'm basing it on the advanced TS boilerplate). looks like I have to reimplement all my custom resolvers as well as the standard queries. As well as the permissioning system looks like it's completely different