Pages

Pages hold a project’s wiki, with documents, nested pages and database entries. Use the sections below to organize and edit content, collaborate, manage files and versions, publish a branch or export it. Imports start from an empty database, as explained in the Databases guide.

Build a project wiki

Open Pages in a project as its owner or a Member; readers can open pages but cannot create them. Use the + menu and choose a page for a document or a database for a structured list. Give the page a useful title and write the specification, decision or procedure it should preserve.

Create subpages for related documents and use the tree controls to move or reorder them. A page cannot become a descendant of itself. Duplicating a page creates new content rather than a live reference to the original. Review the duplicate's branch before editing or sharing it.

Favorites and deletion

Favorite a page to surface it at the top of the project's page tree. These favorites are shared within the project, unlike a private notebook note. Link a page to an issue when the current document is task context; the resource's title follows page renaming.

Deletion sends supported page work to trash. From a page menu, Move to trash first asks for confirmation, naming the page and how many sub-pages go with it; they stay restorable from the trash for 30 days. Check the selected branch before deleting and use recovery rather than recreating a lost page when its content should be retained. Entries with stored database values can be reordered within their database but cannot be moved outside it. If a move is rejected, inspect the hierarchy and entry type instead of forcing it through repeated attempts.

Use the project page controls to choose a document or a database.

Promote a page to an issue

When a page describes work to do, the owner or a Member can turn it into an issue with Numo. Readers do not see this action. Promotion needs available AI usage or a compatible personal key.

1. Choose Promote to issue from the page’s menu in the page tree (… or a right-click on the row) or from the … menu of the open page (Page options). The same action is offered for a database entry opened in the side panel, and in the handle menu of a single entry, as described in the Databases guide.
2. If the open page has unsaved changes, minddy saves them first. If that save fails, minddy reports that the page could not be saved and Numo does not open. Promote the page again once it has saved.
3. Numo opens in the page’s project with the page as context and receives a request to read its title, its content and, for a database entry, its properties. When the page is unclear, or when a database leaves the issue’s scope ambiguous, Numo asks questions before creating anything. Answer them in the conversation.
4. Numo creates one issue and attaches the page to it. Open the issue and check its identifier, scope, properties and the attached page.

Unlike a promoted notebook task, the page is not removed: it stays in its place in the tree, with its content and subpages. If creation fails or the result is unclear after a network error, search for the issue before promoting the page again.

Write a page with blocks and mentions

Open the page and edit its title or body as the owner or a Member. Readers can open and read pages, but cannot edit, import, duplicate, favorite or publish them, or restore a version. Use the slash-command menu and formatting controls to insert headings, text, bullet, numbered and task lists, quotes, callouts, code blocks, dividers, toggles (collapsible sections), sub-pages, images and files. A callout can have an emoji icon and palette color; choose them to distinguish useful information rather than as the only way to communicate a warning.

Use mentions to link relevant issues, objectives, people or pages. Type @ followed by an identifier, title words or a short description; a descriptive query also lists issues found by meaning under Related by meaning, after the text matches. Backlinks help readers find pages that reference the current one. A link supplies context rather than granting a reader access to another project's private object.

Headings, task blocks and the AUR-2 mention keep the page structured. This is demonstration content.

Saving and portability

A page saves as you type: each change reaches the server within a moment, and the save indicator shows saving until the server has accepted it. Several people can edit the same page at the same time, including the same paragraph or the title. Each person's changes appear for the others as they type, and so do the edits Numo or an MCP-connected agent makes to the page.

If the connection drops, keep the page open. Unsaved changes stay on the page and are sent when the connection returns; changes from others arrive at the same time and merge with yours. minddy opens another page only once your changes are saved: while they cannot be sent, it keeps you on the page and says the save failed. Closing a browser tab with unsaved changes asks you to confirm first; quitting the desktop app does not ask, and unsaved changes are lost. If you lose access to the page or your edit rights while changes are unsaved, minddy undoes them and shows a message. When the server refuses a change, for example a title longer than 500 characters or a link whose protocol is not allowed, minddy undoes that change and shows a message. Page history can help inspect earlier saved versions.

Markdown exports and agent page reads preserve callout icons and colors in their supported representation. Export formats have different fidelity and attachment handling, so check the resulting document before replacing an original source. Use code blocks for literal commands and retain their prerequisites and warnings in the surrounding text.

Discuss a page and handle conflicts

Open a project page and its comment controls. Select relevant content when creating an anchored comment, explain the question or proposed change, and use mentions to involve a project member. A reader can comment when the owner turned on Can comment for them. Reply in the thread to keep the decision with the context it concerns. Resolve a thread when its question has actually been addressed.

Presence avatars identify people viewing the page. While someone edits, their caret and selection appear in the body and in the title, in a color of their own and labeled with their name. A reader's caret is not shown. A caret shows where someone is working, not that their text is saved: the save indicator reflects your own changes only.

Read page activity and write a comment in the composer. No comment has been submitted in this example.

Recover a save conflict

Simultaneous edits merge automatically, character by character, including inside the same paragraph. A conflict banner can still appear when minddy has to reload the page while you have unsaved changes: after a disconnection during which many changes were made, or after a change made without live editing, such as an import into a database. If your changes and the reloaded version altered the same top-level block, the document keeps the reloaded version of that block and the banner offers yours for review.

Compare the named block with the current document. Choose Restore mine only when replacing that block with your version is intended. If your conflicting action was a deletion, Delete it again applies that deletion explicitly. Dismiss keeps the adopted document and closes the warning; it does not restore your version. Preserve any wanted text before dismissing, and use history to inspect saved versions when a broader recovery is needed. These choices affect the identified block rather than blindly replacing the whole page.

A missing thread anchor can follow document edits; read the discussion before moving or deleting the referenced block. Comments and activity are internal to the project unless content is explicitly published through a supported sharing path. Use a published-page test to determine the visitor's actual view rather than assuming that project collaboration controls become public.

Attach and retrieve page files

Open the page as a project member and use its attachment or upload controls. Select a nonempty file within the 10 MB per-file limit. Your account or instance storage quota can impose an additional limit. Keep the original until the upload succeeds.

Images can be inserted as image blocks, and other documents can be attached as file blocks. The server determines the stored media type from the bytes rather than trusting the filename or browser label. Upload acceptance does not guarantee that every format has an inline preview; use the file download when a preview is unavailable.

In the project editor, click an image or the name of a supported file block to open the same full-window reader used by issue attachments. Markdown (.md), plain text (.txt, .text), CSV, PDF and supported audio or video open in dedicated containers. Use Close or Escape to return to the page. The File actions (…) menu offers Download. In an editable page, a file block also offers Rename, which changes the name shown in the page, and images and files offer Remove: it asks for confirmation, then removes the block from the document, and you can undo it in the editor. The file block also keeps its direct Download control. Unsupported formats, external file links and file blocks on published pages retain their download behavior. Published images use the reader without a removal action.

The shared file reader keeps Close below the preview. The File actions menu offers Download and, when permitted, Rename and Remove.

Check that the file appears in the page and open or download it. File bytes live in Storage, while the page and file metadata determine access. A successful page save alone does not prove the file bytes are available.

Shared files and failures

A file referenced on a published page can be made available to that page's visitors. Files from pages outside the published branch are not made available merely because another page contains a reference. Review the page and children included in publication before sharing.

If upload fails, check the size, quota and error message. A self-hosted operator should also verify Storage configuration and policies. For a missing file after restoration, recover the matching raw Storage bytes and metadata; a database-only restore cannot recreate the file. Published file URLs are signed for up to 24 hours when the page is rendered. Revoking a share stops new authorized page visits but does not immediately invalidate file URLs already delivered; those can remain usable until their expiry. Downloaded copies cannot be recalled.

Check the actual file state: the second attachment is available, while the first unfinished upload is not.

Inspect and restore a page version

Open the page's save/history indicator to view versions, or its comments/activity control to inspect actions. These tabs answer different questions: a saved version is a document state, while activity can include renaming, deletion or restoration without the same content snapshot.

Select a version to preview it before restoring. The history identifies authors and agent activity, so compare the content with the change you intend to undo. The interface announces a 30-day history window; do not treat history as a permanent external backup.

Restore and verify

As an authorized project member, restore the selected version only after reviewing the current content it will replace. The pre-restore state itself enters history, which supports recovering that state later while it is retained.

Reopen or refresh the page editor after restoration and check its actual body. A previously open editor holds an outdated version and must not blindly overwrite the restored state. Page versions are not complete instance backups: attachment bytes, deleted files or related objects can have separate lifecycles. Use the page-file section and instance restoration procedure when the missing information is outside the saved document body.

Preview a saved state and compare it with the current page before restoring.

Publish a page and revoke its link

Open a project page as the owner or a Member and use its publication controls. Review the content and attachments first. Choose private, password-protected or public access. Password protection requires at least eight characters and is applied after submitting the password; selecting the mode alone does not create a protected link.

Copy the generated /p/ link after publication succeeds. If the page has descendants, review the include-children option and count. Including children publishes the selected branch; excluding them keeps their content outside that publication. A database without published children does not expose all its entry bodies automatically.

Open the link in a separate browser session without your account. Test the password if enabled, page content, intended subpages and file downloads. This verifies the visitor's read-only access rather than your broader member permissions.

Private keeps the page within the project. Review the intended audience before changing publication.

Revoke and check

Return to publication controls, choose private and confirm with Unpublish: the old link stops working, and publishing again creates a new link. After successful revocation, open the old link anonymously and check that access is denied. Copies or screenshots already received cannot be recalled. File download URLs already delivered by a published page are signed for up to 24 hours. Revocation prevents new page visits but those previously issued file URLs can remain valid until they expire.

User page links remain noindex and are separate from the indexed official manual. Noindex is a discovery policy, not an access password. If a child or file is unexpectedly readable, revoke first, inspect the published branch and retest before forwarding a corrected link. Files belonging to unpublished pages do not gain access merely through an internal reference.

Export or print a page

Open the page’s document menu, then Export. Choose Markdown for a page (.md) or a branch (.zip), PDF to open the print view, or the database archive when the page is a database. Review the offered scope before confirming; a page, its branch and a database archive have different contents.

Open the resulting export and verify headings, callouts, links and attachments needed by its reader. The PDF action opens a readable print view rather than the entire application navigation. Use the browser’s print controls to print or save a PDF. There is no general import action in the document menu; supported imports are started from an empty database, as described in the database import section.

Choose Markdown to download the document, or Print / PDF to open the printable view.

Database archives and limits

A database archive (.zip) includes its branch: Markdown and CSV, exact schema and option colors, values, bodies, timestamps, nested pages and file bytes. Import it into a new empty database to restore that structure. Device-specific filtering, sorting and hidden-column preferences stay on the original device.

An export is not a transfer of passwords, account provider credentials or subscriptions. For moving account work between instances, use the account-data transfer guide. If an imported format cannot preserve a block or external property, inspect the result before relying on it as a replacement. Do not delete the original merely because a download file was created.

Routines for new entries

The project owner can choose this database as a routine trigger in Routines. Conditions use the entry’s typed properties. An empty entry can stay waiting until its properties are filled. Creation, duplication, database import and an allowed move into the database count as arrivals; restoration does not. Removing a referenced property or changing its type requires correcting the routine filter.