The editor
StretchDocs documents open in a writable editor — a full writing surface, not a read-only viewer. You draft, format, and save directly in the browser, and StretchDocs handles versioning and word counts for you.
Open and write
- Click a document in the library to open it in the editor.
- Start typing. The editor supports standard structure — headings, paragraphs, lists, and quotes.
- Use headings to break long documents into sections; they also help Document Intelligence score your structure and readability well.
- The word count updates automatically as you write.
How saving and versioning work
StretchDocs commits your content and assigns a version each time content is saved. Practically:
- Every content save increments the version number, so the history reflects real editing milestones.
- The word count and last saved by fields update on each save.
- The document's updated timestamp refreshes, which floats it to the top of the recently-updated library view.
Because each save is versioned, you can always look back at how a document evolved (see Version History and Snapshots).
Editing metadata while you write
You don't have to leave the editor to change governance fields. From the document header you can update the title, status, folder, owner, type, and a short summary. These are metadata edits — they update the document record without rewriting your content.
Content safety
StretchDocs sanitizes document content on save. Active or unsafe markup — scripts, embedded frames, inline event handlers, and javascript: links — is stripped automatically. This keeps documents safe to open and share across your organization without exposing anyone to injected code. Your visible text, headings, lists, and formatting are preserved; only unsafe elements are removed.
Collaborating with others
StretchDocs is built for teams:
- Real-time co-editing. More than one person can work in the same document at once, with live presence showing who else is in the room. See Real-Time Collaboration and Presence.
- Comments and suggestions. Reviewers can anchor comments to specific text and propose tracked changes you accept or reject. See Comments, Suggestions, and the Review Workflow.
- Status hand-offs. Move a document to Review to signal it's ready for feedback, then to Published when it's approved.
A realistic example
Dev writes an onboarding guide. He opens a blank document, adds an H1 title and three H2 sections, and drafts under each. Each time he pauses, StretchDocs saves and bumps the version. He pastes a snippet from an email that happens to contain tracking markup — StretchDocs strips the unsafe parts and keeps the text. When the draft is solid, he sets the status to Review and pings his manager, who joins the document live and starts leaving suggestions.
Tips
- Lead with headings. A document with clear H1/H2 structure reads better and scores higher in Document Intelligence.
- Keep sentences moderate (roughly 5–25 words) — the analysis engine flags very long sentences as harder to read.
- Capture a snapshot before a major rewrite so you have a clean restore point.
- Move to Review rather than emailing a draft around — feedback stays attached to the document.
Troubleshooting
My save didn't stick / I got a save error. Another edit may have landed between your open and your save. Reload to pull the latest version, then reapply your change. See Troubleshooting for save conflicts.
Some pasted formatting disappeared. Unsafe markup (scripts, iframes, event handlers) is removed on save by design. Re-add the content as plain text or standard formatting.
The word count looks off. Word count is computed from the document's text on save; very short edits or pasted markup can shift it. Save again to refresh it.
Was this helpful?
Help us improve this article
Use these controls to share whether this answer solved the issue. Feedback helps prioritize updates to StretchSuite Support.

