Reviews & publishing

Nothing goes live until someone has read it.

Turn on reviews, and every change waits for a reviewer who sees exactly what changed. Or leave them off and publish at once. Either way, each step is a commit with a name on it.

Marguerite, a writer, changes the English headline “The Factory That Never Sleeps” to “…Never Stops” and asks for review. Then Céleste, the reviewer, is introduced. She opens the review, sees the one word that changed, and approves it, which publishes it.

Marguerite asks for review. Céleste sees the one word that changed, and approves.

Try it

Move an article through it

Press the buttons as each person would. Then turn reviews off, and see how a smaller team works.

L'Originale: An Obituary

Draft

    Each move is a commit with the name of whoever made it, and the History shows them all.

    Around the workflow

    Around the workflow

    What makes reviews quick enough that nobody skips them.

    • Diff

      See exactly what changed

      A review shows the fields that changed, word by word, next to the live version.

      • Everything else, said to be the same
      • Machine-written fields marked
    • Notes

      Sent back, with a note

      A reviewer can send work back with a note. The entry returns to draft, and the note stays with it.

      • The writer picks it up from there
      • Questions stay with the content
    • Admins

      The fix that can’t wait

      With reviews on, content leads and admins can still publish at once.

      • A commit with their name
      • For typos at 11 pm
    • Live

      Edit what’s live, safely

      Edit a live entry without touching the live version: the changes wait until someone publishes them.

      • “Publish changes” when ready
      • The list counts edits not published
    • Agents

      Agents only ask

      An agent can ask for a review, never approve. What it wrote stays marked until a person reads it.

      • Both names on every change
      • Approving is a person’s call
    • Webhooks

      Your site hears about it

      Publishing and unpublishing send a signed webhook, so your host rebuilds at once.

      • Signed, so you know it’s us
      • Retried for two hours

    Reviews

    Everything waiting, in one place

    The Reviews page lists what’s waiting, who asked, and when, for everyone who can approve.

    • Waiting, approved and sent back
    • Who asked, and for whom
    The Reviews page in the Studio: entries waiting for review, with who asked and when.The Reviews page in the Studio: entries waiting for review, with who asked and when.
    The Moteur Journal’s Reviews page.

    Questions about reviews

    A small team asksDo we have to use reviews?

    MoteurNo. They’re off until an admin turns them on, project by project. Without them, anyone who writes can publish.

    A tech lead asksCan a content lead skip the review?

    MoteurYes. With reviews on, content leads and admins can still publish at once, for the fix that can’t wait. It’s a commit with their name, like everything else.

    A reviewer asksWhat exactly do I see?

    MoteurThe fields that changed, word by word, next to what’s live, with what a machine wrote marked as such.

    A writer asksWhat happens when it’s sent back?

    MoteurIt goes back to draft with the reviewer’s note on it, and you pick it up from there.

    An editor asksCan we schedule a publish?

    MoteurYes. Pick a day and time on the entry or page, and Moteur publishes what’s saved at that moment. Taking something offline works the same way. With reviews on, a writer’s publish waits for an approval first.

    An editor asksWhat if someone deletes the wrong page?

    MoteurIt goes to the project’s bin, with who deleted it and when. Anyone who writes can take it back out. It comes back as a draft, so going live again goes through review like anything else. Only a content lead or an admin deletes it for good.

    Turn on reviews in your first project.

    Invite a writer and a reviewer, and send something through.