---
title: Wiki pages
description: Write and organise the workspace wiki — creating pages, nesting them, the editor, images, and how autosave and drafts behave.
section: Wiki
order: 1
---

# Wiki pages

Every workspace has one wiki: a tree of pages for the things that do not belong
on a ticket — decisions, guides, conventions, anything you would otherwise
explain twice.

Open it with **Wiki** in the sidebar, under **Workspace tools**.

## Before you start

- The wiki is **per workspace**, and there is one of them. It is created with
  the workspace; if it is somehow missing, writing your first page creates it.
  You do not choose between wikis and you cannot add a second one from the app.
- Wiki access follows **workspace** membership, not board access: everyone in
  the workspace can read every page, including pages about boards they cannot
  open.
- Writing needs a writer role — **owner**, **admin** or **member**. Viewers can
  read and search but cannot create or edit. See
  [Roles and permissions](/docs/workspaces-and-access/roles-and-permissions).

## Create a page

- **A top-level page:** click the **+** beside **Pages** at the top of the
  sidebar tree.
- **A page inside another:** hover the parent row in the tree and click its
  **+**, or open the parent and choose **Add child page** from the `⋯` menu.

Either way, name it in the dialog and click **Create page**. Titles can be up
to 300 characters, and a page left untitled is saved as _Untitled_.

## Nest and organise pages

Pages nest as deeply as you like. The tree in the sidebar shows the structure,
with a chevron to expand and collapse a branch, and the top of each page shows
its breadcrumbs back to the root.

**Move a page under a different parent:** open it, then `⋯` → **Move page**, and
choose a new parent from the dropdown — or **Top level** to bring it to the
root. A page cannot be moved underneath itself or one of its own descendants;
that is refused with "A page cannot be moved below itself."

**Reorder pages among their siblings:** drag a row in the tree and drop it above
or below another row; a line shows where it will land. Dropping a page beside a
row also makes it a sibling of that row, so a drag can change both the parent
and the position at once.

**Show a contents list:** `⋯` → **Show child page list** puts a **Pages in this
section** panel at the top of the page, linking to its direct children with
their own child counts. The same menu item hides it again. The setting belongs
to the page, so everyone sees it.

## Limitations

- **Reordering pages is drag-and-drop only, with a mouse or other pointer.**
  There is no keyboard equivalent — no arrow-key reordering, no "move up" or
  "move down" command, and no way to type a position. Elsewhere in Laver (board
  and column reordering) arrow keys do work; in the wiki tree they do not.
- If you cannot drag, **Move page** is the keyboard-reachable fallback. It can
  change a page's parent, but it cannot set where the page sits among its new
  siblings.
- A page can only be moved within its own wiki.

## Write a page

The page title is the big field at the top; the body is below it.

The editor is rich text. Type `/` for the command menu, or use the toolbar:

- Headings 1–3, **bold**, _italic_, strikethrough, inline code
- Bullet lists, numbered lists, checklists, quotes, code blocks
- Links, images, tables, dividers
- Undo and redo

Type `@` to mention someone. The list is the active members of the workspace,
and the person you mention gets an in-app notification linking to the page.
Notifications are in-app only — Laver does not email them.

## Add images

Paste an image, drop one onto the page, or use the image button in the toolbar.
It uploads to the page and is embedded where the cursor is. Selecting an image
gives you width buttons, including **Auto** for its original size.

- **Images only.** PNG, JPEG, GIF and WebP. Wiki pages do not take PDFs,
  documents or any other file — those go on a ticket instead, where the allowed
  list is wider. See
  [Comments and files](/docs/boards-and-tickets/comments-and-files).
- **10 MB per image.** Anything larger is refused with "Pasted images must be
  10 MB or smaller."
- Images count against the workspace storage allowance — 1 GB on the free plan,
  unlimited on Pro — the same pool that ticket attachments draw on.

## Drafts and autosave

There is no save button. Laver saves the page 750 ms after you stop typing, and
the pill at the top right of the page tells you where it has got to:

| Pill         | Meaning                                                              |
| ------------ | -------------------------------------------------------------------- |
| **Saved**    | The server has your latest edit                                      |
| **Unsaved**  | You have typed since the last save; a save is queued                 |
| **Saving**   | A save is in flight                                                  |
| **Error**    | The save failed. Your work is kept in this browser and Laver retries |
| **Conflict** | Someone else saved this page while you were editing it               |

Every keystroke is also written to a draft in **this browser**, so closing the
tab or losing connection does not lose your work. When you reopen a page whose
local draft is newer than the server's copy, a banner says "A newer local draft
was restored from this device." — keep typing to save it, or click **Discard
draft** to go back to the server's version.

Two things worth knowing about drafts:

- The draft is stored in the browser you typed it in. It does not follow you to
  another device or another browser.
- **Conflict** means Laver has stopped pushing your edits so it does not
  overwrite someone else's. Your draft is safe and unsent. Copy what you need,
  reload the page to pick up their version, and paste your changes back in.

## Version history

**History** is its own button at the top of the page, next to `⋯`. It lists
every saved version, newest first, each with its version number, the time it
was saved and the page title at the time, and a **Restore** button. Restoring
writes the old content back as a new version, so nothing is lost by trying it.

Every autosave creates a version, so the list is granular.

## Rename a page

Edit the title field at the top of the page — it autosaves like the body. To
rename a page without opening it, right-click its row in the tree and choose
**Rename**.

## Duplicate a page

`⋯` → **Duplicate page**, or right-click a row in the tree and choose
**Duplicate**. The copy is titled "_original_ (copy)" and is placed directly
after the original among its siblings. **Child pages are not copied** — only
the page itself.

## Search the wiki

Type into **Search the wiki...** in the sidebar, or press `Cmd`/`Ctrl`+`K`.

Search covers page **titles and body text** across the whole wiki, and results
show a matching excerpt. Use the arrow keys and `Enter` to open one. Archived
pages are not searched.

## Delete or archive a page

`⋯` → **Archive page**, or right-click a row in the tree and choose **Delete**.
Both do the same thing, and both **take the page's child pages with them** —
the confirmation says so.

The pages disappear from the tree and from search for everyone. There is no
restore in the app, so read the confirmation before accepting it.
