Skip to content

The product

A document, a diagram, and a deck are the same thing here.

Most teams keep the words in one tool, the picture in another, and the version the executives saw in a third. Three copies of one idea, and at least two of them are wrong. DocZoid keeps one.

Docs

Write in blocks, with the canvas beside you.

Paragraphs, headings, lists, quotes. Each block is its own unit, so you can reorder, comment on, or reuse any one of them on its own. Text is stored as Markdown, so nothing you write is trapped here.

A doc can carry a diagram canvas in a resizable split view. Explain the thing on the left, draw it on the right, and stop alt-tabbing between two applications to keep one idea straight.

A doc with a canvas0:10
Containers and theming0:44

Diagrams

A real canvas, not a picture of one.

Basic shapes and flowchart symbols on a 20px snapping grid. Edges attach to anchor points on each side and render as bezier curves. Style presets for the eight states you actually use.

Containers are the part that makes a large diagram survivable. A container holds a set of shapes, gives the group a title, and themes every shape inside it at once, shading by nesting depth. Nest them for subsystems inside subsystems, and let an individual shape override the theme when it needs to stand out.

Containers in the guide

Zoids

The deck is built on the same canvas.

A Zoid is an ordered list of 16:9 slides, and each slide is a diagram canvas. Every shape, container, and connector you know from a diagram works on a slide, because it is the same canvas.

Present full screen, read-only so nothing moves by accident, and advance with the arrow keys. A Zoid is a document in your team like any other, which means it has comments, presence, and version history too.

Building and playing a Zoid1:42

PortalSnips

One object, many places, always in step.

This is the mechanism behind every claim on this site. A PortalSnip is a passage of text or a region of a canvas that you create once and insert in many places. It is a live reference, not a copy.

Creating and inserting a PortalSnip0:33

In a doc

Attached to a block, in the flow of what you are writing.

In a diagram

As a read-only node on the canvas.

In a Zoid

As a slide element, with its title and source document shown.

Owned by the team

Or marked document-only to stay private to where it came from.

Edit the source, and every reference follows. That is how a diagram regenerated from your repository ends up correcting a slide in a deck you presented last quarter.

How it is organised

Everything lives in a team.

A team owns your docs, Zoids, and PortalSnips, and decides who can see and change what.

Team
The home for everything. Owner, admin, member, viewer.
Doc
Blocks of text, optionally with a canvas.
Zoid
An ordered list of 16:9 slides.
Diagram
Nodes and edges on a canvas, inside a doc or a slide.
Container
A titled, themed group of shapes.
PortalSnip
A live reference to a passage or a region.
Structureteam → documents → content

One source. Three views. No copies.

  • Read-only repo access
  • Works with Claude Code, Cursor, Claude Desktop
  • Free for one editor