Docs spaces and project wikis
Iskue has two places for pages: Docs spaces, site-wide spaces with their own readers and editors, and project wikis, which follow the project's membership. Both use the same pages, editors, tree, history and blocks.
Docs spaces need the Professional edition (the DOCS_SPACES licence feature). Project wikis work on every edition.
Pages and the page tree
- Tree. Pages nest under each other. Drag a page to reorder it or move it under another parent, or use the keyboard. A breadcrumb shows where you are.
- History. Every save is a revision: view any revision and restore it.
- Comments on each page.
- Permanent links. Every page has a short link,
/d/<id>, that keeps working when the page is renamed or moved. Copy link puts it on your clipboard, and the address bar follows the open page. - Search across space pages, project wikis and knowledge-base articles.
Imported HTML artifacts
A page can be an imported HTML artifact — for example a report or a small interactive page made with Claude. Import it the way you create a page. It renders in a sandboxed frame, can be replaced with a newer version, keeps an optional source URL, and is searchable like any other page. A numbered source view shows the HTML.
The editors
The visual editor is the default. The page is a stack of cards: click a text card to edit it in place (paragraph, headings, lists, task lists, quotes, code; bold, italic, code and links, with Ctrl+B and Ctrl+I), or click a block card to open its settings with a live preview. Cards move up and down, and typing / in an empty text card opens the Insert block picker, which you can search by block name or by its Confluence macro name.
The Markdown editor stays available — Write / Preview, with Insert block at the cursor. Each user picks one and the choice is remembered. Both editors read and write the same Markdown, so a page moves between them freely, and blocks you did not touch keep their source byte for byte.
Blocks
Blocks are Iskue's answer to Confluence macros. They are stored as Markdown directives, so a page stays plain text:
:::info{title="Heads up"}
The release freeze starts on Friday.
:::
::tickets{query="project = CORE AND status != Done" limit=10}
Current state: :status[In review]{color=yellow}| Group | Blocks |
|---|---|
| Layout | Info, tip, note and warning callouts · panel · expand · columns · excerpt · decision · page properties · chart from a table · table of contents |
| Inline | Status · date · anchor · ticket |
| Navigation | Child pages · page tree · page index · recently updated · include page · include excerpt · spaces list · space details · saved search · change history |
| Live | TQL ticket list or count (tickets) · ticket chart by status, priority, type, assignee or project (ticket-chart) |
| Media | YouTube and Vimeo embeds; any other URL becomes a link card |
Security
- Blocks show only what the reader may see. Data blocks read the same permission-checked endpoints as the page itself: a ticket list is scoped to the reader's projects and honours restricted tickets, and a hidden ticket shows its key only, never its title.
- No HTML block and no RSS block, by design. Raw HTML in a page is an injection surface, and RSS would make the server fetch arbitrary URLs. Imported HTML artifacts, in their sandbox, cover the HTML case.
- Embeds use
youtube-nocookieand Vimeo withdnt=1, in sandboxed frames. - Includes stop on cycles and after 3 levels.
Not there yet
Compared with Confluence, these are still open: page attachments (and the file, gallery and Office blocks that depend on them), page labels (content by label, page-properties report), page templates, page favourites and watches, contributor blocks, and inline comments.