Wiki gives a space a calm, curated place to read the published articles that deserve a longer life. Instead of asking readers to search every feed or browse the whole document library, maintainers can collect durable guidance, decisions, explanations, and reference material in one space-level knowledge tree.
Curated Knowledge, Grounded in the Space
Wiki is an article-only reading surface. It does not create another kind of page or copy content into a separate publishing system. Each Wiki page is an existing published article, with the same title, body, author context, and reading experience it has elsewhere in Visual Space.
That narrower scope gives Wiki a clear job beside the space's other content surfaces:
Because Wiki belongs to the whole space, it can bring together selected pages from the space root, its subspaces, its activities, and folders nested below those areas. It remains one coherent reference surface even when the community's work is spread across several teams or topics.
Open Wiki and Follow Its Tree
Open the space Apps menu and choose Wiki, immediately after Expo. This is the only Wiki entry point in version one. Wiki does not also appear as an About preview or as a separate shortcut from another content surface.
Wiki opens from the current space's Apps menu, directly beside the independent Expo experience.
The left side of Wiki presents an expandable tree built from the space's existing organization:
Select an arrow or structural row to expand or collapse that branch. Space, subspace, activity, and folder rows organize the tree; they do not open content. Only an article leaf opens in the reading area. This keeps the tree predictable: branches reveal where knowledge belongs, while leaves hold the knowledge itself.
Branches preserve the current space and Documents structure, while linked-article leaves are the destinations readers can open.
When no article is selected, the center asks you to choose a Wiki page. An empty Wiki explains that published articles will appear in their current Documents folders after they are added. If the tree cannot load, use Retry in the Wiki panel.
For a complete reader journey, see Browse and Read a Wiki.
Read an Article in Wiki Context
Selecting a page opens the normal article reader in the center while keeping the Wiki around it. The article's summary and body remain the source of truth; Wiki supplies a different navigation context for moving through the space's curated knowledge.
On the left, the Wiki tree replaces the normal Topics or article index. This means the panel navigates between curated pages and their folders rather than jumping between headings inside the current article. On the right, the existing About panel continues to provide space context.
The Wiki tree becomes the article index for this route, while the established reader and About context remain familiar.
The Wiki route is intentionally read-only. Edit, publish, and delete actions are suppressed even when the current reader could change that article through its normal Articles route. Wiki is where people consult the curated collection; article authoring remains with Articles.
Curate the Collection
The space owner and members with the Manage Content permission can add or remove eligible pages. The action appears as Add to Wiki or Remove from Wiki in the menu for a published article, including its supported Documents menu.
An eligible Wiki page must be:
Draft articles, folders, raw files, and other document types are not eligible Wiki pages. Adding an article to Wiki does not publish a draft, move the article, or grant it new visibility.
Wiki uses a confirmed-success state for curation. After you choose an add or remove action, the visible membership marker changes only when Visual Space confirms that the operation succeeded. If the request fails, the current marker remains unchanged instead of suggesting that an uncommitted change took effect.
Removing a page only removes it from the Wiki collection. The source article remains published and stays in its current Documents location. Use Curate a Wiki for the complete maintenance workflow and its success checks.
Let Documents Control Placement
Wiki does not ask maintainers to organize the same page twice. It reads each curated article's current Documents placement and includes only the folder ancestors needed to show that location in the tree.
As a result, normal organization work flows through automatically:
There is no separate Wiki ordering, folder creation, drag-and-drop, or move command in version one. Organize the source material in Documents, then use Wiki membership to decide which published articles belong in the curated reading set.
Wiki and Expo Stay Independent
Wiki and Expo are both curated, but they answer different questions. Wiki helps readers navigate durable article knowledge. Expo showcases selected space work. Expo can include several supported content types and presents them as a showcase; Wiki accepts only published articles and presents them in a Documents-derived tree.
Their membership is independent. Adding an article to Wiki does not add it to Expo, and adding it to Expo does not add it to Wiki. Removing it from either surface has no effect on the other. A space can choose the same article for both when it serves both purposes, but each decision must be made separately.
Separate menu actions make the two curation decisions independent even when one article belongs to both collections.
Version One Boundaries
Wiki's first version concentrates on finding and reading curated articles. It does not include:
These limits keep content ownership clear: Articles handles writing and publishing, Documents handles location, and Wiki handles the curated reading set.
Common Questions
Can every document become a Wiki page?
No. Wiki accepts published articles only. Drafts, folders, raw files, and other document types remain outside the collection.
Why does selecting a folder not open its contents in the center?
Folders and space areas are structural branches in version one. Expand them to reveal descendants, then select an article leaf to read it.
What happens when a Wiki article or its folder moves in Documents?
Wiki follows the current Documents placement. The page appears under its updated area and folder path on the next Wiki read; no separate Wiki move is needed.
Does removing a page from Wiki delete or unpublish it?
No. Removal changes only Wiki membership. The published source article and its Documents location remain intact.
Why did Add to Wiki or Remove from Wiki appear not to change?
The visible state changes only after the request succeeds. If it stays unchanged, the operation was not confirmed; check your connection and try again.
Can I edit an article while reading it in Wiki?
No. The Wiki route keeps the article reader read-only. Open the article through its normal Articles context to use authoring actions available to you.
Does adding an article to Expo also add it to Wiki?
No. Expo and Wiki are independent collections with different purposes and eligibility rules.
Who can curate the Wiki?
The space owner or a member with the Manage Content permission can add and remove eligible published articles. Readers who can open the space's Wiki do not receive curation controls unless they also have that authority.