---
title: Drafts and review
description: Drafts keep proposed design work off the mainline until the owner accepts it. Review one in the viewer, inspect and copy its elements, and resolve conflicts.
section: platform
order: 2.5
featured: false
related: platform/projects, solutions/ship-to-code, platform/collaboration
---

# Drafts and review

A draft is a proposed version of a project that has not landed yet: the pull request of the design world. It is a branch of work kept off the mainline until someone with the keys accepts it.

## What is a draft?

A draft is a named branch of your project, started from a checkpoint or from the latest mainline. Edits on a draft never change what visitors see on the mainline. Drafts usually come from an agent or a tool working against your project.

| State | Means |
|---|---|
| Draft | Being worked on. Where a draft starts |
| In review | Submitted, waiting for the owner to accept or send it back |
| Accepted | Merged into the mainline as a new checkpoint |

The list of drafts is public: anyone who can see the project can see its open drafts, each with its state and how many checkpoints it is ahead. A project row shows its open-draft count next to its other stats.

## What does the draft viewer show?

A draft opens at brilliant.design/{handle}/{project}/draft/{name} in three panes.

| Pane | What it holds |
|---|---|
| Left: Canvases | Every canvas as a flat jump list, grouped by folder |
| Center: the canvas | Rendered live on WebGPU and fit to the frame. Click any element to select it. Without WebGPU you get a static snapshot |
| Right: the inspector | Read-only properties of your selection, and the tools to copy it out |

The header carries the breadcrumb, a Draft or In review badge, a switcher between the mainline and other drafts, and a History link. On a narrow window the viewer steps aside with a note, and a phone or tablet opens the touch-friendly read-only viewer instead.

## What can I inspect?

Everything an element is made of, every value ready to copy: name and type, position and size, corner radius, text and its font, fills, strokes, effects, and the design token each property is bound to. With nothing selected, the inspector summarizes the canvas. Link to this element copies a URL that lands a teammate exactly where you are.

## How do I copy an element out?

Use Copy as in the inspector. It copies the selected element and everything inside it.

| Format | What you get |
|---|---|
| Blueprint | Brilliant's own compact language ([The Blueprint DSL](/docs/developers/blueprint)). Paste it into your project to recreate the element exactly |
| React | JSX with inline style objects, ready for a .tsx file |
| HTML | Markup plus inline CSS |
| SVG | The vector graphic |

This is why a view-only visitor can walk away with any piece of a public design: you can't change the owner's work, but you can copy it into your own.

## How does the owner review a draft?

The owner sees three controls in the draft header. Everyone else gets the read-only viewer.

| Control | What it does |
|---|---|
| Submit | Sends an active draft in for review |
| Withdraw | Pulls it back to keep working |
| Accept | Merges it into the mainline as a new checkpoint, and drops you into the mainline editor. If it overlaps mainline changes made since it branched, the resolver opens |

## How do I resolve a conflict?

The resolver shows each conflicted canvas side by side: Mine, the mainline, and Theirs, the draft. Elements that differ are highlighted on both sides, and a panel lists every one with a running count.

<DocStep n="1" title="Pick a side for each element.">

Mine keeps the mainline's version, Theirs takes the draft's, and Both keeps them both. Take entire Mine or Take entire Theirs decides a whole canvas in one move. Several conflicted canvases show as tabs.

</DocStep>

<DocStep n="2" title="Press Confirm & accept.">

It writes your merged result as a new checkpoint and accepts the draft. That write is a real, published checkpoint, so Brilliant asks you to confirm, and it can't be undone.

</DocStep>

Two guardrails sit behind the merge. If either version of a canvas fails to load, the resolver stops and tells you. And a resolution that would empty a canvas that holds elements is refused outright.

## Where next?

- **Publish and mark versions:** [Publish a project](/docs/platform/projects).
- **Work with other people:** [Collaborate live](/docs/platform/collaboration).
- **Take a design into code:** [Import and export](/docs/workspace/import-and-export).
