RichScripts
Use this tool Jump to inputs and settings
DOCUMENTATION · REVIEW BEFORE PUBLISHING

See what changed.
Approve what goes next.

Compare two documentation snapshots. Review added, changed and removed articles, inspect audit findings, then export the source updates you approve.

Free local workspaceNo account neededNo automatic publishing
Laptop and notebook on a bright desk

1. Upload two snapshots

Use ZIPs to preserve paths. UTF-8 Markdown, HTML and TXT; each snapshot allows 100 docs, 512 KB per doc, 5 MB total and 500 ZIP entries. Matching paths identify articles. Assets are inventoried but excluded from export.

Choose both snapshots or try the example.

Resume a saved review

Restoring replaces the current comparison. Save your draft first. Drafts include both source snapshots, approvals and notes; handle them as private documentation. Saved approvals are local decisions, not verified team sign-off. Original assets are not retained.

Customer questions to address

Import a review JSON exported from Documentation Support Finder. Only questions marked Documentation gap are included. Imports merge by ID; existing notes take priority. These historical references are not a new audit or proof that an update fixes the question.

No gap backlog imported.

The backlog is independent of article approvals. Save it separately before closing; review drafts and approved-source packages do not include it. Mark a question addressed only after verifying the published result.

A practical maintenance cycle

  1. Export source files from your documentation system.
  2. Use the same paths in the proposed snapshot. Rename appears as removal plus addition; approve both deliberately.
  3. Review source changes and findings. Missing uploaded links may exist online; factual accuracy and external links require manual checking.
  4. Export approved changes, apply them through your publishing system and verify the live articles.

What this workspace checks

Source text is compared after line-ending and BOM normalization. Common changed lines are shown using shared prefixes and suffixes; long changes are truncated for preview. This is not a semantic diff. Proposed docs use the Documentation Audit checks for links, headings, duplicates and possible limit conflicts.

Limits and privacy

This tool does not generate articles, verify product facts, crawl public pages, publish updates or connect to help-center services. Files and decisions stay in this tab and disappear when it closes or inputs change. Save a full review draft before leaving, or export approved changes for handover. Images and attachments require a separate publishing workflow. HTML/MDX may contain active content: review original sources in your secure publishing system before publishing.