On Tue, Jun 18, 2019 at 11:10 AM Stephen Coady <scoady@redhat.com> wrote: Hi John - just to add to what Paul has said above. My general thoughts are: 1. From a docs perspective, we should probably have a very natural flow where they build from nothing (the 00 example Paul mentions) to a little less basic where both queries and mutations are present in both the server-side schema and the client pointing at this server. I think this could be one example with annotations pointing out the building blocks of types, queries, mutations etc. 2. This kind of naturally answers your next question of should they be done together. I think they probably should. The first part of the docs after the basic hello world example could be explaining the schema. The queries and then the mutations would naturally flow from here. 3. I think where the client side code lives is probably a bigger discussion. I'm not sure putting this code in the sdk is the best choice. 4. Do we know why we are using webpack for the examples? Taking a look at the current docs example you have listed it seems like overkill to me. I don't think we need to mention builds and the build sizes as they are irrelevant. I'm also not sure needing to open a browser just to see the console is a good getting started experience. It might be better to consider using ionic to serve a basic app - or even consider just running the client from the command line. Stephen |