Pages and files
Write pages in markdown-safe blocks, bring files in, take pages out, and keep translations honest.
A project’s knowledge base is its Documents: pages written in a block editor limited to blocks that round-trip through markdown. Markdown is what your assistant reads and what it writes back, so its edit comes as a clean diff rather than a reshuffled page.
Writing a page
Choose New document, or start from one of the project’s Templates. The editor has a slash menu and a small, deliberate set of blocks — headings, paragraphs, lists and checklists, quotes, code blocks, tables, images and dividers — every one of which survives a round trip through markdown. Paste markdown and it becomes blocks; copy blocks out and they are markdown again.
- A Mermaid code block renders as a diagram on the page; the diff stays readable text.
- Comments attach to the page or to a passage of it. Commenting on a page watches it, so later changes reach your Inbox.
- Pin a document to keep it in your own pinned group above the document tree. Pins are personal; other members see their own.
- Every page keeps its revision History: compare any two revisions, revert to an earlier one (a new revision, nothing rewritten), and see which channel each revision came through.
The project’s Guidance is a page too — the instructions your assistants and agents read before they work in the project.
Bringing files in
Upload a file and Rindo turns it into a page, with the original attached as its source:
| You upload | What happens |
|---|---|
| Markdown, HTML, plain text | the content becomes the page’s first revision |
| Word (DOCX) | the text, with embedded images placed where they were |
| Excel (XLSX) and CSV | each sheet becomes its own page: table regions as labelled record lines, the rest as layout flow; a cell’s comments become a trailing Comments section of text |
| PowerPoint (PPTX) | the slides’ text in reading order, images placed at their anchors |
| the text layer; the original previews in the browser |
The import runs in the background and records what it could not carry over — images skipped, content truncated: shown in Sources when an import fails, kept in the project’s audit trail when it succeeds. A changed file uploaded again arrives as a new page; only the identical file, read differently by a newer extraction, appends a revision to the existing one.
Files that arrive this way sit in Sources until you Promote one into the document tree; a failed import shows there too, with Re-trigger.
A scanned PDF, or any file that arrives with no readable text, offers Request conversion: a converter agent — a program you run like a runner, with your own model — reads the pages as pictures, and the result arrives as a pending draft a person approves. Ask us about it at hello@rindo.io.
Bringing a folder in
Import… a .zip of a markdown folder — a Notion, Confluence or Obsidian export — and its folders become nested pages, previewed before anything is written.
Taking pages out
Every page except Guidance exports as Markdown, PDF or Word; the export follows the language you are reading, and the PDF embeds its fonts. A project’s Owner can also export the whole project as a file, from the project’s general settings.
Translations
A page has one source language and may have a translation per language the project enables — English, Japanese, Vietnamese, Korean — each with its own revision history, drafts and approval. Rindo does not translate: a translator agent, or your own assistant, proposes the translation as a draft a person approves.
When the source changes after a translation was made, that translation is flagged Outdated on its own, on the language switcher and in lists, with a one-click request for a new one. Readers switch language in the page header; what you see falls back from your preferred language to the project’s primary language to the source.