Design
Views
Turn a product model into visual interfaces without losing the meaning behind them.
Views are the visual layer of Lines. They show how the product model appears to a person as a screen, flow, state, or interface composition.
In the interface, a bounded View may be presented as an Artboard. The name changes with the task; the principle does not. A View is not the product model itself. It is a visual projection of that model.
Design with context intact
Traditional design files are good at describing pixels but often lose the reasoning behind them. Lines keeps semantic Nodes in Model Mode and visual Views in Design Mode, then lets you connect the two when preparing a handoff.
This gives teams room to explore visually while preserving the product structure underneath. You can redesign a screen without rewriting the model, or create multiple Views of the same concept for different devices, roles, and states.
Work with familiar visual tools
Use Design Mode to:
Create preset or custom Artboards.
Add and edit text.
Place images.
Draw freehand strokes and Bezier paths.
Organize objects in the Layers panel.
Apply fills, strokes, opacity, corner radius, and typography.
Add layout guides to an Artboard.
Export selected Artboards as PNG or SVG.
The Properties Inspector changes with the selection, giving you focused controls for the page, Artboard, text, image, vector, or connector you are editing.
One model, many expressions
A product concept rarely has only one visual form. The same task may appear in a desktop workflow, a compact mobile flow, an empty state, and an error state. Views let you explore those expressions while the underlying Node remains the stable reference for intent and behavior.
This makes reviews more precise. Instead of asking whether a frame “matches the requirements,” your team can inspect the relationship between the product model and the interface that represents it.
Prepare cleaner handoffs
When a View is packaged with its related Nodes, an implementation agent receives both visual direction and semantic context. People can inspect those connections before anything is built, reducing the gap between what was intended, what was drawn, and what gets implemented.
Views, their visual objects, guides, and bindings are saved in your local Lines Markdown file.
Learn how to create and edit Views in the documentation — /docs/artboards-and-views.