User Story: Start Editing Contents
As an editor I want to open and edit existing content so that I can update, or improve it.
✅ Acceptance criteria
The user can click in any place and start typing or editing.
The user can modify text, images, or formatting.
The user can publish any time with an Publish button always available even if nothing changed.
The system confirms when changes are successfully published.
The system shows autosave every time the user changes something.
The system shows you if another user publishes your document at the same time to review versions.
Save vs publish — this is the key tension. Right now the flow forces a binary: publish or discard. But users naturally want a third state: "I'm done for now, save my draft, I'll publish later."
In a multi-user context, Discard isn't really "throw away my work" — it's closer to "revert to the last published version", which is a much more meaningful and specific action. That's a different mental model entirely.
User lands in a document
User can click in any place and start typing or editing.
Users gets versions conflict notification
User reviews versions
For future considerations:
The system shows you if another user is joined the document you are editing.
The system shows you if another user is editing your document at the same time.
🪜 Basic flow
User navigates to the content.
User does click in any area to start editing and the text cursor appears with the block in soft green.
User makes changes.
User clicks Publish.
System updates the content and shows confirmation.
Another user is working on the document creating a new version, user gets notification to review or dismiss.
⚠️ Edge Cases
User lacks permission to edit → Do not show "Publish" button
User lacks permission to edit → Do not show "New" button
User lacks permission to edit → Options in 3 dots button list will vary
Network error during publishing → show retry option.
Conflicting edits (multi-user) → prompt to review versions, publishing or dismissing.
🟠 UI considerations:
Improve buttons contrast color, in this design screen a propose an updated version of Primary, Secondary and Subtle button.
Update the autosave text to be always visible when document has a cover photo.
User Story: Explore contextual document options
As an editor I want to explore document contextual options so that I can explore relevant actions related to the document.
✅ Acceptance criteria
The user can click on the 3 dots button for doc. options, available next to Publish button.
The user can see "Versions history"→ A versions history will open on the right side.
The user can edit "Document Settings" → Edit or add cover, change publication date, ... will open on the right side (by now).
The user can "Share link" → Creating a link that can be shared by pasting it. What is shared is the latest published version.
The user can "Duplicate document"→ It opens the duplicated document right away to start editing.
The user can "Export document"→ It exports a MD and PDF version.
The user can see "Child documents"→ All child documents of this document will be shown (what we called directory today, change name, is too technical)
The user can "Delete a document"→ The document will be deleted with a warning modal, "Are you sure you want to delete this document?" Delete (red) Cancel (secondary).
The user can create a "Document Branch" (consider if this is necessary if it is the same as duplicating)
🪜 Basic flow
User clicks the 3 dots button
A dialog opens bellow the button with a list of option
User selects one of the options of their interest
User closes the dialog by clicking outside in desktop or in the X icon in mobile.
⚠️ Edge Cases
User lacks permission to edit → Options in 3 dots button will vary just showing:
Share link
Export document
Draft / never published — Share link should be greyed out or not shown since there's no public URL yet.
Doc is already a branch: branching a branch is probably not allowed. If document is already a branch, option could be replaced by "View source document"
Doc has no children: Shows empty state
🟠 UI considerations:
Update copy as in design for more clarity of what the actions are, ie: Document version -> Versions history
Directory -> Child documents
Update icons as in design for more clarity of what actions are.
Update order of the actions by priority and group with deleting always at the end.
User Story: Modify text, images, or formatting.
Do you like what you are reading?. Subscribe to receive updates.
Unsubscribe anytime