The goal is simple: let AI hunt through documentation topics, suggest edits to the first post, and let a docs maintainer choose exactly which suggestions to apply.
V1 in one sentence: scan selected docs topics, attach reviewable suggestions to the first post, show a small indicator on the topic, and let docs maintainers selectively apply accepted suggestions as a normal post revision.
The centerpiece
This is the product: a review screen with before/after diffs, one short reason per change, and a single apply action. Everything else exists to feed this screen.
Primary review screen
Review suggested edits [pending]
How to configure S3 backups
first post · base revision 12 · 3 changes
------------------------------------------------------------
Change 1 [substantive]
Reason: Add the missing warning to verify restores before
relying on backups.
Before After
------------------------------ ------------------------------
Enable backups and set your Enable backups and set your
bucket credentials. bucket credentials.
Before relying on backups,
run a restore test and verify
the archive can actually be
read.
[Accept] [Reject]
------------------------------------------------------------
Change 2 [small]
Reason: Reorder the steps so verification comes before
"you are done".
Before After
------------------------------ ------------------------------
1. Enter credentials 1. Enter credentials
2. Save changes 2. Save changes
3. You are done 3. Run a test backup
and verify it completes
4. You are done
[Accept] [Reject]
------------------------------------------------------------
Sidebar
Accepted: 2
Rejected: 1
Pending: 0
[Apply accepted changes]
What matters here:
- each change stands alone
- each change gets one short reason
- maintainers accept or reject individually
- apply only touches accepted changes
- result becomes a normal revision
Entry point
Topic list
Documentation
How to configure S3 backups [3 edits]
Using object storage for uploads [1 edit]
Backups FAQ
That badge is enough for v1.
Topic page
[Review suggested edits]
That button only appears for the docs maintainer group when suggestions exist.
Secondary states
No suggestions
No badge in topic list.
No review button on topic page.
Stale
This suggestion is stale.
The first post changed after suggestions were generated.
[Regenerate] [Dismiss]
Apply is disabled.
Applied
Suggestions are gone.
The topic now just has an ordinary revision in post history.
What stays in v1
- first post only
- selected categories and tags only
- docs maintainer group reviews and applies
- small fixes and substantive changes both allowed
- one short reason per change
- accept or reject each change
- accepted changes become a normal revision
- stale detection before apply
What gets cut
- titles
- replies
- public review
- bot replies in-topic
- automatic apply
- comments on each suggestion
- rebasing
- fact checking pipeline
- big settings surfaces
Minimal data shape
| Thing | Needs |
|---|---|
| Suggestion | topic id, post id, base revision, status, created at |
| Change | before text, after text, reason text, pending/accepted/rejected |
That is enough for v1. The reason can just be text. The status can just be simple. The plugin does not need a giant ontology to do one useful job.
Success
- Maintainers can find docs topics with suggested edits.
- The review screen is obvious at a glance.
- People can accept only the parts they want.
- The result lands as a normal first-post revision.
Final cut: v1 should feel like a disciplined review tool for docs maintainers. If it starts looking like an AI publishing platform, something has gone wrong.