Productivity

Docs & Wiki Workspace

A block-based docs + wiki workspace: nested pages, rich blocks, real-time collaboration, permissions, search, and sharing.

Full planning bundle — BRAND, MRD, BRD, PRD, DESIGN
Branded styleguide — typography, color, components
5 previewable mockups

Cloning copies the full plan into a new project you own — edit it freely.

Inside the bundle

Styleguide and mockups

A look at the brand palette and screen-level mockups that ship with this plan. Cloning copies all of them into your project.

Mockups

Style guide

Styleguide

What this blueprint gives you

The modular “blocks + nested pages” knowledge-workspace model: a document is a tree of typed blocks, pages nest infinitely, teams collaborate in real time with granular permissions and fast search — captured as an ownable, build-ready plan.

Five planning documents (BRAND, MRD, BRD, PRD, DESIGN) at senior depth.

Planning documents

Preview the plan

Each blueprint includes the senior-level planning files. These cards show the opening text before you clone the full bundle.

Brand Guidelines Document

BRAND.md

Preview

BRAND — Docs & Wiki Workspace One line One place for everything a team knows — written as blocks, organized as pages. Who it speaks to Teams drowning in scattered docs, wikis, and notes: startups, ops teams, agencies, communities. They want a single, fast, structured home for knowledge that's easy to write and easy to find later. Voice & tone Clear and structural. The product is about structure; the copy is well organized and spare. Calm productivity. No hustle theatrics — "find what you wrote i

Design Specification Document

DESIGN.md

Preview

DESIGN — Docs & Wiki Workspace Information architecture App shell: left sidebar (workspace switcher, page tree, search, shared with me, trash) | center page editor | optional right pane (comments / history / page info & access). Settings: profile/notifications; workspace admin (members, roles, audit, retention, export, ownership). Public: shared/public page view (read or comment), no app chrome. Key screens & layout Editor: centered document column (comfortable measure); blocks with hover handle

Market Requirements Document

MRD.md

Preview

MRD — Docs & Wiki Workspace The problem Team knowledge is scattered across docs, chat, wikis, and notes apps. It's hard to write consistently, harder to find later, and risky to edit together (collisions, lost work). Teams want one structured, fast, collaborative home for knowledge with real permissions and history — ownable, not just rented. Who it's for Primary — the team contributor. Writes/reads docs, specs, notes, runbooks daily. Wants a fast block editor, easy structure, instant search, no

Business Requirements Document

BRD.md

Preview

BRD — Docs & Wiki Workspace Business outcomes 1. Active knowledge use. Weekly active contributors + reads/searches per workspace — the asset's value. 2. Activation & retention. Workspace reaches "knowledge home" status (≥N pages, ≥N contributors, regular search) within 2–3 weeks; workspace retention. 3. Collaboration trust. Zero reported lost edits; convergence correctness — the credibility of the whole product. 4. Stickiness. Page tree depth + cross links + integrations correlate with retention

Product Requirements Document

PRD.md

Preview

PRD — Docs & Wiki Workspace Phase 0 — Workspace, identity, model Auth + roles: workspace owner , admin , member , guest . Data model: page = ordered tree of typed blocks; pages nest (parent→children); workspace owns the root tree. Sync foundation: real time service (CRDT/OT) + websocket; document load/save; offline op queue scaffold. Acceptance: a workspace exists with a root page tree; a block edit persists and reloads identically; the sync channel is established with presence. Phase 1 — Editor