On Mon, Jun 17, 2019 at 12:25 PM John Stafford <jstaffor@redhat.com> wrote: Hi, I'm wanting to solicit your thoughts on the current situation with regard to the Data Sync docs work. For the "getting started" data sync user story, my mind is occupied with this following and I would like your thoughts on some specifics around this: 1) Getting started with a Data Sync Server locally | Passed tests 2) Adding a data scheme to the data sync server | Passed tests 3) Querying a Data Sync Server using a Data Sync Client (in a local context) | Passed tests 4) Working with Data Sync mutations (in a local context) | Ongoing 5) Deploying a Data Sync server on OpenShift (Local data-sync-client querying the data-sync-server on Openshift) | Passed tests 6) Incorporating Data Sync client into a mobile app (Mobile App data-sync-client querying the data-sync-server on Openshift) | Support requested. Specifics: 1) As I was working through the above, it became apparent to me that I needed a (1) Data Sync Server and a (2) Data Sync Client - two separate "software applications". I expect this is a natural setup for a developer - what are your thoughts in general on this? For example, do you think it makes sense to incorporate the work created for "2) Adding a data scheme to the data sync server" and "3) Querying a Data Sync Server using a Data Sync Client" into the Data Sync Server? 1.1) Note that the data sync client is a project in my repo, this is not going to work for Limited Availability/ GA / etc. Do you think Eng can create a similar repo and maintain it (I'm assuming this is what QE would use to test against). I think it would be great to reference it in our docs - it would be awesome from a Customers POV! — Or, build an example into https://github.com/aerogear/aerogear-js-sdk/tree/master/packages/sync that works with an instance of https://github.com/aerogear/voyager-server. — Or, ... 1.2) The data sync client I started with is based on a default "webpack" project that then incorporated "@aerogear/voyager-client". In terms of incorporating this into an Angular/Ionic app - is this a relatively simple piece of work do you know? 2) Do you think it makes sense to keep "queries" and "mutations" in the one code snippet example, or, keep them separate? To help answer this, put yourself in the Customers shoes - as a Customer, would you want to use only "queries" and only "mutations", or, would you want to use both together in the one document? Regards, John |