Spaces and Pages
Working with Pages
Working with Pages
Pages live in the sidebar tree. Everything you do to them starts either there or from the page’s own right rail.
Create a page
In a space, the sidebar section header reads Content and carries a + button, tooltip New content. The menu offers:
- Page
- Folder
- One entry per plugin document type installed (a Board, for example)
The Create new page dialog asks for a Page name and shows which space or folder it lands in. Press Enter or click Create.
Same dialog, other routes: the space page right rail (New page, New folder) and the New Page button in the space directory. An empty space shows Create your first page in the sidebar. There is no keyboard shortcut: ⌘ N is reserved but not wired to anything.
Inside a page or folder
Hover an item in the tree and click its + button, tooltip Add inside. The menu is the same list as New content: Page, Folder, then one entry per document type. Name the new item and it is created inside the one you opened the menu from. That item opens in the tree to show it, and the new item opens and is selected.
Add inside… in the page action menu opens the same menu.
Page action menu
Right-click any item in the tree, or hover it and click the More actions button (…). From the keyboard, focus the item and press Shift F10 or the Menu key. The arrow keys move through the menu and Escape closes it.
| Item | What it does |
|---|---|
| Rename | Turns the tree label into an editable field. Enter commits, Escape cancels. |
| Add to Favorites / Remove from Favorites | Toggles the star. |
| Duplicate | Creates a sibling copy named Title (Copy) and opens it. |
| Add inside… | Opens the add menu: a page, a folder or any document type, created inside this item. |
| Move to space… | Moves the page, and everything beneath it, to another space, in this Nexus or another one. With several rows selected it reads Move N pages to space… and moves them all. See Move pages to another space. |
| Move back to space | Only on a page you moved into your own Nexus: sends it back where it came from. |
| Open in new tab | Opens the page in a new browser tab. |
| Move to Trash | Soft-deletes the page. See Trash and Restore. |
Hovering also exposes a + button, tooltip Add inside, next to the …. It opens the same add menu.
Duplicating copies the page’s content, icon, and cover, but not its children. Duplicate a folder and you get an empty folder.
A whiteboard comes with its drawing, a Database View with its table and settings, a Board with its GitLab source, and a Requirements collection with its items, traces and allocations. The copy starts its own history: earlier versions and baselines stay with the original. Git Docs pages cannot be duplicated; add a new one and point it at the same repository.
The right rail
Open a page and a vertical toolbar sits on the right: Edit page, Chat, Version history, Watch for changes, Add to favorites, Access, Tags, and More options.
Access opens the page’s access panel: who can reach the page and at what level, the share link, and the seal. See Who can reach a page below.
More options holds Add icon / Change icon, Add cover, a Child index section (Space default, Always show, Hide on this page, plus a depth choice while the index is shown), Export, Convert to folder, and Delete.
If you can only view the page, Edit page stays in the rail but is greyed out, and its tooltip says you can view the page but not edit it. Tags is not shown, More options holds only Export, and Version history lists the versions without Restore. The sidebar tree offers the same reader Add to Favorites and Open in new tab on a row, and nothing that changes it.
The child index is the list of pages inside this one, shown below the page. To put it somewhere else, for example under an introduction and above the detail, type /child in edit mode and insert Child pages where you want it. The list then appears there instead of below the page, at the depth chosen in More options. Remove the block to put it back at the bottom.
Nesting and reordering
The tree is drag and drop. Grab the handle on the left of a row and drop it:
| Drop target | Result |
|---|---|
| Above a row | The page becomes the previous sibling. |
| Below a row | The page becomes the next sibling. |
| Onto a row | The page becomes a child of that row. |
Dropping onto a row only nests when that row is a folder or already has children. Otherwise the drop is treated as “place after”. You cannot drop a page onto its own descendant.
Click the chevron to expand or collapse a branch. Expanded state is remembered per space in your browser, and the tree auto-expands to reveal whatever page you navigate to, scrolling to its row when it is out of sight.
The tree is one stop when you press Tab. Inside it:
| Key | What it does |
|---|---|
↓ ↑ | The next or previous item |
→ | Expands a branch; on an expanded one, moves to its first item |
← | Collapses a branch; anywhere else, moves to the item it sits in |
Home End | The first or last item |
Enter | Opens the item |
A small dot beside a title means Unpublished edits.
A folder is a page with a different job: it opens a directory listing of its children instead of the editor. Add pages, folders and any other document type inside it from its row’s +, as you would anywhere else.
Move pages to another space
Choose Move to space… in a page’s menu. The Move Page dialog lists every space you can move it into, grouped by Nexus: this Nexus first, then your own Nexus, then the others. Pick one, read what the dialog says the move will do, and click Move Page. The page arrives at the top of that space with everything beneath it.
You need full access to both spaces: the one the page leaves and the one it enters. Whoever can make the trip can make it back.
Every move to another space switches off the page’s public share links, and those of everything beneath it. They cannot be restored.
Into another Nexus
When the destination is in another Nexus, the dialog also lists:
- Granted only: people who had access to these pages by name keep it, but are not members of the other Nexus, so they see only what they are granted there.
- Group access is removed: a group belongs to one Nexus, so its grants do not travel.
- Labels are removed: a label belongs to one Nexus.
- Sealed pages travel sealed: the other Nexus’s administrators will be able to read them.
- These will stop at their next fetch: Git Docs pages and boards whose connection the other Nexus is not allowed.
Three things cannot cross:
- A Requirements collection, which belongs to its Nexus.
- A sealed page, unless you administer the Nexus it is leaving. Ask an administrator of this Nexus to make the move.
- Somebody else’s own Nexus.
Your own Nexus as a workbench
Your own Nexus is somewhere only you can see. Move a few pages into it to rework them in private, then move the result back out when it is ready.
On the way in, nobody else’s access travels with the pages: the dialog lists the people and groups whose access is set aside, and your own Nexus stays private. Anyone who had one of the pages open is disconnected and cannot open it again there. Create a space in your own Nexus first if it has none; the dialog says so.
On the way out, the dialog lists that set-aside access with a box beside each. Going back to the space the access was set aside from, the box is ticked; going anywhere else, it is not. A person who is no longer a member of the Nexus you are moving into, or whose account is deactivated, is left unticked with a note saying so: tick them yourself if you mean to give them access back. Ticked access is put back as part of the move; unticked access is gone for good. A group’s access can only come back into that group’s own Nexus. If somebody is removed from a Nexus while their access to one of its pages is set aside, that access goes with the removal.
A page you moved in shows Move back to space in its menu while it sits in your Nexus. It opens the same dialog on the space it came from, puts the page back under the page it was under (when that page is still there), and has the set-aside access ticked.
Converting a page to a folder, and back
A page that has outgrown itself — a short introduction with the real material in sub-pages — can become a folder: open it and choose Convert to folder from the right rail’s More options menu.
- If the page has content, it moves to a page with the same name inside the new folder, keeping its history, comments, attachments, labels, watchers and links — anything that pointed at the page still opens the same content. Its sub-pages move into the folder beside it.
- If the page is empty (and has no unpublished edits), the node itself simply becomes a folder. Nothing is created.
The reverse lives on the folder view’s More options menu as Convert to page. A folder that holds only the page it was made from gives that page its place back, undoing the conversion exactly. Any other folder becomes a page with an empty body, and everything inside it stays inside.
Making a folder a space
A folder that has grown into a subject of its own can become a space in the same Nexus. Right-click the folder in the sidebar, or open its More options menu, and choose Make it a space…. The entry appears when you hold full access on the space and are a member of the Nexus.
The dialog says what will happen before anything does:
- The new space takes the folder’s name, icon and cover, and holds every page that was in the folder, including any in the Trash. The folder’s sub-pages become the top level of the space. Page addresses do not change.
- Who can open the space. A sealed folder gives the space its own access list, so nobody else in the Nexus gets in by default. Any other folder gives the space the access list and the Everyone level of the space it was in, so the same people can open it. You are added with full access either way.
- What changes for people, by name: who gets less access and who gets more.
- People watching the folder watch the space instead, and the folder’s primer becomes the space’s. Favorites of the folder are removed, because a space cannot be a favorite.
A folder that carries comments, a comment conversation, labels, a share link, tasks or properties of its own cannot become a space; the dialog lists what to remove first. The folder’s old address leads to the new space.
Renaming
From a space or folder directory, right-click a card (or open its menu) and choose Rename to open Edit page. It carries the Page name field; Save changes commits. The Delete button at the bottom left moves the page to Trash.
Who can reach a page
The page’s Access button in the right rail, and Access on a page, folder or database card’s menu, open the same panel. Anybody who can open the page can read it; changing anything needs full access on the space or administering the nexus.
Every row says who reaches the page, at what level, and why (the small chip beside the level opens the reason):
- Admins of the nexus, one row, expandable to their names.
- Everyone via the space: what every member of the nexus gets on this page through its space. The level is the space’s; clicking the row opens the space’s own panel.
- Each grant on the page, a person or a group, with the level, who granted it, its expiry, and a remove glyph. A person who is not a member of the nexus is marked Granted only.
- Anyone with the link: the share link, off or on. See Sharing Pages. The row is absent when an administrator has turned public links off.
- Only people listed here can see this page: the seal. When it is on, the space’s ordinary rules no longer reach the page: only the people listed on it, the admins of the nexus, and whoever holds full access on the space can open it, and the last two are recorded when they do. The sentence under the switch says exactly that. A sealed page carries a lock beside its title.
Give access at the bottom adds a person or a group at a level, with an optional expiry. Typing a colleague’s name finds them; somebody outside your nexuses is found by their exact username or email, and their row reads Granted only.
A refusal is printed beside the control you pressed, in the server’s words.
Page URLs
Pages use a hybrid URL, /p/{title-slug}-{shortId}, for example /p/welcome-to-docu-nexus-184f94aa.
The slug is cosmetic. The trailing 8 characters are the stable identifier, so renaming a page never breaks a link. Folders use /folder/{id}, and the older /page/{id} form still works. A folder link to something that is now a page opens the page.