Monday, 10:00 · Marguerite Fontaine, Writer
The collection, look by look
Each look is an entry: a name, the pieces, the photos, a line of text. The collection page lists them in the order of the show.
Models & blocks →Use case · Fashion house
Many people have a say. Nothing goes live until the right one approves it.
Maison Vérane shows a collection twice a year. The copywriter writes it, translators carry it into three languages, the brand director reads every word, and legal wants a look at the campaign. The site goes live the hour the show starts. Here’s the week before.
A week at the house
Collection week
A copywriter, two translators, a brand director, and a show on Friday. Pick a day.
Tuesday, 15:20 · Céleste Armand, Reviewer
Notes on the field
Céleste leaves a note on the third look’s text. Legal answers in the same thread. Nobody hunts for it in an email.
Collaboration →Wednesday, 11:45 · Marguerite Fontaine, Writer
Three languages, field by field
The translators work beside the English. What’s missing is marked, and the English stays as it was.
Multilingual →Thursday, 17:00 · Céleste Armand, Reviewer
Approved, word by word
Céleste sees the words that changed, next to what’s live. She approves, or sends it back with a note.
Reviews →Friday, 20:00 · Louise Gagnon, Admin
Live as the show starts
The collection was scheduled for eight. It goes live with the first look, and the site rebuilds.
Publishing →An example week. Every step is something the Studio does today.
Try it
Move the campaign text through it
Press the buttons as each person would: the copywriter asks, the brand director approves or sends it back.
Autumn collection: the campaign page
Draft
In review
Live
Unpublished
Each move is a commit with the name of whoever made it, and the History shows them all.
Many hands
Who does what at the house
Roles are set per project. Pick one to see the Studio as they do, with reviews on.
- Write and edit entries and pages
- Edit translations
- Ask for review
- Approve, which publishes, or send back, not for the writer role
- Publish without a review, not for the writer role
- Delete for good from the bins, not for the writer role
- Change models, blocks and forms, not for the writer role
- Change settings and people, not for the writer role
- Make API channels, keys and webhooks, not for the writer role
- Change the plan and the card, not for the writer role
I write the collection pages and the campaign text. When I’m done, I ask Céleste.
I write the French and Italian. The English stays as the copywriter left it.
I’m the brand director. I read exactly what changed, then approve it, which publishes, or send it back with a note.
I’m the house’s head of content. I publish without waiting for a review, and keep the media and menus in order.
I’m at the agency. I shape the models, blocks and forms the site is built from.
I’m at the agency too. I run the project: its settings and the team, and I can publish a fix at once.
I’m the agency’s developer: channels, keys and the webhook that rebuilds the site.
I’m in the house’s finance team. I see the plan, the card and the invoices. Nobody else does.
What it takes
The parts that do the work
Reviews
Nothing live unread
With reviews on, every change waits for a reviewer who sees exactly what changed.
- Sent back with a note
- Content leads can still fix at once
Notes
Questions on the field
Notes are pinned to the field they’re about, answered in a thread, resolved when they’re done.
- Every author kept
- No email chain to find later
Languages
A translator role
Translators edit the other languages and nothing else. The original stays as the writer left it.
- Missing fields marked
- An address in each language
Show time
Live at the hour
Pick the day and time. Moteur publishes what’s saved at that moment. A writer’s publish waits for an approval first.
- A webhook tells your host
- Taking offline works the same way
POST /projects/maison-verane/schedules
{ "resourceType": "page", "resourceId": "autumn-collection", "action": "publish", "scheduledAt": "2026-03-06T19:00:00Z" }
Questions agencies ask
A reader asksCan a page need two approvals, the brand director’s and legal’s?
MoteurNot yet. One reviewer’s approval publishes. Today, legal leaves a note on the field and the brand director approves once it’s resolved. The history shows who did what.
A reader asksHow many people can work on one site?
MoteurUp to 20 on Extra, each with a role in this project only. The house’s finance team can hold billing and see nothing else.
A reader asksCan we see who changed a word last season?
MoteurYes. Every save is a commit with a name on it. Any version comes back as a new save.
Build the first one this week.
A free project costs nothing, and its files are yours from the first save.