Visual Space manual, Spaces, Browse And Read A Wiki
Use this walkthrough to enter the right space, find its curated knowledge, and open a Wiki page with confidence. For the wider purpose and boundaries of the feature, start with the [Wiki overview](../wiki.md).
Use this walkthrough to enter the right space, find its curated knowledge, and open a Wiki page with confidence. For the wider purpose and boundaries of the feature, start with the Wiki overview.
Open Wiki In The Intended Space
Wiki belongs to one space. It can organize pages from that space root, its subspaces and activities, and their Documents folders, but it does not combine pages from several spaces.
•
Enter the intended space - Open the community whose knowledge you want to read. If the space or one of its areas is protected, you need access before its Wiki pages can appear.
•
Open the Apps menu - Use the space's app launcher so you stay in the current workspace context.
•
Choose Wiki - Select Wiki. You can also open a saved link to a Wiki page.
•
Confirm the community - Check the current space identity. Opening Wiki from the Apps menu returns to its alphabetized collection index, so you can choose a page without reopening the last one you read.
Find A Page In The Tree
The Wiki tree combines two kinds of structure. Space-area headings show where work belongs in the community; nested folder rows reflect how that material is organized in Documents. Subspaces begin expanded, while activities and folders begin collapsed. A direct article link opens its ancestor branch for you. See Space Areas for the upper hierarchy and Library And Folders for the folder structure beneath it.
•
Choose a route into the collection - Select a title from the alphabetized center list, or explore the space-area branches on the left. The tree does not repeat the current space as an extra enclosing row.
•
Follow the narrowest context - Choose the subspace or activity that best matches your subject, then continue through any nested folder rows.
•
Use structural rows for orientation - Selecting a subspace, activity, or folder row only expands or collapses its descendants. These rows do not open content in the center.
•
Choose an article leaf - Article rows are the only leaves that open a Wiki page. Select the title that matches what you want to read.
Folders appear only as routes through the tree; there is no folder landing page or folder-content view in Wiki. If a structural branch has nothing to reveal, it is context rather than a reading destination.
The selected page keeps its place in the Wiki tree while you read.
Read The Selected Page
The selected leaf opens in the center using the normal article reading view. Read its summary and published body in order, open supported media, and use the reader actions available to you. Reading Articles explains the complete reading experience.
•
Keep the Wiki tree as your index - On the Wiki route, the left tree replaces the article's ordinary Topics index. Use it to move between curated pages rather than to jump among headings inside the current page.
•
Use About for space context - The existing About panel remains on the right. It explains the current community context; Wiki does not add a separate right-side panel.
•
Continue with another leaf - Select another article title in the tree when you are ready to move through the curated collection.
On mobile, open the navigation panel to reach the same Wiki tree. Selecting an article closes the panel and gives the reading view the available space.
On mobile, the same Wiki tree moves into the space navigation panel and closes after a page is chosen.
Trust The Current Documents Location
Wiki does not maintain a second folder arrangement. When a maintainer moves or renames an article or one of its folders in Documents, the Wiki tree uses that current location automatically the next time it loads. Readers do not need to follow a separate synchronization step or learn a Wiki-only path.
A page can appear under a different branch after the library is reorganized. If you already have Wiki open when a change is made, leave it and reopen it to load the updated collection.
Handle Loading, Empty, And Error States
•
Wait while Wiki loads - Placeholder rows and a Loading Wiki message mean Visual Space is preparing the current tree. Let the request finish before deciding that a page is missing.
•
Recognize an empty Wiki - No Wiki pages yet means no curated articles are currently available to you. The collection may be empty, or its pages may belong to private areas you cannot enter. Ask a space maintainer if you expected to see a particular page.
•
Retry a failed load - If you see Wiki could not load, check your connection and select Retry in the Wiki tree. The current structure is requested again without changing any page.
•
Recheck context and access - If the tree loads but the expected leaf is absent, confirm the space and area, then consider whether the page is published, curated, and available to you.
•
A saved link opens the collection instead - The linked article is no longer part of the Wiki available to you. Choose a current title or ask a maintainer to check its curation and access.
You have completed the journey when you are in the intended space, can find the article through the collection or tree, and see its published content in the reader. Return to the Wiki overview for the feature model. If you maintain the collection, continue with Curate A Wiki.
Visual Space
4 Followers
Meet fellow creators and transform bright ideas into real projects β¦β¦β¦ or just geek out for the fun of it π
Visual Space is built for projects like thisβwhere creators collaborate, organize goals, and grow communities around real work.
Manage Your Cookie Preferences
We use essential cookies to keep Visual Space working. Optional analytics help us understand usage, improve the app, and measure ad campaigns including registrations and return visits.
Essential storage β always active
Keeps you signed in and remembers your preferences. This stays active with either choice below.
Analytics β optional
Only if you allow it, we count page views, daily visitors and recent activity using a random daily device identifier and broad page, source, device and country categories. General audience totals are not linked to your account. Accepting also enables ad campaign measurement for 30 days using a separate random identifier to measure exploration, account creation and returning days. Campaign attribution can be linked to your newly created account. We do not send page addresses.
Analytics totals are kept for 13 months; general audience identifiers expire within 48 hours. Campaign attribution lasts 30 days. Reopen Cookie preferences at any time to change your choice or turn analytics off.
