Getting started
CloudSource CMS documentation
Everything from deciding whether to buy, through to the API call your storefront makes in production.
How a headless CMS works
CloudSource separates your content from how it is displayed. Your team manages content in the admin panel; your storefront, app or in-store screen fetches it as JSON and renders it however it likes.
For a retailer that means one place to manage product copy, imagery, category pages and campaign content — and any number of places to display it.
You define the shape
Create models such as Product, Category or Campaign, with exactly the fields you need.
Your team fills it in
Merchandisers write copy, upload imagery and schedule when it goes live.
Your storefront reads it
One HTTP request returns published content as JSON, ready to render.
Admin panel API Your storefront
| | |
| define models | |
| upload imagery | |
| write copy | |
| hit "Publish" ──▶| content goes live |
| |◀── GET /api/content ───────|
| |─── JSON response ─────────▶|
| | | renders page
Set-up path
Working through these in order takes a typical team an afternoon, not counting the frontend work.
Coming from another CMS?
If you are on Contentful, you do not need to rebuild anything by hand. Export your space as JSON and import it in one upload — models, assets and entries all come across.