Output files
Built files to take away, grouped by kind: in the playground’s Outputs view, the files dta build writes (output/css/…, output/tailwind/…, output/js/…) in CSS, Tailwind and JS. Each group has one download for all its files (a zip with the same folders); each file has its path, its size, Copy and Download. The path opens the file’s preview in the Detail panel.
When to use
Section titled “When to use”- For a handful to a few dozen generated files a visitor takes some or all of.
- Not for source files someone edits, and not for a single file (show that one in the panel or a Terminal).
Three groups with their files, one preview open
CSS
4 files- 1006 B
- 743 B
- 744 B
- 1006 B
Tailwind
6 files- Tailwind v4462 B
- Tailwind v3650 B
- Tailwind v4471 B
- Tailwind v3659 B
- Tailwind v41.2 KB
- Tailwind v31.4 KB
JS
1 file- 1.2 KB
CSS
4 files- 1006 B
- 743 B
- 744 B
- 1006 B
Tailwind
6 files- Tailwind v4462 B
- Tailwind v3650 B
- Tailwind v4471 B
- Tailwind v3659 B
- Tailwind v41.2 KB
- Tailwind v31.4 KB
JS
1 file- 1.2 KB
Guidelines
Section titled “Guidelines”- Rules and type on the canvas, no cards. A group’s head: the name in the
titletype, the file count in monofg-muted, the group download as an outline Button (Download CSS (.zip)), closed by astroke-inkrule inborder-strong. - A row per file, hairline
border-defaultbetween rows: the path in monoaction-text, underlined, as written bydta build; the size in monofg-muted, tabular figures; Copy (Copy button) and Download as quiet Buttons at the 44 px touch minimum. Their accessible names say which file (Download output/css/base.css). - Which output, where a group mixes them: the Tailwind group holds the v4 files (
tailwind.css, an@themestylesheet) and the v3 files (tailwind.tokens.ts, a theme object) side by side, so each of its rows says which after the path:Tailwind v4orTailwind v3, monofg-mutedin a hairlineborder-defaultoutline (tag). The playground takes it from the file’sformat(@dta/build) and labels only groups with more than one output, so CSS and JS rows say nothing twice. The preview’s kicker names it too (Output · Tailwind v4 · 1.1 KB). - The row whose preview is open is marked (
aria-current) and tintedaction-subtle, as in the Structure table. - Below 560 px of container width the path (with its output label) takes its own line and the size and actions follow under it; nothing scrolls sideways. A long path breaks after a
/or., never inside a folder or file name (Token path). - When the build fails:
dta buildwrites no files while the tokens have errors (a broken alias, TICKET-119), so the Outputs view lists none and shows the build’s diagnostics as an error status banner instead (Findings withbanner:status-error-subtle, a complete 2 pxstatus-error-markeroutline, the lines instatus-error-text); the summary line’s part readsbuild failedwith the error square. See Status colours; the Findings page shows it as “The build has errors: a status banner”. - The component reports clicks; saving files is the page’s (in the playground a blob URL: nothing leaves the browser).
- A Preact component; stories render it to static HTML.
- Motion: each group is a view-transition part (
view-transition-class: dta-swap); when the chosen formats change, the playground keeps the files on screen until the new build lands, then the groups that stay move into place and the others fade. The open row’s tint comes and goes overfast. See Motion.
Tokens used
Section titled “Tokens used”Read from the component’s source:
--action-bg--action-subtle--action-text--border-default--border-strong--fg-default--fg-muted--font-mono--font-sans--motion-duration-fast--motion-ease-standard--radius-sm--space-1--space-2--space-3--space-4--space-8--stroke-focus--stroke-hairline--stroke-ink--type-body-sm-size--type-meta-line-height--type-meta-size--type-title-line-height--type-title-size--type-title-weight