@picked/client 0.0.1-dev.1785305085063 → 0.0.1-dev.1785908062293

package/dist/docs/content/layouts.mdx

@@ -1,70 +0,0 @@
----
-layout: docs
----
-
-import { Screenshot } from '../../../components/Screenshot'
-
-# Page & Step Layouts
-
-Layouts are reusable JSON schemas. Page Layouts back standalone Pages; Step Layouts back individual Steps inside a Flow.
-
-<Screenshot
-  route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/models"
-  alt="The layouts list in the schema builder on the Picked dashboard"
-/>
-
-## What a layout is
-
-A layout is a reusable schema that defines the fields a piece of content can hold. It holds no data itself: a [Content Entry](/content/content-entries) instantiates the layout and fills it in. The dashboard groups both kinds of layout under **Models**.
-
-## Page layouts vs step layouts
-
-A layout has a fixed category that decides what it backs:
-
-| Layout | Backs | Used by |
-| --- | --- | --- |
-| **Page Layout** | A standalone [Page](/content/pages). | The SDK renders the bound entry on your server. |
-| **Step Layout** | A single [Step](/steps) inside a Flow. | The Step renders the bound entry in the browser. |
-
-## Create a layout
-
-1. Open your workspace and click **Models** in the sidebar.
-2. Click **New Model** and choose the category, **Page Layout** or **Step Layout**.
-3. Enter a name and a **Key**. The Key is a unique, stable identifier used in SDK code and API references.
-4. Add fields (see below) and save.
-
-The category is fixed at creation and cannot be changed later.
-
-## Field types
-
-A layout is built from fields. Each field has a type that decides its editor and the shape of the value it stores.
-
-| Type | Stores | Use it for |
-| --- | --- | --- |
-| **Single-line text** | A short string. | Titles, labels, short headlines. |
-| **Multi-line text** | A longer plain string. | Descriptions, paragraphs without formatting. |
-| **Markdown** | A Markdown string. | Rich body copy with formatting. |
-| **Slug** | A URL-safe string. | Path segments, identifiers. |
-| **Number** | A numeric value. | Prices, counts, ratings. |
-| **Boolean** | A true/false value. | Toggles, flags. |
-| **Date** | A date value. | Publish dates, deadlines. |
-| **Color** | A color value. | Theme accents, swatches. |
-| **JSON** | An arbitrary JSON value. | Structured data with no dedicated editor. |
-| **Group** | A nested object of fields. | Grouping related fields together. |
-| **Section** | An embedded [Section](/content/sections) schema. | Reusing a shared schema fragment. |
-| **Asset** | A reference to an [Asset Library](/content/asset-library) item. | Images, video, documents. |
-| **HTML asset** | A reference to an uploaded `.html` file. | Pre-built HTML embedded into content. |
-
-## Repeatable and grouped fields
-
-Any field can be made **repeatable**, which renders as a sortable list of values rather than a single value. Use it for galleries, feature lists, or any collection.
-
-A **Group** field nests a set of fields under one key, producing a structured object. Combine repeatable with a group to model a list of objects, such as a list of feature cards.
-
-## Composing with sections
-
-A **Section** field embeds a reusable [Section](/content/sections) schema inside the layout. Define a common structure, such as a hero or a feature list, once as a Section, then reference it from any Page or Step Layout.
-
-## Changing a schema
-
-Editing a layout's schema can leave existing Content Entries out of date. After a schema change, revalidate the entries that use the layout and fix any per-field errors before publishing.

package/dist/docs/content/pages.mdx

@@ -1,67 +0,0 @@
----
-layout: docs
----
-
-import { Screenshot } from '../../../components/Screenshot'
-
-# Pages
-
-A Page is a standalone, server-rendered experience backed by CMS content, built for SEO-critical landing pages.
-
-<Screenshot
-  route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/experiences"
-  alt="The experiences list, where Pages and Flows are created on the Picked dashboard"
-/>
-
-## Pages vs flows
-
-Picked has two kinds of experience:
-
-| Experience | What it is | Use it for |
-| --- | --- | --- |
-| **Page** | A standalone experience rendered on your server, backed by a Content Entry. | SEO-critical landing pages, campaign pages, content the crawler must see. |
-| **Flow** | A multi-step, interactive experience rendered in the browser. | Quizzes, surveys, product finders, multi-step onboarding. |
-
-Reach for a **Page** when the content must appear in the server HTML for search engines and social unfurls. Reach for a **Flow** when the value is in the interaction, and client-side rendering is fine. See [Experiences](/experiences) for the wider model.
-
-## How a page fits together
-
-Four pieces back every Page:
-
-1. A **Page Layout** defines the shape: the fields a page can hold. See [Page & Step Layouts](/content/layouts).
-2. A **Content Entry** fills that shape with real data. See [Content Entries](/content/content-entries).
-3. A **Page** binds one entry so the SDK can render it.
-4. The **SDK** fetches the entry and renders it on your server. See [Server-Side Rendering](/sdk/ssr).
-
-A layout defines the shape, a content entry fills it with data, a Page binds an entry so the SDK can render it. Step Layouts do the same for individual Steps inside a Flow.
-
-```
-Author (dashboard) -> Publish -> Delivery API (config + content)
-  -> serialize() on server -> Provider seeds client -> ExperienceSlot renders -> hydrate
-```
-
-## Create a page
-
-1. Open your project and select a workspace.
-2. Click **Experiences** in the sidebar.
-3. Click **New Experience** and choose the **Page** type.
-4. Pick a **Page Layout**. The layout determines which fields the page holds.
-5. Click **Create**.
-
-A Content Entry is created and linked to the page on its first save, so the page always has somewhere to store its data.
-
-## Edit page content
-
-The Page editor has a **Properties** tab for the page's content and a **Settings** tab for its name, condition, and layout. Fill in the fields on the **Properties** tab. The inspector on the right edits the selected field, and the preview panel shows the page as it fills in.
-
-## Change or remove the layout
-
-Use the change-layout control on the **Settings** tab to switch the page to a different Page Layout. Unlinking a layout detaches the Content Entry from the page. The entry is not deleted, but the page no longer has content to render until you bind a layout again.
-
-## Validate and publish
-
-Invalid fields surface inline as per-field errors while you edit, so you can fix them before publishing. When the page is valid, publish the workspace to make it live. Publishing produces the version the Delivery API serves to anonymous readers.
-
-## Render a page
-
-A published Page is rendered by the SDK on your server. See the [Build a Personalized Page](/guides/build-a-personalized-page) guide for the end-to-end walkthrough, and [Server-Side Rendering](/sdk/ssr) for the SDK reference.

package/dist/docs/content/sections.mdx

@@ -1,33 +0,0 @@
----
-layout: docs
----
-
-import { Screenshot } from '../../../components/Screenshot'
-
-# Sections
-
-Sections are reusable schema fragments you embed inside layouts, so common structures such as a hero or a feature list are defined once.
-
-<Screenshot
-  route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/blocks"
-  alt="The sections list in the schema builder on the Picked dashboard"
-/>
-
-## What a section is
-
-A Section is a reusable fragment of schema with its own **Key**. Where a [layout](/content/layouts) backs a whole Page or Step, a Section is a piece you compose into one or more layouts. Define the shape once, reuse it everywhere.
-
-## Create a section
-
-1. Open your workspace and click **Sections** in the sidebar.
-2. Click **New Section**.
-3. Enter a name and a **Key**. The Key is a unique, stable identifier used in SDK code and API references.
-4. Add fields and save.
-
-## Use a section in a layout
-
-Add a **Section** field to a Page or Step Layout and point it at the Section you want to embed. The layout then carries the Section's fields wherever that field appears. A Content Entry built from the layout fills the Section's fields like any others.
-
-## Changing a section
-
-Editing a Section does not automatically migrate the entries that already use it. After changing a Section, revalidate the affected [Content Entries](/content/content-entries) and resolve any per-field errors before publishing.

package/dist/docs/delivery-api/index.md

@@ -1,46 +0,0 @@
----
-layout: docs
----
-
-# Delivery API
-
-The Delivery API is a public, read-only REST API that serves your published project config and page content. It is separate from the GraphQL management API.
-
-## Delivery API vs the management API
-
-Picked has two HTTP APIs. Use the one that fits the job:
-
-| | Delivery API | Management API |
-| --- | --- | --- |
-| Style | REST | GraphQL |
-| Access | Public, anonymous | Authenticated |
-| Operations | Read-only | Read and write |
-| Use for | Serving published config and content to your app | Managing projects, experiences, and content |
-
-The management API is documented under [API Reference](/api). This section covers the Delivery API.
-
-## Base URL and versioning
-
-All Delivery API routes are versioned under `/api/v1`:
-
-```
-https://api.picked.app/api/v1
-```
-
-## Published vs preview
-
-Each endpoint serves two surfaces:
-
-- **Published** content is anonymous. Anyone can read your published config and content.
-- **Preview** content is gated by a `preview_token` query parameter, so you can render unpublished drafts before going live.
-
-A workspace's preview token is available as the `previewToken` field on the workspace in the management API, and the dashboard preview action issues one for you.
-
-## Endpoints
-
-| Endpoint | Description |
-| --- | --- |
-| [Project Config](/delivery-api/project-config) | `GET /api/v1/projects/:projectId` returns the published project config, including each step's content link. |
-| [Experience Content](/delivery-api/experience-content) | `GET /api/v1/projects/:projectId/experiences/:id/content` returns the Content Entries that back an experience. |
-
-For the operational details shared by both endpoints, see [Preview, Caching & Crawling](/delivery-api/preview-caching-crawling).

package/dist/docs/delivery-api/preview-caching-crawling.md

@@ -1,59 +0,0 @@
----
-layout: docs
----
-
-# Preview, Caching & Crawling
-
-The operational surface shared by both Delivery API endpoints: preview tokens, caching, CORS, and crawling.
-
-## Preview tokens
-
-Pass `?preview_token=<token>` to read unpublished content. Both endpoints accept it, and both return `versionId: null` on the preview surface. An invalid token returns `401`.
-
-```bash
-curl "https://api.picked.app/api/v1/projects/proj_123?preview_token=<token>"
-```
-
-A workspace's preview token is available as the `previewToken` field on the workspace in the [management API](/api), and the dashboard preview action issues one for you. Use the same token for the project config and the experience content requests so both come from the same preview surface.
-
-## Caching
-
-Caching depends on the surface and the requesting client. The SDK sends a `Picked-Client: sdk` request header:
-
-| Request | `Cache-Control` |
-| --- | --- |
-| Published, `Picked-Client: sdk` | `public, s-maxage=60, stale-while-revalidate=86400` |
-| Published, other clients | `private, no-store` |
-| Preview | `no-store` |
-
-Cacheable published responses also send `Vary: Picked-Client`, so a shared cache keys on the client header and never serves an SDK-cached body to a non-SDK request.
-
-## CORS
-
-Both endpoints are cross-origin readable. An `OPTIONS` preflight returns `204` with the CORS headers:
-
-| Header | Value |
-| --- | --- |
-| `Access-Control-Allow-Origin` | `*` |
-| `Access-Control-Allow-Methods` | `GET, OPTIONS` |
-| `Access-Control-Allow-Headers` | `Content-Type, Picked-Client, Picked-Version, traceparent, tracestate` |
-
-## Crawling and SEO
-
-Both endpoints are crawlable so search engines can read your published content. Preview URLs are disallowed, so drafts never reach the index. The `robots.txt` rules:
-
-```
-User-agent: *
-
-# Allow crawling of the public project config and experience content endpoints
-Allow: /api/v1/projects
-Allow: /api/v1/projects/*/experiences/*/content
-
-# Keep preview (draft) responses out of crawlers
-Disallow: /api/v1/projects/*preview_token=
-
-# Everything else (GraphQL, MCP, internal, ping) stays disallowed
-Disallow: /
-```
-
-See [Project Config](/delivery-api/project-config) and [Experience Content](/delivery-api/experience-content) for the endpoints themselves.

package/dist/docs/experiences.mdx

@@ -1,42 +0,0 @@
----
-layout: docs
----
-
-import { Screenshot } from '../../components/Screenshot'
-
-# Experiences
-
-An experience is a personalized experience delivered to visitors on your site. Each experience maps to a component registered in your application.
-
-Picked has two kinds of experience. A **Flow** is a multi-step, interactive experience rendered in the browser, covered on this page. A **Page** is a standalone, server-rendered experience backed by CMS content, built for SEO-critical landing pages. See [Pages](/content/pages) for that kind.
-
-<Screenshot
-  route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/experiences"
-  alt="The experiences list for a workspace on the Picked dashboard"
-/>
-
-## Create an experience
-
-1. Open your project.
-2. Click **Experiences** in the sidebar.
-3. Click **New Experience**.
-4. Enter a name and a component name. The component name must match a component registered in your application. See [SDK Experiences](/sdk/experiences) for details on registering components.
-5. Click **Create**.
-
-The flow editor opens with an empty canvas. See [Building Flows](/flow-builder/building-flows) to start adding nodes.
-
-## Experience settings
-
-Select no nodes on the canvas (or click the canvas background) to open the experience inspector in the right panel.
-
-**Name**: The display name shown in the dashboard. Visitors don't see this.
-
-**Component Name**: The identifier that maps this experience to a registered component in your application.
-
-**Condition**: An optional activation condition. When set, the experience only activates for visitors who match the condition logic. See [Condition Builder](/flow-builder/condition-builder) for details on configuring conditions. Leave blank to activate for all visitors.
-
-**Initialize Open**: An optional condition that controls whether the experience opens automatically on page load. When blank, the experience loads but stays closed until opened.
-
-## Experience list
-
-The experiences list shows all experiences in the current project. Click any experience to open it in the flow builder.

package/dist/docs/features.mdx

@@ -1,58 +0,0 @@
----
-layout: docs
----
-
-import { Screenshot } from '../../components/Screenshot'
-
-# Features
-
-Features let you run A/B tests and feature flags. Control which visitors see which variant of your site without deploying code changes.
-
-<Screenshot
-  route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/features"
-  alt="The features list for a workspace on the Picked dashboard"
-/>
-
-## Create a feature
-
-1. Open your project.
-2. Click **Features** in the sidebar.
-3. Click **New Feature**.
-4. Enter a name.
-5. Click **Create**.
-
-## Keys
-
-Each feature has a unique key. Use this key in your application to check which variant a visitor is assigned to. The key is set when you create the feature and cannot be changed later.
-
-## Configure variants
-
-Each feature has one or more variants. Visitors are assigned to a variant based on the rules you define.
-
-Configure variant allocation, targeting rules, and rollout percentages from the feature detail page.
-
-## How visitors are bucketed
-
-Visitors are assigned to variants using weight-based probabilistic rollout. Each variant has a weight from 0 to 100, representing the percentage of traffic it receives.
-
-For example, with two variants weighted 50/50, roughly half of visitors see each variant. A variant weighted at 0 receives no traffic.
-
-Bucketing is deterministic — the same visitor sees the same variant on repeat visits, unless the feature version changes.
-
-## Feature versions
-
-Each feature has a version number (starting at 1). Incrementing the version resets all visitor assignments, so every visitor is re-evaluated as if they were seeing the feature for the first time.
-
-### What happens when you increment the version
-
-- **All visitors are re-allocated.** Every visitor currently allocated to this feature will be re-evaluated against the new version. A visitor who was in the control group may end up in a variant, and vice versa.
-- **Cached decisions are invalidated.** The SDK caches allocation decisions in browser storage using a key that includes the version. When the version changes, the old cache entry no longer matches, forcing a fresh evaluation on the next page load.
-- **This is irreversible.** You cannot decrement a version. Once incremented, the previous allocation assignments are lost.
-
-### When to increment
-
-Increment the version when you have changed the weight or allocation and want all visitors — including those already allocated — to be re-evaluated from scratch.
-
-### When not to increment
-
-If you only want changes to affect new visitors (those who haven't been allocated yet), update the weight without incrementing the version. Existing visitors will keep their current assignment.

package/dist/docs/fields.mdx

@@ -1,79 +0,0 @@
----
-layout: docs
----
-
-import { Screenshot } from '../../components/Screenshot'
-
-# Fields
-
-A field is a data input shown to visitors inside a step. Fields collect information like names, email addresses, preferences, or selections.
-
-These are experience Fields, which collect visitor input. They are distinct from the Content Fields that make up a CMS layout's schema, covered in [Page & Step Layouts](/content/layouts).
-
-<Screenshot
-  route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/fields"
-  alt="The fields list for a workspace on the Picked dashboard"
-/>
-
-## Create a field
-
-1. Open your project.
-2. Click **Fields** in the sidebar.
-3. Click **New Field**.
-4. Enter a name, key, and label.
-5. Select a type.
-6. Click **Create**.
-
-## Field types
-
-Fields support many types. Here are some common examples:
-
-`TEXT`: A string input. Use for names, emails, free-form text.
-
-`NUMBER`: A numeric input. Use for quantities, ratings, ages.
-
-`BOOLEAN`: A true/false toggle. Use for checkboxes, opt-ins, consent.
-
-`OBJECT`: A structured data input. Use for complex or nested data.
-
-## Configuration
-
-**Name**: Display name in the dashboard. Not visible to visitors.
-
-**Key**: Programmatic identifier. Set once, can't change. Not visible to visitors.
-
-**Label**: The label visitors see next to the field.
-
-**Placeholder**: Hint text shown inside the input when empty.
-
-**Description**: A longer description of the field's purpose. Shown in the dashboard, not to visitors.
-
-**Help Text**: Assistive text shown to visitors below the field.
-
-**Default Value**: The initial value when the field loads.
-
-## Validation
-
-**Required**: When enabled, visitors must fill in this field before proceeding.
-
-**Validation rules**: Define conditions for advanced constraints like minimum/maximum values, patterns, or custom logic. See [Condition Builder](/flow-builder/condition-builder) for details on building validation rules.
-
-## Multiple values
-
-Enable **Multiple** to allow visitors to submit more than one value for this field. Useful for multi-select inputs or tag-style fields.
-
-## Options
-
-For fields that present a fixed set of choices (like dropdowns or radio buttons), add options. Each option has a value that gets submitted with the response.
-
-Each option can also have a condition applied. When a condition is set, the option only appears to visitors who match the condition logic. See [Condition Builder](/flow-builder/condition-builder) for details.
-
-## Privacy
-
-**Do Not Track**: When enabled, this field's data is excluded from analytics tracking.
-
-**Do Not Store**: When enabled, this field's data is processed but not persisted. Use for sensitive information like passwords or payment details.
-
-## Reuse fields
-
-Fields are project-level entities. Assign the same field to multiple steps across different experiences. Changes to a field's configuration apply everywhere it's used.

package/dist/docs/flow-builder/building-flows.md

@@ -1,61 +0,0 @@
----
-layout: docs
----
-
-# Building flows
-
-Build flows by dragging blocks onto the canvas, connecting nodes with arrows, and configuring each node in the inspector.
-
-## Add nodes
-
-Drag a step, action, or condition from the entity browser onto the canvas. A new node appears where you drop it.
-
-You can also drop a block directly onto an existing arrow. The node inserts inline — the original arrow splits into two arrows with the new node in between. A **+** indicator appears when you hover over a valid arrow.
-
-## Connect nodes
-
-Click and drag from a node's output handle (right side) to another node's input handle (left side). An arrow appears connecting them.
-
-The flow follows arrows from left to right, starting at the origin. Every node downstream of the origin is part of the experience flow.
-
-## Branch with conditions
-
-Connect the origin (or any node) to a condition node. The condition evaluates its logic and routes the flow down one of two paths.
-
-Connect the green (true) handle to the nodes that should run when the condition passes. Connect the red (false) handle to the alternative path. Either path can lead to more steps, actions, or further conditions.
-
-## Assign fields to steps
-
-Drag a field from the entity browser and drop it onto a step node. The field is now assigned to that step.
-
-You can assign multiple fields to a single step. The step node shows a count of assigned fields. To see which fields are assigned, select the step and check the **Assigned Fields** section in the inspector.
-
-## Select nodes
-
-Click a node to select it. Its inspector opens in the right panel.
-
-Drag on empty canvas to marquee-select multiple nodes. Press `Cmd/Ctrl+A` to select all nodes.
-
-When multiple nodes are selected, the inspector shows a count and grouped list. Click any item in the list to navigate to its inspector.
-
-## Move nodes
-
-Drag a selected node to reposition it. Nodes snap to the grid automatically.
-
-Use arrow keys to nudge selected nodes. Hold `Shift` for larger nudges.
-
-## Delete nodes
-
-Select one or more nodes and press `Delete` or `Backspace`. The nodes and their connected arrows are removed.
-
-## Duplicate nodes
-
-Select one or more nodes and press `Cmd/Ctrl+D`. Copies appear offset from the originals.
-
-## Undo and redo
-
-Press `Cmd/Ctrl+Z` to undo. Press `Cmd/Ctrl+Shift+Z` to redo. The undo stack tracks node additions, deletions, connections, and position changes.
-
----
-
-[Overview](/flow-builder/overview) · [Nodes](/flow-builder/nodes) · **Building Flows** · [Keyboard Shortcuts](/flow-builder/keyboard-shortcuts) · [Condition Builder](/flow-builder/condition-builder)

package/dist/docs/flow-builder/condition-builder.md

@@ -1,54 +0,0 @@
----
-layout: docs
----
-
-# Condition builder
-
-The condition builder is a visual rule editor used across the dashboard. It lets you define logic without writing code.
-
-## Where it appears
-
-The condition builder is used in several places:
-
-- **Condition nodes** — define branching logic in the [flow builder](/flow-builder/overview)
-- **Experience conditions** — control when an experience activates for a visitor
-- **Initialize open conditions** — control when an experience opens automatically on page load
-- **Field option conditions** — show or hide individual options based on visitor state
-
-## Rule structure
-
-Rules are organized into groups. Each group uses either **AND** (all rules must match) or **OR** (any rule must match).
-
-A single rule has three parts:
-
-1. **Field** — the data source to evaluate
-2. **Operator** — how to compare (equals, not equals, greater than, contains, etc.)
-3. **Value** — the target value to compare against
-
-You can nest groups inside other groups to create complex logic. For example, an AND group containing two OR groups.
-
-## Available data sources
-
-When building rules, you can reference these data sources:
-
-**Responses** — values visitors have submitted through form fields in the current experience. Each field you create in your project appears here by its name.
-
-**Actions** — references to actions that have been triggered during the flow.
-
-**Features** — the state of feature flags in your project. Use this to branch based on which variant a visitor is assigned to.
-
-**Location** — properties of the visitor's current page URL, including pathname, search parameters, hostname, and hash.
-
-## Example
-
-To show a step only to visitors on a specific page who opted into marketing:
-
-1. Create an AND group.
-2. Add a rule: **Location → pathname** equals `/pricing`.
-3. Add a rule: **Responses → marketing_opt_in** equals `true`.
-
-Both conditions must be true for the rule group to match.
-
----
-
-[Overview](/flow-builder/overview) · [Nodes](/flow-builder/nodes) · [Building Flows](/flow-builder/building-flows) · [Keyboard Shortcuts](/flow-builder/keyboard-shortcuts) · **Condition Builder**

package/dist/docs/flow-builder/keyboard-shortcuts.md

@@ -1,66 +0,0 @@
----
-layout: docs
----
-
-# Keyboard shortcuts
-
-These shortcuts are available when the flow builder canvas is focused.
-
-## Canvas tools
-
-| Shortcut (Mac) | Shortcut (PC) | Action |
-| --- | --- | --- |
-| `V` | `V` | Select tool |
-| `H` | `H` | Hand tool (pan) |
-| `Space` (hold) | `Space` (hold) | Temporary hand tool |
-
-## Layout
-
-| Shortcut (Mac) | Shortcut (PC) | Action |
-| --- | --- | --- |
-| `Shift+L` | `Shift+L` | Auto-layout |
-
-## Selection
-
-| Shortcut (Mac) | Shortcut (PC) | Action |
-| --- | --- | --- |
-| `Cmd+A` | `Ctrl+A` | Select all nodes |
-| `Escape` | `Escape` | Deselect all |
-
-## Editing
-
-| Shortcut (Mac) | Shortcut (PC) | Action |
-| --- | --- | --- |
-| `Cmd+D` | `Ctrl+D` | Duplicate selected nodes |
-| `Delete` / `Backspace` | `Delete` / `Backspace` | Delete selected nodes |
-| `Cmd+Z` | `Ctrl+Z` | Undo |
-| `Cmd+Shift+Z` | `Ctrl+Shift+Z` | Redo |
-
-## Movement
-
-| Shortcut (Mac) | Shortcut (PC) | Action |
-| --- | --- | --- |
-| Arrow keys | Arrow keys | Nudge selected nodes |
-| `Shift`+Arrow keys | `Shift`+Arrow keys | Large nudge |
-
-## Zoom
-
-| Shortcut (Mac) | Shortcut (PC) | Action |
-| --- | --- | --- |
-| Scroll | Scroll | Zoom in/out |
-| Pinch | Pinch | Zoom in/out (trackpad) |
-| `Cmd+=` | `Ctrl+=` | Zoom in |
-| `Cmd+-` | `Ctrl+-` | Zoom out |
-| `Shift+1` | `Shift+1` | Fit view |
-| `Shift+0` | `Shift+0` | Zoom to 100% |
-
-## Panels
-
-| Shortcut (Mac) | Shortcut (PC) | Action |
-| --- | --- | --- |
-| `Cmd+\` | `Ctrl+\` | Toggle both side panels |
-| `?` | `?` | Toggle shortcuts |
-
----
-
-[Overview](/flow-builder/overview) · [Nodes](/flow-builder/nodes) · [Building Flows](/flow-builder/building-flows) · **Keyboard Shortcuts** · [Condition Builder](/flow-builder/condition-builder)