Document workspace

Polytrail

A calm writing and knowledge workspace: browse a folder of documents, edit them in tabs with real formatting, and keep an AI writing assistant beside the page it can see.

Loading Board demo

Document Workspace

A calm place for the notes your team actually reads: browse a folder of documents, edit them in tabs with real formatting, and keep an AI writing assistant beside the page that already knows which document you have open.

If you have ever written something in a chat window and then hunted for it a week later, this is the other way round: the document is the thing you keep, and the assistant works on it with you.

Where to take it next

It is a small, complete writing workspace, so it grows in whatever direction your knowledge base needs:

  • Make it your handbook. Shape the folders like your team thinks: a Handbook, a Meetings folder dated by week, a Research folder for the comparisons you keep redoing. The welcome page that comes with it is meant to be replaced.
  • Give every new note a shape. Documents start empty today; add a starting skeleton per type — a meeting note with attendees, agenda and decisions, or a decision record with context and alternatives — and nothing arrives as a blank page.
  • Turn it into a publishing pipeline. Markdown already exports to a standalone HTML page. Point a scheduled routine at a Published folder and you have a blog with drafts, or a help centre that rebuilds itself.
  • Use it as your second brain. Because the assistant works on the same folder you do, you can ask it to file a note away, split a long page, or turn a transcript into a summary — and the result is a file, not another chat log.
  • Make it a documentation site. The left column already lists everything; add a table of contents beside the page and it reads like a docs site.

What to reuse in your own board

Each of these stands alone:

  • A document surface that is not an IDE. Markdown with tables, checklists, math and diagrams, plain text with syntax highlighting, HTML previews and media previews — one viewer that decides how to show a file instead of asking the user.
  • Tabs that survive a reload. The open documents and the one you were reading are remembered, so it always reopens where you left it. A small touch, and it changes how the tool feels.
  • An editor that keeps up. Opening, saving, renaming, moving and creating each land in a single step, with whatever you were typing flushed along the way, so the page never lags behind you even when the folder lives somewhere else.
  • Files that can change underneath you. Edit a file on disk, or let an agent edit it, and the open document refreshes itself, tells you when it changed, and refuses to silently overwrite your unsaved edits. This is the part most editors get wrong.
  • An assistant with the right scope. The chat knows which document is open rather than having its text pasted in, is told to edit files directly instead of printing replacements, and pauses your cursor while it writes.

How to use it

  • Browse and organize on the left. New document, new folder, drag to move, right-click to rename or delete, and the search box filters as you type.
  • Write in the middle. Markdown opens as a formatted document; type / for headings, lists, tables, code and images. Other text files open as highlighted source. HTML, images, PDFs, audio and video get a preview instead of an editor.
  • Switch documents with tabs. Each tab keeps its own draft and reading position. Closing a tab saves it first.
  • Ask the assistant on the right. It sees the document you have open, so "cut the intro in half" applies to the page in front of you. While it writes, the editor is read-only so you cannot overwrite each other.
  • Save happens shortly after you stop typing; Cmd/Ctrl+S saves immediately. If a file changes on disk while you have unsaved edits, a notice lets you reload or keep yours.
  • Export HTML turns the current Markdown document into a standalone page next to it, with math and diagrams already rendered.

Good to know

  • The workspace is a plain folder. Any file you drop into it shows up here, and everything you write stays readable Markdown.
  • The assistant needs no setup beyond the board itself. It works on this folder and nothing else.
  • Your documents are just files, so moving to another tool means copying a folder.