Create and edit Context pages
A Context page is a durable explanation: a plan, a decision, a guide, or a summary. Write it for a person who joins the project later. Keep original material in Library. You need Editor or Owner access to create and edit pages.
Write your first page
- Check the workspace, then open Context → New Context page.
- Give the page a clear title, such as Launch plan. A title is one line of up to 256 characters.
- Write a short introduction, then add headings and lists. Type
/for the block menu, or use toolbar controls for headings, links, tables, Citation, and References (N). - Open Page properties to change Destination, Page type, Aliases, or the URL Slug. A page can have up to 32 tags of up to 48 characters each and up to 32 aliases of up to 80 characters each.
- Choose Save draft, check the saved status, and read the result before publishing. The saved draft is visible to other authorized workspace Editors and Owners, not only to you.
For example:
# Product Launch
Mina owns the launch. The audience is new team members.
## Before launch
- [ ] Choose a reviewer for the installation checklist.
- [ ] Check the frequently asked questions.
You can start with ordinary sentences. Toolbar and block commands insert Markdown for you. Source, Reading, and Split are views of the same Markdown; narrow editors may hide Split.
Use Citation, /cite, or the References panel to choose an accessible Context, Library, or Agent document. Cite in text inserts a document-address citation; Add to references only lists the document without an in-text marker. See Images, links, and citations for selection, the 500-reference limit, and publication.
Save and publish deliberately
INTERACTIVE EXPLANATION
Who can read this version?
Compare who can read each state. MCP private editing differs from browser Save draft; these are not mandatory steps for every page.
Selected state: Author-private editing. Readers of this version: The author of this edit.
An open MCP edit is author-private
An MCP editing session in the editing state is readable only by its author. This differs from Save draft in the browser.
Readers of this version
- The author of this edit
Other authors and Viewers do not receive this private edit.
The same example page
Welcome guide decision
Working note: test a shorter introduction before choosing the first exercise.
Unsubmitted edit
An MCP edit stays private until submitted. A browser-saved draft can be read by permitted workspace Editors and Owners.
Fictional example. These controls explain a workflow; they do not operate dtxWiki.
| State | Who can read it | What it does |
|---|---|---|
Private MCP editing (editing) | Its author | Holds an open MCP edit before submission. Saving an MCP edit does not share it with other authors. |
Browser draft (draft) | Authorized workspace Editors and Owners | Save draft and browser autosave keep an unpublished version other editors can inspect. They do not by themselves create an explicit Review item. |
Submitted draft (draft) | Authorized workspace Editors and Owners, including eligible reviewers | Adds an explicit review request to an unpublished proposal. Review routing and access still apply. |
Published snapshot (published_snapshot) | Workspace readers allowed to read the page | Supplies the version Viewers receive. |
The browser's message is This draft is visible only to editors until you publish it. It means workspace Editors and Owners can read it; browser Save draft is not author-private storage. Unsaved text in the browser is different from a saved draft. The separate MCP editing workflow can maintain an author-private edit until explicit submission.
Choose Publish for workspace publication. A human Editor or Owner can publish when the page and policy allow it; an approved Review can also publish a version. Anonymous access requires the separate Publish to web action.
The explorer's Recent change marker lasts 72 hours after the first publication or a publication with changed body text. Save draft, autosave, and review submission do not themselves create that publication marker. Editors and Owners see a clock while a review targets the current draft. See explorer markers.
Read the page and its pending review
The Context reader has View, History, Graph, and Activity tabs. Activity lists events for this page; it is different from the workspace-wide Activity feed. Children appears when the page has child items and lets you open them.
When Draft pending review appears, check the version and the available View review, View changes, Request changes, and Approve actions. View changes belongs to this page banner; the Review queue uses Compare changes. Check what an approval will publish and which earlier reviews it will settle. Details are in Review and history.
Update a published page
Open Edit, change the page, and save a draft. Editors and Owners can inspect the saved draft, while Viewers keep reading the existing published version. Check Readers see v… and History before concluding that a change is available to readers.
If someone else changed the page, use View their changes. Preserve text you need before Reload latest, or choose Preserve mine as alternative when offered. An alternative is saved work, not an automatic merge or publication.
The editor's explorer row menu offers status and favorites; the full tree actions are on the Context screen.
Organize the tree
On the Context screen, use a row's ⋯ menu for Move up, Move down, Rename, Move, Copy link, or Delete, as your role and the item allow. Drag a row only after reading the placement hint: Before, After, Into, or Top of identifies where it will land. Cancel or retry when the hint is not your intended position. A link keeps identifying its document after a rename or move.
Delete archives the selected item and, where stated in the confirmation, its branch of children. It leaves the tree and search, and its anonymous web exposure ends. Version history is kept. Inspect the affected branch and sharing state before confirming; use backups for recovery planning.
Add an inline comment
Save the page and any current changes first. Select text in the editor and choose Comment. Inspect Prepare inline comment, write a Note, then choose Create. The comment is anchored to that saved version and creates a Page inline comment review item. It does not directly change the quoted text or publish a new version. Open the resulting review to follow it.
Resolve a blocked save
- Add a title and choose a valid destination. Titles and the first top-level heading have at most 256 characters on one line.
- Correct invalid aliases in Page properties. The whole stored page can have at most 1,000,000 characters.
- Retry or remove unresolved uploads. A failed upload is not a finished image insertion.
- If a reference change has an uncertain result, use its retry/check action before saving or publishing; do not repeat unrelated edits to guess whether it succeeded.
- Replace an Unresolved citation by choosing the intended document from References. See Lint.
- If publication is blocked, read the findings and confirm the saved draft still exists.
Long input is rejected rather than shortened. The editor's AI rewrite controls are disabled in v0.2.1; they do not rewrite your text.
Links and review state in 0.2
Link fixes and Lint policy can adjust supported addresses when you save. Reopening the same MCP chat's own pending submission can reuse that version and withdraw its earlier review; check the next submission's exact review target. Graph links and citations come from the current published version, so saving a draft alone does not add a public graph connection.
Continue with Images, links, and citations and Review and history.
Implementation reference: browser editor, draft saves, version visibility, Context tabs and pending review, tree actions, reference controls.