Cards

A card is the basic unit of work in Kard. This guide covers what a card holds, how to link one to objects in your level, how to relate cards to each other, and how to move and save them.

Cards are stored as standard assets inside your project’s Content folder, so they version-control alongside the rest of your project.

What a card is

A card is a single Kard asset. It carries a title, a markdown description, and a set of fields like status and priority. Cards come in three types:

Task — trackable work with a status and priority. The default card type.
Note — a sticky note. Has a color and an optional audience list.
Page — a long-form content document. Pure body text, no task fields.

A card’s type is fixed when it’s created and can’t be changed afterward — create a new card of the right type instead.

Card fields

Every card shares a common set of fields. The table below covers the ones you’ll edit or read directly. Some are type-specific (noted in the table).

Field	What it’s for
Title	The card’s name. Shows as Untitled until you set it.
Description	The markdown body — the main content of the card.
Status	Where the card sits in its folder’s workflow (default: Open → In Progress → In Review → Done). Tasks only.
Priority	How urgent: Blocker, Critical, Major, Minor, Trivial (default Major).
Assignee	Who the card is assigned to. New cards you create are assigned to you automatically.
Tags	Free-form labels for grouping and filtering. A card can have many.
Category	A single category label per card, chosen from your configured list.
Emoji	An emoji shown on sticky-note cards. Leave it blank for an auto-picked one.
Color	The sticky-note color. Notes only (default warm yellow).
Audience	Who a note is visible to — a list of handles, or the groups `team` / `all`. Empty means everyone. Notes only.
Private	Marks a note as private to its creator. Notes only.
Author / Created	Who created the card and when. Set automatically; not editable.

Cards also store internal fields used for a future cloud sync backend. These are not user-editable and are reserved for that release; you can ignore them.

Link a card to the engine

A card connects to objects in your project through contexts. A context can point at an actor, a level, a Blueprint class, or any Content Browser asset. There are two roles:

Anchor — one spatial context that decides where the card’s badge appears in the viewport. A card has at most one anchor. No anchor means the card lives on the dashboard only.
References — any number of extra contexts the card points at, with no effect on placement.

Anchor a card in the viewport

Give a card an anchor to pin its badge to a spot in your level. The fastest way is to drag.

You can anchor to a placed actor, a level, the nearest instance of an actor class, or a fixed point in a level. The Quick start guide covers creating a task directly in the viewport with Kard → Tasks → Create Task Here, which anchors it for you.

Link with wikilinks and references

Inside a card’s description you can drop three kinds of inline links:

Card-to-card link — [[Target]] or [[Target|Display text]], Obsidian-style, to point at another card.
Context link — drag an actor, asset, or Blueprint into the description and Kard inserts a context reference automatically.
Attachment — ![id] embeds an image attachment the card owns.

You rarely type these by hand. Dragging an object into the description inserts the right form for you; pasting a copied Kard link converts it into the inline reference.

For the full attachment model — where images are stored and how cards claim them — see the attachments reference once published.

Relate cards to each other

Beyond inline links, you can declare a typed relation between two cards. Relations express intent the way a tracker would:

Blocks — this card blocks the target.
Depends on — this card needs the target done first.
Duplicates — this card duplicates the target.
Relates — a loose connection.

A relation is stored on the source card only. The target automatically shows the matching incoming relation — Kard derives those backlinks for you, so you never add the reverse by hand.

Move and edit a card

Move a card to another folder

Drag a card in the sidebar to a different folder, or use the right-click Move to entry. Moving a task also reconciles its status against the destination folder’s workflow — if the current status doesn’t exist there, the card takes the destination’s first status. The whole move is a single undo step.

Spatialize or re-anchor by dragging

Drag an actor or asset onto a card’s description to give it (or change) its spatial anchor and context references, as covered above. Drops are handled generically by payload type — an actor becomes an actor context, a Blueprint becomes a class context, a texture becomes an attachment, and so on.

Edit and save

Kard uses an explicit edit-then-save model. What you see on a card is always its last saved state — your edits live in a working buffer until you commit them.

Edit the title or description in the detail panel.
Save the card with Ctrl+S or the Save button.
Press Esc to cancel an in-progress edit and revert to the saved value.

New cards start as drafts held in memory; saving writes them to disk as assets in your Content folder. Each card also keeps a short edit history of recent changes.

Next steps

Boards — folders, workflow statuses, the Board layout, and saved views.
Quick start — create your first task in a couple of minutes.
Settings — categories, folder roots, and viewport options.