| .. | ||
| docs | ||
| graphql | ||
| src | ||
| .env.example | ||
| .eslintrc | ||
| .graphqlrc.yml | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| next-env.d.ts | ||
| next.config.js | ||
| package.json | ||
| README.md | ||
| saleor-app.ts | ||
| sentry.client.config.js | ||
| sentry.edge.config.js | ||
| sentry.server.config.js | ||
| tsconfig.json | ||
| vitest.config.ts | ||
CMS
Overview
What is it?
CMS Hub is a Saleor app that exports products from Saleor to several popular CMSes.
Here is a list of currently supported CMSes and their configuration guides:
How does it work?
cmslistens to Saleor product variant events through webhooks.- When an event is triggered, we extract the product data and pass it to the CMS Client.
- CMS Client checks what CMS you picked, transforms the data to the format the CMS expects, and sends it over.
Mapping fields
Currently, the CMS Hub does not support mapping Saleor fields to your CMS fields. Your product model should have the following fields:
- strings fields:
saleor_id,name,product_id,product_name,product_slug, - JSON fileds:
channels.
Known issues
CMS Hub updates product variants in CMS providers on create, update or delete product variant webook events. They are triggered on product variant channel listing added or updated, but they currently don't trigger on deleting channel listing due to the core issue #12247. To make it working on deleting channel listing, you can additionally modify other product variant field e.g. name, so webhook handlers receive the updated channel listings as well.
How to use it?
- Install the application in your Dashboard and open it.
- Go to Providers.
- Add CMS provider instance with proper configuration.
- Go to Channels.
- Turn on provider instances for desired channels.
- Go to Products in Dashboard.
- Add, edit or remove product variant to see it is added, updated or removed in configured CMS provider accordingly.
How can I contribute?
See CONTRIBUTING.md.