Core concepts

Renza models a small set of objects. Learn these five and the rest of the docs read easily.

Deck

A deck is the durable document — the thing you name, share, and permission. It's the unit of value: a self-contained, interactive document with persisted state, not a static .html file.

A deck is the first document type in an extensible system. Today a deck is a sequence of slides; the architecture treats "deck" as one type among future ones (a report is sections, a one-pager is a single surface). When you share a link or set a role, you're acting on the deck.

A deck carries a lifecycle status that maps to the everyday loop:

Artifact

An artifact is one concrete version of a deck's content — the actual HTML (or HTML bundle) you imported. Re-import to the same deck and you add a new artifact; the deck's current artifact advances while every prior one is kept. This is what makes version history a ledger rather than a black box.

The artifact is served from an isolated content origin, never the app origin — see Security.

Slide

Renza parses an artifact into slides using the slide contract — the conventions that mark where one slide ends and the next begins (data-renza-slide on each section, or a deck that ships its own chrome which Renza detects and adapts to). Slides give you present mode, thumbnails, keyboard navigation, and a stable target for comments.

Share

A share is a token that grants link-based access to a deck — either link (anyone with the link) or public. Shared decks carry the "Shared with Renza" badge until removed on a paid plan. Shares are the distribution surface; see Sharing & permissions.

Grant

A grant gives a specific principal — a user, an email, or a group — a role on a deck or folder: viewer, commenter, or editor. Grants are how access is set per-person, in the Drive-style share dialog. The effective role a person has is computed from the grants that apply to them.

How they fit together

Org
 └─ Folder
     └─ Deck            (the document — named, permissioned, lifecycle status)
         ├─ Artifact    (a version of the content — the imported HTML)
         │   └─ Slide   (parsed sections — present mode, thumbnails, comment targets)
         ├─ Share       (link / public access tokens)
         ├─ Grant       (per-principal roles: viewer / commenter / editor)
         └─ Comment     (anchored to a slide, threaded, resolvable)

Everything lives inside an org (a workspace). A user can belong to multiple orgs; the active org scopes what you see and act on.