PortalSnips

A PortalSnip is a reusable piece of content that you create once and insert in many places. When you update the original, every place that uses it updates too — so the same diagram or passage of text never drifts out of sync across your docs and presentations.

Think of a PortalSnip as a live "portal" to a snippet of content, rather than a copy-paste that immediately goes stale.

Two kinds of snip

Where they live

PortalSnips belong to the Team, which means they can be shared and reused across all of that team's docs, diagrams, and presentations.

A snip can also be marked document-only, in which case it stays private to its source document instead of being offered team-wide.

Creating a PortalSnip

Use Create PortalSnip ("Add a new PortalSnip") in the editor:

• From a Diagram — select the region you want to capture; the snip stores that bounding box.
• From a Doc — capture the text content you want to reuse.

When a snip is created, Doczoid stores its content along with a cached image of how it renders, so it can be inserted quickly elsewhere. The snip is tied to its source document, and can be locked to a specific version of that document.

Inserting a PortalSnip

Use Insert PortalSnip ("Insert a PortalSnip") in any doc, diagram, or presentation slide. The snip appears at the insertion point:

• In a Doc, it attaches to a block.
• In a Diagram or Zoid slide, it appears as a node (a read-only image of the snip).

Each place you insert a snip creates a reference back to the original. That's what keeps everything connected.

Live updates

This is the point of PortalSnips: edit the source, and every reference follows.

When the original content changes, the snip's cached rendering is refreshed and propagated to all the docs, diagrams, and slides that reference it. You maintain one source of truth and let it flow everywhere it's needed.

Inserted snips in presentations

When a PortalSnip is placed on a Zoid slide, it shows as a read-only element. Its menu displays the snip's title and the source document it came from, with quick actions to:

• Edit the source (jump to where the snip is defined), or
• Remove the snip from the slide.

When to reach for a PortalSnip

• A diagram (architecture, flow, legend) that appears in several docs and decks — define it once, reuse it everywhere.
• A standard passage (a disclaimer, a definition, boilerplate) that must read identically across documents.
• Anything you find yourself copying and updating in multiple places — that's the signal to make it a snip instead.

Tips

• Lock a snip to a document version when you want a stable reference that won't change even as the source keeps evolving.
• Use document-only snips for content you want to reuse within a single document but not expose to the whole team.
• Combine snips with Containers: capture a themed, titled container as a diagram snip and reuse that whole labeled group across slides.

Related

• Diagrams and Docs — where snips are created and inserted.
• Containers — capture a whole themed group as a snip.
• Collaboration — version locking keeps snips stable.