The doc is the meeting.
Writers, editors, reviewers, and the AI all work in the same document. The same one that becomes the live WordPress post. Cursor presence, anchored comments, one source of truth.
Three big things land this quarter. One of them is finally the publishing queue v2 we promised in May. The other two are smaller, but they sharpen the editor in ways our writers have been asking for.
We made a deliberate choice to ship the queue first even though it depends on a backend migration, because every other improvement assumes it.
Most content reviews happen in the wrong tool.
A writer drafts in Notion. The editor leaves comments in Google Docs. Stakeholders weigh in via Slack threads. The final post is rebuilt by hand in WordPress, and a typo from version four somehow makes it to publish.
When the review surface isn’t the publish surface, every step is a translation. Translations leak.
Karyla puts every actor (writers, editors, the AI, the WordPress post) in the same room.
How it works.
04 stepsOpen together
Anyone with access opens the same doc. Cursors and changes appear in real time.
Edit in place
Writers write. Editors revise. Comments land on the selected text, not the whole doc.
AI alongside the team
AI suggestions show up inline next to human edits, with the same accept and reject controls.
Ship it
Publish to WordPress from the same doc. The doc becomes the post.
Under the hood.
See who’s where, what they’re doing.
Live cursors with names. Selection highlights. You can see what your editor is reviewing without asking, and they can see what you’re writing without interrupting.
- Live cursors with name and color
- Selection sharing. See what someone is reading.
- Active and idle indicators
Comments anchored to text, not paragraphs.
Select a phrase, leave a note. The comment lives with that selection. Resolve, reply, mention. All where the text is.
- Threaded replies and resolve / reopen
- Mentions tied to your team members
- Reviews stay scoped to the selection that started them
AI suggestions with reasons attached.
Karyla’s suggestions appear inline alongside human edits. Each one has a short reason explaining why. Accept or reject just like you would with a colleague’s edit.
- Per-suggestion accept or reject
- Reason attached to every suggestion
- Original text stays until you accept
How we compare.
Common questions.
Stop arguing about which doc is the latest.
Bring your team into one room. Real-time editing, anchored comments, AI alongside the team. Ship from the same doc you wrote in.