A multi-product retailer · Retail
Content operations on Sanity with a separate dataset for each product
Social content, brand guidelines and the publishing queue are managed in Sanity, with a dataset per product.
A retailer selling different products keeps its content in sync with Sanity: a separate dataset for each product, with social media content, brand guidelines and a publishing queue managed there.
What it solves
The problem, and what runs now.
The problem: Content for different products gets mixed together in one place.
What runs now: Each product has its own Sanity dataset, so its content stays separate.
The problem: Brand guidelines kept away from the content are easy to overlook.
What runs now: Brand guidelines are managed in Sanity, alongside the content.
The problem: Social media content spread across tools is hard to keep in sync.
What runs now: Social media content and the publishing queue are both managed in Sanity.
How it runs
Step through the workflow.
Product datasets
A separate Sanity dataset for each product
Each product the retailer sells has its own Sanity dataset, so a product's content stays with that product.
Brand guidelines
Brand guidelines managed in Sanity
Brand guidelines are managed in Sanity, next to the content they apply to.
Social content
Social media content managed in Sanity
Social media content is managed in Sanity, under the product it belongs to.
Publishing queue
A publishing queue in Sanity
Content waiting to go out sits in a publishing queue in Sanity.
In sync
Content kept in sync
With the datasets, guidelines, social content and queue all in Sanity, the content stays in sync.
What we built
Services
- Content Operations
- Publishing Queue
Stack
- Sanity