---
title: Slide layouts and themes
description: The thirteen slide layouts and their slots, the built-in themes, how to set your organisation's own colours, fonts, logo and corner radius once, one artifact's own tweaks, and themed HTML pages.
section: studio
order: 30
audience: [user, operator, builder, agent]
sources: [services/nodejs-cloud/lib/studio/layouts.ts, services/nodejs-cloud/lib/studio/themes.ts, services/nodejs-cloud/lib/studio/html-kit.ts, services/nodejs-cloud/components/studio/TweaksPanel.tsx, services/nodejs-cloud/migrations/0363_studio_artifact_tweaks.sql]
features: []
---

## Layouts

A slide is `{ "layout": "...", "content": { slot: value }, "notes": "..." }`. Each layout has named slots; `*` marks the
required ones. Venom draws the slide; nobody positions anything.

| Layout | Slots |
|---|---|
| `title` | `title`*, `subtitle`, `meta` |
| `section` | `title`*, `subtitle` |
| `bullets` | `title`*, `bullets`* (up to 8) |
| `two_column` | `title`, `left`*, `right`* (blocks) |
| `big_number` | `title`, `value`*, `label`*, `delta`, `good` (`"up"` or `"down"`: which direction of the change is good news; default `"up"`), `note` |
| `chart` | `title`, `chart`* (a chart, diagram, table, stats or image block), `caption` |
| `image_left`, `image_right` | `title`, `image`* (an image block), `body`* (blocks) |
| `quote` | `quote`*, `by` |
| `comparison` | `title`, `left`*, `right`* (each `{ "heading": "...", "points": [...] }`) |
| `timeline` | `title`, `timeline`* (a timeline or gantt block) |
| `table` | `title`, `table`* (a table, comparison or stats block), `caption` |
| `closing` | `title`*, `subtitle`, `contact` |

```json
{ "layout": "big_number", "content": { "value": "$4.2M", "label": "Annual recurring revenue", "delta": "+12% vs last year" } }
```

Slides are 16:9 and scale with the space they are shown in, so a thumbnail, a full-screen present and a printed page are the same
slide. `studio_layout_get` returns every layout with its slots and an example.

Content slides put their title at the top left and let the chart, table or columns fill the rest. The title slide sets its title
large at the lower left with the meta line under a rule; a section slide is filled with the theme's accent; the closing slide is
centred, with the contact as a pill.

## Themes

A theme is stored once per organisation and applied when an artifact is drawn. Four are built in: `venom` (light and dark, follows
the viewer), `midnight` (dark), `paper` (a warm serif) and `mono` (high contrast). An artifact names a theme, or follows the
organisation's default.

An org owner or admin makes their own with `studio_theme_set` (or the console's theme page):

```json
{
  "name": "Acme",
  "colors": { "bg": "#ffffff", "text": "#1b1b1b", "accent": "#d9480f" },
  "fonts": { "heading": "serif" },
  "radius": 6,
  "logo": { "src": "https://example.com/logo.png", "alt": "Acme" }
}
```

You give three colours; Venom derives the rest (surfaces, borders, the eight chart colours). Colours must stay readable: text and
muted text need a 4.5:1 contrast against the background and the accent 3:1, and a theme that fails is refused with the ratio.
Chart colours are picked from a colour-blind-safe palette and adjusted until each has 3:1 contrast on your background, so a chart
cannot come out unreadable. For a theme that follows the viewer's light or dark setting, set `"mode": "auto"` and give a `dark` palette.

Fonts are the system stacks `sans`, `serif`, `rounded` and `mono`. Nothing is downloaded, so a theme works offline. A logo is an
`https` image or a small `data:` image, shown on title and closing slides. Radius is 0 to 24 px.

## Tweaks

One artifact can look a little different from its theme without anyone changing the theme. Its tweaks are stored with the
artifact (and with each version, so a restore brings them back) and applied on top of its theme wherever it is drawn: the console,
public links, present, print, thumbnails and themed HTML pages.

| Tweak | Values |
|---|---|
| `accent` | `#rrggbb`, at least 3:1 contrast against the theme's background (both backgrounds for a theme that follows the viewer) |
| `font` | `sans`, `serif`, `rounded` or `mono`: the body text, and the headings unless `heading_font` is set |
| `heading_font` | the same four |
| `radius` | 0 to 24 px |
| `density` | `compact`, `normal` (the theme's spacing) or `roomy`: the gaps, paddings and space between blocks |

In the editor, **Tweaks** opens a panel with an accent picker, the two fonts, a radius slider and the spacing. The preview changes
as you move them; **Save tweaks** writes a version, **Discard** drops the draft and **Reset to the theme** clears them. An agent
does the same with `studio_artifact_update` (`tweaks`, or `null` to clear; it replaces the previous tweaks) or passes `tweaks` to
`studio_artifact_create`:

```json
{ "id": "0190...", "tweaks": { "accent": "#0f766e", "font": "sans", "radius": 16, "density": "roomy" }, "expect_version": 4 }
```

An accent that is not readable is refused with its ratio. If the artifact later moves to a theme on which the accent no longer
reads, the theme's own accent is used there instead.

## Themed HTML pages

An HTML page can take the organisation's theme too. Put one tag in its `<head>`:

```html
<meta name="venom-theme" content="org">
```

When the page is served (the console's frame, a public link, present, print, `studio_artifact_export`), Venom inlines a small
stylesheet right after that tag: the theme's colours, fonts and radius as the same `--st-*` variables decks and pages use (light
and dark, following the same rules as a deck), sensible element defaults (body, headings, links, lists, tables, code, buttons,
form fields) and a few `vk-*` classes: `vk-container`, `vk-prose`, `vk-section`, `vk-stack`, `vk-row`, `vk-grid` (and
`vk-grid-2/3/4`), `vk-card`, `vk-surface`, `vk-nav`, `vk-eyebrow`, `vk-lead`, `vk-muted`, `vk-btn` (`vk-btn-primary`, `vk-btn-ghost`,
`vk-btn-sm`, `vk-btn-lg`), `vk-badge` (`vk-pos`, `vk-neg`, `vk-warn`, `vk-neutral`), `vk-stat`, `vk-table`, `vk-field`, `vk-hint`,
`vk-switch`, `vk-tabs` with `vk-tab`, and `vk-logo`. Agents get the full list from `studio_catalog_get` with `group: "html"`.

An html page can also be a slide deck: a `vk-deck` holding one `<section class="vk-slide">` per slide. Each slide is 16:9 and sizes
its text in container units, so it scales with the screen; an element with `vk-slide-notes` holds speaker notes and is never shown
or printed. Such a page prints one slide per sheet ([Print and PDF](/docs/studio/sharing.md#print)), and a chart placed in a slide with a
`venom+json` script ([components](/docs/studio/components.md#placing-them)) is drawn at slide size.

The kit sits in a CSS layer and its element rules have no specificity, so anything the page writes itself wins. It is added at
serve time and never saved into the page: change the artifact's theme (the picker in the editor, or `studio_artifact_update`) or
the org's default theme, and the page follows. The logo is available as `--st-logo` and through `vk-logo` only when it is a
`data:` image, because the page's sandbox cannot load an `https` image. The sandbox and its Content-Security-Policy are the same
for a themed page ([why](/docs/studio/sharing.md#html-pages-are-sandboxed)).

A page without the tag is served exactly as written, with one exception: a bare fragment with no `<html>`, `<head>` or `<body>`
tag, no `<style>`, no `style=` attribute and no `<link>` (say, a few headings, paragraphs and a list) is served wrapped in a whole
document with the theme, as a readable article, instead of the browser's default Times on white.

## Import a design system

If your team already has a design system, Studio can turn it into a theme instead of you copying colours by hand. In the
console, open **Themes**, then **Import design system**, and drop or paste the files that hold your brand:

| What | Read from |
|---|---|
| CSS custom properties | `:root { --primary: … }`, shadcn/ui's `globals.css` (`--background`, `--foreground`, `--primary`, `--muted-foreground`, `--border`, `--destructive`, `--chart-1`…, in hex, `rgb()`, `hsl()`, a bare hsl triplet or `oklch()`), Tailwind v4's `@theme { --color-*: … }` |
| A dark palette | a `.dark { … }` block, `[data-theme="dark"]`, or `@media (prefers-color-scheme: dark)`; with one, the theme follows the viewer |
| Tailwind v3 config | `theme.extend.colors` (a brand scale's 600 shade becomes the accent, `hsl(var(--x))` is read from the CSS file sent with it), `fontFamily`, `borderRadius` |
| Design tokens | W3C DTCG (`$value`, `$type`), Style Dictionary and Tokens Studio exports (`value`, `type`, sets named light and dark), with `{alias.references}` |
| A brand guide | Markdown or text that lists colours with a label (`Primary: #E8590C`, a table row), and lines such as `Headings: Merriweather, serif` |

Names decide roles: primary, brand or accent becomes the accent; background, bg or canvas the background; foreground, text or ink
the text; card or surface the surface; muted text, subtle or secondary text the muted colour; border, divider or line the border;
success and destructive, danger or error the good and bad news colours; chart-1 to chart-8 the chart series. A missing background
or text colour is guessed, and the most saturated unclaimed colour becomes the accent when none is named.

Before anything is saved you see the proposal: the palette, a sample slide and page in light and dark, and a report of what was
found (and from which token), what was guessed, and which colours were adjusted. Text and muted text are darkened (or lightened on
a dark background) to 4.5:1 and the accent to 3:1, the same bars a hand-made theme has to meet, and the report shows each colour
before and after. Change any field, then **Save as theme**, and tick **Make it the organisation's default** to make every new
artifact take it. Saving needs an org owner or admin, as for any theme.

Some things are not imported. Web fonts are never downloaded, so a stack such as `Inter, sans-serif` maps to the nearest system
stack (`sans`, `serif`, `rounded` or `mono`) and the report names the web fonts. Colours in `lab()`, `lch()`, `color()` or
`color-mix()` are skipped and named. Logos, images and design files (Figma, Sketch) are not read; add a logo after saving. A
`tailwind.config.js` is read as text and never run. Up to 20 files of 250 KB each; your browser reads them and sends their text,
and nothing is stored until you save.

**From a repository or a codebase.** Venom Cloud does not fetch from GitHub or anywhere else for this. Ask an agent that has the
code (venom, or Claude Code with the Venom MCP) to import the theme: it reads files such as `app/globals.css`,
`tailwind.config.ts` or `tokens.json` itself and calls `studio_theme_import` with their text:

```json
{ "files": [{ "name": "app/globals.css", "text": ":root { --background: oklch(1 0 0); --primary: oklch(0.55 0.2 293); … }" }] }
```

The answer is the proposed theme, an id, and the same report, and nothing is stored. After you agree, the agent calls it again
with `"save": true` (and `"default": true` to make it the default), or saves an edited proposal with `studio_theme_set`
(`{ "id": "…", "theme": … }`). Proposing needs a credential that may change Studio; saving needs an org owner or admin. The
REST twin is `POST /api/v1/studio/theme-import`.
