Update Customer GraphQL Documentation to Include Mutations

[erikmarr]

This PR is a:

• New topic
• Content update
• Content fix or rewrite
• Bug fix or improvement

Summary

When this pull request is merged, it will fix issue #3338.

This PR updates the graphql documentation to include the new mutations.

Additional information

List all affected URLs

• https://devdocs.magento.com/guides/v2.3/graphql/reference/customer.html

[keharper]

Some big-picture things before I start reviewing at the sentence level.

• Create a head2 called Parameters and move all the parameter tables under that.
• Find a way to consolidate the Customer tables. That's too much duplicate info.
• Create subsections under Mutations: Manage customers, manage customer addresses, manage customer tokens
• Your example usage statements are H2s. They should be a lower heading than what's used for the mutation name.

[erikmarr]

@keharper I have made several changes, but am struggling with some of these suggestions. I feel like we should keep the queries and mutations as separate tables/sections since they cannot be used together in the same graphql call (at least that is my understanding). I propose a structure like:

Queries
-structure of call
-attribute tables
-example

Mutations
-structure of call
-attribute tables
-Manage customers
--Example(s)
-Manage customer address
--Example(s)
-Manage customer token
--Example(s)

Here's a new build with the above proposed structure:
https://devdocs.magedevteam.com/em_magento-graphql150/guides/v2.3/graphql/reference/customer.html

[erikmarr]

@keharper, I just posted a new build for review:
https://devdocs.magedevteam.com/em_magento-graphql150/guides/v2.3/graphql/reference/customer.html

[erikmarr]

closing as this is resolved in the following PR: #3818

[ghost]

Hi @erikmarr, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.