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 reference material in Library.

You need Editor or Owner access to create and edit pages.

View full-size image

Actual dtxWiki screen with fictional demo data. Item names can differ from the walkthrough. Markdown source editor showing a fictional Product Launch Plan and its Save draft and Publish controls.

Write your first page

1. Check the workspace, then open Context → New Context page.
2. Give the page a clear title, such as Launch plan.
3. Write a short introduction, then add headings and lists. Type / to open the block menu, or use the toolbar for headings, bold text, links, and tables.
4. Open Page properties if you need to change Destination, Page type, Aliases, or the URL Slug. Tags help describe the page; aliases give it additional names for search and wikilinks.
5. Choose Save draft, check the saved status, and read the result before publishing.

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. Markdown syntax is useful but optional knowledge; toolbar and block commands insert the formatting for you. This is a Markdown editor with Source, Reading, and Split modes, rather than a word processor that guarantees identical layout in every export.

Save and publish deliberately

INTERACTIVE EXPLANATION

Who can read this version?

Select a state to compare its readers. These are separate choices, not a mandatory four-step approval process.

Selected state: Private editing. Readers of this version: The author of this edit.

Saved does not mean submitted

The browser’s Save draft keeps this author’s unsubmitted edit. Other people do not receive it simply because it was saved.

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

Remember

An authorized human Editor or Owner may publish directly in the browser. Explicit review submission is another route.

Fictional example. These controls explain a workflow; they do not operate dtxWiki.

State	What it means
Private editing (editing)	An unsubmitted saved edit is visible to its author. It is not shared merely because it was saved.
Submitted draft (draft)	A proposed version is available to authorized Editors for review. It is still not the version a Viewer reads.
Published snapshot (published_snapshot)	The workspace's current published version for readers.

In this build, the browser editor's Save draft saves the editor buffer without publishing it; it does not itself call the explicit review-submission operation. MCP clients and the REST editing workflow can explicitly submit a private edit for review.

Choose Publish to save and publish the current page version. An authorized human Editor or Owner can publish directly; review is also available for proposed changes. Publish here is workspace publication. Anonymous access requires the separate Publish to web action.

An Editor's searches or Ask requests can retrieve draft evidence they are permitted to read. Do not assume that every unpublished version is excluded from every Editor's answer. Other authors' unsubmitted private edits remain private; Viewers receive published evidence.

Update a published page

Open the page and choose Edit. Make changes, save, and publish when ready. Until then, workspace Viewers continue to read the existing published version. Use the Readers see v… indicator and History to check the exact reader-facing version.

If someone else changed the page, review View their changes. Choose Reload latest after preserving text you need, or Preserve mine as alternative when offered. An alternative draft is preserved work, not an automatic merge or a published replacement.

Resolve a blocked save

• Add a title and select a valid destination.
• Fix invalid aliases if the editor requests it.
• Retry or remove unresolved image uploads before saving.
• If publication is blocked, read the finding and confirm the page still has a saved unpublished version. Do not assume a failed publish erased it.

The AI rewrite controls shown in the editor are disabled in v0.1.2; they do not automatically rewrite your page.

Continue with Images, links, and citations and Review and history.

Implementation reference: browser save and publication, version visibility, editing endpoints.