Docs: creating products, categories, orders through GraphQL.

[djkato]

Problem

The current docs only describe consuming the API as a storefront, but there's no documentation or guidelines I could find that describe creating products, categories, orders, customers etc. Currently I have to create products through dashboard and watch the GraphQL queries, then make the assumption that that's how it's meant to be done.

It would be nice to split the doc into consuming vs mutating or something to make it clearer.

From what I reverse-engineered from the dashboard, the correct way is to:

• productCreate: generic info
• productChannelListingUpdate: to set it's channel and make it public(?)
• variantCreate: to create a mandatory variant so it can have a sku and price
• productVariantChannelListingUpdate: To set the price.

Nowhere is there explained why prices are only available inside variants. This feels quite unintuitive to me, as in my mind I only need to create variants if there are variations. A guide describing why this is the case would be nice, as I didn't see this inside the cunsumption doc (maybe I missed it?).

And ofc a guide that describes the rest of the common mutations a user might have to do, like creating a Category, Orders, Accounts etc.

I'm currently writing a database migration, 'cause we're moving our store from a proprietary system to Saleor, and I have to keep on testing and reseraching if this is the correct way when there's no info about it public. I still am unsure if the steps above I found are correct.

Thanks, dj

[ashwin1596]

Hi,

I am interested in working on this issue and believe it will help me learn more about the codebase.

Could you please confirm if I can start working on it?

Thank you!

[aniav]

I have moved this issue into the docs repository as it makes more sense here. Since this issue has been created we've improved the structure of docs and it should be easier to create what you are suggesting @djkato. Each section from Core concepts now has an API Guide that covers part of what you ask for.

I guess what you are suggesting is more around a complete guide on how to go from an empty state to a configured shop and we defo want to have something like that.

@ashwin1596 feel free to work on this but try with a draft PR first to check if the direction you'd want to go is going to fit with the current docs structure.