By default, Apollo Server and Apollo Client take care of most aspects of client awareness automatically, with the requirements being:
* Using recent versions of Apollo Server and Apollo Client which support client awareness automatically.
* The `name` and `version` be set on the `ApolloClient` constructor.
As currently written, the variables used in this _Advanced setup_ section have caused some to believe that those are the headers that should be used, whereas they were merely suggestions. The _Setup_ section above should still be observed for most cases and I hope the additional clarity in this re-wording will help avoid future confusion.
An "application programming interface" need not be capitalized in its full form, but I believe API should remain capitalized.
With all due respect to SCUBA, I'm not willing to let every form initialism land in the dictionary in lower-case.
* Remove .DS_Store
* Initial Client Awareness Docs
* Reorg images and write some content
Makes the intro a bit smoother and builds up the meat of the article
with some more screenshots
remove you
* Include client awareness in sidebar
* Fix code highlighting
* Add new before ApolloLink
* Fix some typos
* Reorganize the client-awareness documentation
Overview -> setup -> use cases -> advanced setup
