Your team already has all the answers,
the only thing missing is a way to find them
Pages
55 pagesDraft
Published
Under Review
Every document, connected to the work behind it
Mosic doesn't just give you a rich text editor. It gives every page a home inside your workspace, linked to the tasks, projects, deals, and people it's about, so knowledge isn't just written, it's found.
How it works
Set up your team's knowledge, write in a block editor that stays out of your way, manage documents that connect to the work, and share with anyone inside or outside your team.
Set up your team's knowledge base in ten minutes
Create pages inside any workspace, organize with categories and types, nest child pages under parents, pin the important ones. Your team's knowledge base grows naturally because every page lives next to the work it describes.
- 20 page types with icons and auto-generated identifiers
- Categories for topical grouping with custom icons and colors
- Parent-child tree with expand/collapse navigation
- Pin important pages so they are always one click away
Write once, find it forever
The block editor stays out of your way: paragraphs, headings, lists, checklists, code blocks, tables, images, quotes, and more. Auto-save means you never lose work. Content outline generates from your headings. Focus mode removes distractions. Revisions track every change so you can restore any version.
- 14 block types with full formatting toolbar
- Auto-save with revision history and one-click restore
- Content outline auto-generated from headings H1 through H3
- Focus mode for distraction-free writing
Knowledge that travels with the work
Pages don't live in a vacuum. A PRD links to the project and every task it spawns. A meeting note connects to the deal and the contacts in the room. CRM notes are just pages with a type. Your team finds what they need because documents are connected to the work behind them, not filed in a folder by month.
- Pages linked to tasks, projects, deals, tickets, and contacts via relations
- CRM notes are pages: create, edit, and read them from any entity
- @mentions in page content auto-link to mentioned documents
- Reading time and word count calculated automatically
One editor, everywhere your team writes
Task descriptions use the same block editor as pages. Project descriptions too. Your team doesn't switch between a rich editor for docs and a plain text field for tasks. They write in the same tool, with the same blocks, everywhere. Knowledge from a project spec flows into task descriptions. Meeting notes become task context. Everything connects.
- Same block editor in pages, task descriptions, and project descriptions
- Mentions and links auto-create relations between documents
- Portal customers see shared pages with the same rich formatting
- Export any page as Markdown, HTML, PDF, or plain text
Start building pages that connect to everything your team needs
Give your team a knowledge base that lives inside the workspace, connected to every task, project, and deal. Free to start, no credit card required.
See how each piece works
Every feature has a job. Here's what it does, why it matters, and how it fits into your team's day.
Block Editor: Write without friction
You open a new page and start typing. Paragraphs, headings, numbered lists, checklists. Need a table? Two clicks. A code block? One. Images upload inline with captions. The editor generates a content outline from your headings automatically, so you see the structure of your document while you write. Auto-save fires every thirty seconds. If you close the tab, your work is there when you come back. Made a mess? Open the revision history, pick any version, and restore it in one click. Focus mode strips away the sidebar, the tabs, everything except your words. Full-screen takes even the browser chrome away. Your team writes in the same block editor everywhere: pages, task descriptions, project descriptions. Same toolbar, same blocks, same experience.
What's inside
- 14 block types: paragraphs, headings, lists, checklists, code, tables, images, quotes, and more
- Auto-save every 30 seconds with full revision history and one-click restore
- Content outline auto-generated from H1 through H3 headings
- Focus mode and full-screen mode for distraction-free writing
Page Hierarchy: Your knowledge has a structure
You write a product spec. Under it, you nest the feature specs for search, notifications, and billing. Under each feature, the individual task specs. Your page tree grows as your project grows, and the tree navigation in the sidebar shows the whole thing: expand all, collapse all, or scope it to just the current branch. Click any node and you're there. Breadcrumbs at the top track where you are. Add a sub-page from any level without leaving the page you're on. When a project ships, archive the parent and every child goes with it. Your team doesn't scroll through a flat list of 200 pages. They open the tree, find the branch, and they're three clicks from anything.
What's inside
- Parent-child tree navigation in the sidebar with expand and collapse controls
- Scope to current tree: see only the branch you are working in
- Breadcrumbs track your position in the hierarchy
- Archive a parent page and every child page archives with it
Page Types: Every document knows what it is
Right now your team has documents in folders with names like "Q3 Planning (FINAL v2).docx." Nobody knows if it's a proposal, a spec, or meeting notes without opening it. Mosic gives every page a type with its own icon and color: Document, Note, Wiki, Knowledge Article, Proposal, PRD, Spec, Decision Log, Research, Agenda, Meeting Notes, Retrospective, Status Report, Changelog, Runbook, SOP, Policy, and more. Twenty types, each with an auto-generated identifier: PRD-1, WIKI-3, RUN-5. Your team filters by type in the list view, groups by type in the board view, and searches by identifier. A new hire opens the workspace and sees the difference between a runbook and a retrospective without asking anyone.
What's inside
- 20 page types with unique icons, colors, and auto-generated identifiers like PRD-1 and WIKI-3
- Filter by type in list view, group by type in board view
- Types inherit to child pages automatically: nest specs under a PRD and they share the prefix
- Search by identifier: type three letters and find the exact document
Templates: Start from done
Your support team writes the same knowledge article structure every time: Problem, Steps to Reproduce, Solution, Affected Systems. Your product team starts every PRD with Overview, Goals, Requirements, Open Questions. Instead of copying from an old doc and forgetting to change the title, mark any page as a template. Next time someone needs a PRD, they pick it from the template list and Mosic clones the content into a fresh Draft. The title gets a (Copy) suffix so you never confuse the template with the real thing. Categories and types carry over. After six months, your team has 15 templates and onboarding a new writer takes ten minutes instead of two hours of "here's how we structure things."
What's inside
- Mark any page as a template with one click, unmark it just as fast
- Clone from template: content, structure, and type carry over, status resets to Draft
- Templates show up in the creation dialog, searchable and organized
- Use built-in types as starting points: Wiki, Runbook, SOP, Proposal, and more
Relations: Pages that know what they are about
A product manager writes a PRD. She links it to the project and every task the PRD spawns. A support agent writes a knowledge article. It links to the ticket that prompted it and the product area it covers. A sales rep jots meeting notes after a call. Those notes link to the deal, the contact, and the organization. Every page in Mosic connects to the work behind it through relations. Open a task and you see every page linked to it. Open a project and the pages tab shows the specs, the notes, and the runbooks. Open a CRM contact and the notes section shows every page your team wrote about that client. @mention a task inside a page and the relation creates itself automatically. Your team doesn't search for context. Context is already there.
What's inside
- Pages link to tasks, projects, task lists, deals, tickets, contacts, and organizations
- See every linked page from the entity: project pages, task pages, contact notes
- @mentions in page content auto-create relations to mentioned documents
- Bidirectional: see outgoing links (pages you link to) and incoming links (pages linking to you)
Same Editor Everywhere: One writing experience across your workspace
Your team writes task descriptions, project descriptions, and pages. In most tools, those are three different editors with three different capabilities. Not in Mosic. Task descriptions use the same rich block editor as pages. Project descriptions do too. The same toolbar, the same 14 block types, the same auto-save, the same revision history. This means a product manager can write a rich spec in the project description with headings, tables, and code blocks, and the team sees it fully formatted right where the work happens. A developer can write a detailed task description with checklists, images, and inline steps. Copy from a page into a task description and the formatting survives. Your team learns one editor and uses it everywhere.
What's inside
- Rich block editor in pages, task descriptions, and project descriptions
- Same 14 block types, same toolbar, same auto-save behavior everywhere
- Rich formatting in task and project descriptions, not just in pages
- Copy formatted content between pages, tasks, and projects without losing structure
Portal Knowledge Base: Share what your customers need
Your support team has written 80 knowledge articles. Right now they live in a help center tool your customers barely visit. Publish those pages in Mosic and they appear in your customer portal, searchable, with cover images, reading time, and the same rich formatting your team sees. Customers browse the pages section, search by keyword, and open any article. They see the same content, the same headings, the same code blocks, the same tables. Share a page explicitly with a specific customer, or link it to a project they have access to, and it shows up in their portal automatically. Mark a page as hidden from portal and it stays internal. Your team writes once. Customers find answers themselves. Ticket volume goes down.
What's inside
- Published pages appear in the customer portal with search and pagination
- Share pages explicitly with specific customers or link them to portal-accessible projects
- Customers see the same rich formatting: headings, tables, code blocks, images
- Hide internal pages from the portal with a single toggle
Export & Sharing: Your content, in any format
You need to send a spec to a client who doesn't use Mosic. Export as PDF and attach it. You want to publish a runbook on your developer wiki. Export as Markdown and paste it in. You need to email a proposal. Export as HTML with embedded styling, or copy the page as Markdown directly to your clipboard. Four export formats cover every use case: Markdown for technical docs, HTML for web publishing, plain text for simple sharing, PDF for formal documents. Each export includes your page title and metadata. The share dialog gives you a direct link, an email shortcut, and a one-click Markdown copy button. Your content is never trapped inside Mosic. It's yours, in any format you need, whenever you need it.
What's inside
- Four export formats: Markdown, HTML, plain text, and PDF via print dialog
- Share dialog with direct link, email shortcut, and clipboard Markdown copy
- Metadata included in exports: title, date, source link
- Image URLs converted to absolute paths for external use
See it in action
Real scenarios teams run every day with Mosic Pages.
The PRD that stayed alive
A product team of six manages three active projects. Before Mosic, their PRDs lived in Google Docs, detached from the tasks they spawned. When requirements changed, someone updated the doc, but half the team still worked from the old version. After Mosic, they write the PRD as a page inside the project.
- 1Create a PRD page inside the product project, type set to PRD, identifier auto-generated as PRD-1
- 2Nest feature spec pages underneath: Search gets PRD-2, Notifications gets PRD-3, each one a child page
- 3Link the PRD to the project and individual tasks via relations, so every task page shows the spec
- 4Set status to Published, the whole team sees it in the tree navigation on the left
- 5When requirements change, update the page, the revision history tracks what changed, the outline updates
The answers were already written
A marketing team of eight manages campaigns for twelve clients. Every campaign has a brief, a proposal, brand guidelines, and meeting notes. Those documents live in email attachments, chat threads, shared links, and folders on individual laptops. When someone needs the latest brand guidelines, they ask in chat, wait for a reply, get three different versions, and pick the one that looks newest. They spend three hours a week just looking for documents they know exist.
- 1Create a client project in Mosic, add campaign pages with type set to Proposal, Brief, or Creative Brief
- 2Write brand guidelines as a page inside the project, linked to the campaign and the client deal via relations
- 3After every client call, create meeting notes and connect them to the project, the deal, and the contact
- 4The team sees every document in the page tree, organized under each campaign, always the current version
- 5A new team member joins, opens the project, and finds every document without asking anyone
One spec, fifty tasks, zero copy-paste
A consulting firm delivers software for eight clients. Each project starts with a technical spec that the project manager writes as a Mosic page. Tasks are created from the spec, and the spec lives inside the project where the team, and the client through the portal, can always find it.
- 1Project manager creates a Spec page inside the client project, writes the full technical spec with the block editor
- 2Developers create tasks from the spec: task descriptions use the same block editor, they copy relevant sections directly
- 3The spec page links to all fifty tasks via relations, visible in the pages tab on the project
- 4Client sees the spec in their portal, alongside the project progress and task list
- 5When the spec changes, the PM updates the page, revision history tracks the delta, and the client sees the latest version
Your team already writes the docs. Give them a place that actually connects.
Pages, specs, meeting notes, and runbooks inside your workspace. Linked to the work, shared with customers, exported in any format. Free to start.