Visual Space - Page 6 | Visual Space

MathPad is Visual Space's workspace for writing structured mathematics directly in its rendered form. It brings formula entry, visual templates, keyboard-friendly editing, inspection, accessible output, and several portable formats into one focused Live App. It is useful when the shape and meaning of a formula matter as much as the characters used to describe it.

Live Apps are focused creative workspaces that stay connected to the space area where the work belongs. You begin with familiar file browsing, then open a dedicated editor for drawing, video, spatial planning, 3D scenes, technical designs, or formulas. That shared shape makes it easier to move between ambitious tools without losing the surrounding Visual Space context.

Layouts gives you a fast, measured 2D workspace for sketching rooms, renovations, office arrangements, event setups, and other floor-plan ideas. It combines a meter grid with approachable drawing tools, so you can communicate dimensions and spatial relationships without starting a full building-design project.

Live Apps bring focused creative tools into the spaces where people already plan, discuss, and review their work. Use this guide to choose the right workspace, understand what will be saved, and continue into a practical walkthrough.

Frames is a focused video-timeline workspace for assembling and reviewing an early sequence. It brings clips, captions, titles, audio, markers, and editing controls together so you can explore the shape of a video before a production media and export workflow is involved.

Canvas is Visual Space's layered workspace for painting, image composition, and artwork drafts. A Canvas belongs to a space area, opens in a focused editor, and stays connected to the documents and conversations around the work. Its editable project can be revisited instead of becoming a flattened picture after every session.

Blueprints is a CAD-lite workspace for people who need a technical idea to keep its measurements and design intent. Makers can explore a simple part, students can learn how references and constraints shape geometry, and reviewers can inspect a design without separating the model from its discussion. The emphasis is **controlled geometry**, not merely producing a convincing picture of an object.

Use this walkthrough when a Chat conversation needs a lasting link back to a goal. You will choose the goal from the reference picker, send it as part of a message, and confirm that the posted reference opens the intended work. A goal reference is more than typed text. Selecting a result from the picker turns the visible label into a durable link that follows the goal when its space key or location changes.

This walkthrough turns a busy Goals workspace into an understandable plan. You will shape the active workflow, move later work into the backlog, make responsibility visible, and then use filters and search without disturbing the order you established. The guide is primarily for space owners and goal managers. Wherever a reporter, direct assignee, or member of an assigned role can perform an action on an individual goal, that step is marked **Goal editors**. For the concepts behind the workflow,

Finishing a goal has two stages. First, a goal editor moves the goal into a column whose category is `Done`. Later, a space owner or goal manager can clear that whole column from the active board into Done Goals history. This walkthrough takes you through both stages and helps you check the result before the completed work becomes a lasting read-only record.

Use this walkthrough when an idea is ready to become visible work. You will place it in the right space area, publish it to a workflow column or the backlog, develop its article, add responsibility and a color tag where useful, then confirm that other members can recognize it on the board. Goal creation is immediate: there is no draft stage in the current board and backlog flow. A clear title is enough to create the goal, but the linked article is where you explain the result, context, and invit

Assignees, color tags, activity labels, filters, and search add structure to a Goals workspace without changing what a goal is. The same goal keeps its article, discussion, reference, status, and board or backlog placement; these organizing details simply make responsibility and context easier to see.

Goals helps a community turn shared ideas into visible, organized work. Use this guide to understand the planning model, choose the right surface, or follow a complete workflow from creation through completion.

Goals gives a community a shared place to turn ideas into visible work. It is a lightweight planning layer for a space: structured enough to show what matters and who is helping, but deliberately less formal than a company project tracker. Each goal combines two useful shapes. On the board it is a compact card that can move through the community's workflow. Open it, and it becomes a full article with the context, discussion, and supporting content needed to help someone understand the work and c

Goal references give each goal a readable label that is easy to recognize on a board and easy to share in Chat. A label such as `VS-42` combines a space's goal key with the goal's number in that space. The label is a convenient name, not a fragile link. When someone selects a goal through the Chat picker, the shared reference continues to follow that intended goal even if its visible label later changes.

Completed Goals keeps finished work available as a record of progress after it no longer needs space on the active board. It is the second stage of completion: first a goal reaches a `Done` category, then a manager may clear that column into history without deleting the goal or its article.

The Goals board keeps a community's active work visible without turning participation into a heavy project-management process. It gives members one place to see what is waiting, what is underway, and what has been finished, while leaving future work in the [backlog](backlog.md).

The backlog is the Goals workspace for worthwhile work that is not ready to occupy the active board. It lets a space keep promising ideas, paused efforts, and later priorities without mixing them into the work people are trying to move forward now. A backlog goal is still a complete goal. Moving it away from the board changes its placement, not its identity or the context people have already built around it.

Use this walkthrough to place important published work in Expo, confirm where it appears, and remove it when it no longer belongs in the showcase.

Use this walkthrough to find selected work without searching the entire document library. For the broader purpose of the showcase, start with the [Expo overview](../expo.md).

Expo turns selected published work into a focused showcase for a space and its areas. Use this guide to understand what appears at each level, explore community highlights, or maintain the selection as a space owner.

Expo is the official showcase for a space and its areas. It brings selected posts, articles, events, goals, and documents into one visual collection so visitors can quickly understand what the community values and has accomplished.

Use this walkthrough to keep a published event accurate as plans change. You will update the event article, make only the schedule changes allowed by its current state, and confirm that the article and event card still agree.

Use this walkthrough to find an event that matters to you, read its full context, share your attendance plans, and keep a personal shortcut for later. The journey may begin in Events, on an About page, or in Search, but the event's linked article remains the durable place for its details and discussion.

Use this walkthrough to prepare a scheduled community occasion privately, then publish it for members of the right space, subspace, or activity. You will finish with an event card that opens into a detailed event article.

Events helps a community plan scheduled occasions, make likely attendance visible, and preserve the surrounding context after the date has passed. Use this guide to understand the event model or follow a complete journey from private draft to lasting community record.

Events gives a community one place to coordinate scheduled moments such as planning sessions, workshops, demos, larger meetings, and shared deadlines. It keeps the date and expected attendance easy to scan while giving every event enough room to explain why people should join. Events belongs to the area where the occasion is organized. A space can host community-wide events, while a subspace or activity can keep a more focused schedule close to the people and work it concerns. This makes Events

An event article is the durable home for a scheduled community occasion. The event card gives members a compact view of what is happening and when; opening it reveals the fuller explanation, conversation, and related material that people need before, during, and after the event. This pairing keeps scheduling and context together. Members can scan Events to make an attendance decision, then open the same event to understand the agenda, contribute to the discussion, or revisit what happened later.

Attendance gives members a quick way to share whether they expect to join an event. The three response counts help coordinators estimate likely participation without turning Events into a personal calendar or asking everyone to explain their schedule.

Documents accepts everyday media and project files while keeping upload rules visible at the point where they matter. You can add several files at once, bring in a folder tree, and recover from one failed item without losing sight of the rest of the batch.

Use this walkthrough to add a batch of files or an existing folder tree to Documents, follow every result, and confirm that the new material arrived in the right part of the space. The destination matters as much as the files: everything you upload inherits the audience of the space, subspace, or activity that contains it.

Use this walkthrough to bring one document or a carefully chosen set from Documents into an active Chat conversation. You will keep the source material in its library location, review exactly what Chat accepted, add a useful explanation, and confirm that the resulting attachments or links respect the source access rules.

Documents supports two ways to begin publishable work. You can create an Article, Event, Retrospective, or Whiteboard from `New`, or you can choose `Publish` on an existing upload to make a separate article-style draft around it. Both paths keep unfinished work private to its author until publication. Choose the first path when the work should begin in a Visual Space editor or collaborative app. Choose the second when you already have a source file that should remain available in its original fo

Use this walkthrough to turn a crowded Documents area into a library that members can understand. You will inspect the current location, build a small folder structure, move the exact items that belong together, and verify both placement and access before cleaning up anything left behind. This guide is for space owners and members who see space-management controls. **The space-owner path is the dependable management path.** A member with space-management access may see move, rename, or folder co

Documents remains the home of a file, article, or app file even when people use it elsewhere. You can bring a document into Chat for discussion, save it to View Later for yourself, feature eligible published work in Expo, collect a published article in Wiki, or respond to document-backed content with a reaction. Each route adds a useful connection without creating a second source location. That distinction matters for access. **Sharing, saving, or featuring a document never makes it available to

Organizing Documents is less about keeping a perfect folder tree and more about making deliberate changes that other members can understand. Select only the material you intend to affect, choose a destination that matches its community context, then check both the old and new locations before continuing. Documents supports quick single-item moves and larger cleanups across folders, subspaces, and activities. The same location rules apply in both cases: ordinary folders organize content beneath a

Documents gives a space one connected library for folders, uploads, articles, and supported app files. Its structure begins with the areas members already know, then adds ordinary folders for more detailed organization. This keeps a file's location understandable without creating a second map of the community.

Documents is the shared library for a space. Use this guide to understand how folders, uploaded files, articles, and supported app files stay connected to the spaces, subspaces, and activities where people work.

Documents is the shared library for a space. It brings uploaded files, folders, articles, and supported app files into one place, then arranges them by the same spaces, subspaces, and activities that members already use elsewhere in Visual Space. That shared structure is the important part. A useful image from Chat, a file uploaded for an activity, and an article created for the same work do not need three unrelated filing systems. They can remain close to the community context that gives them m

Files in Documents form part of a space's shared memory. A direct upload can live alongside images and videos collected from Chat or articles, so useful material remains discoverable after the conversation or publication where it first appeared has moved on. The library accepts many everyday file formats, but it does not pretend that every file can be displayed in the same way. **Preview availability changes how a file is presented, not whether an accepted file remains useful.** A file without a

Documents can hold more than uploaded files. Articles, Events, Retrospectives, and Whiteboards can appear in the same library, close to the folders and space areas where people expect to find them. These entries are app files: selecting one opens the Visual Space experience that owns the content rather than treating it as a generic download. Publishing an upload uses a related but importantly different path. **The uploaded file and the article-style document created from it remain separate libra

This walkthrough helps you share files with the right people, follow the upload through completion, and confirm that recipients can open what you sent. It applies to both [Activity Chat](../activity-chat.md) and [Direct Messages](../direct-messages.md), with an important difference in where the files live.

This walkthrough turns one valuable Activity Chat message—or an idea that has grown beyond a chat message—into a reviewed article. Use it when a contribution deserves a durable life outside the rapid conversation, but does not represent the outcome of the whole topic.

Use this walkthrough to keep important conversations close, quiet noisy discussions, clear unread attention at the right scope, and step away when a conversation should no longer reach you. Most of these choices organize only your own **Messages** view. Blocking and leaving go further because they change who can communicate or participate.

This walkthrough takes an Activity Chat topic from an author-only draft to a focused live discussion and a durable summary. Use it when a group is beginning a distinct question, phase, or decision that should remain understandable after the rapid exchange has ended.

Use this walkthrough when one message needs to answer an earlier point, reach a specific participant, and keep a durable link to the work being discussed. You will prepare the message in the right topic, send it without losing its context, verify the result, and correct it in place if needed. The workflow applies to both [Activity Chat](../activity-chat.md) and [Direct Messages](../direct-messages.md). Their audiences differ, but their reply, mention, goal-reference, formatting, and editing tool

Topics turn a flowing conversation into sections people can understand later. Each divider gives readers a clear place to begin, while Activity Chat adds a connected summary for the decisions and useful findings that should outlast the live exchange.

Chat offers several quiet signals that help you answer two different questions: **who belongs in this conversation context**, and **what has changed since you last looked**. Participant lists explain the people around the discussion, while presence, typing, and unread cues help you decide where to focus next. These signals do not change messages or grant access. They reflect the current Activity Chat area or Direct Message conversation, and they stay separate from the conversation itself.

Messages in Visual Space are designed for quick conversation without throwing away the context people need later. The same core experience works in [Activity Chat](activity-chat.md) and [Direct Messages](direct-messages.md): write a short update, shape it with lightweight formatting, point to a person or goal, and reply without leaving the main conversation. This page explains that shared message experience. Files and engagement stay close to messages too, but they have their own guidance so the

Chat helps members keep live conversation connected to shared work, preserve useful outcomes, and continue privately when a one-to-one or group discussion is the better fit. Use this guide to understand the two conversation spaces or follow a complete workflow for topics, messages, files, Direct Messages, and custom emoji.