@picked/client 0.0.71-next.1 → 0.0.71-next.3

package/dist/docs/{features.mdx → reference/dashboard/features.mdx}

@@ -1,8 +1,9 @@
 ---
+type: reference
 layout: docs
 ---
 
-import { Screenshot } from '../../components/Screenshot'
+import { Screenshot } from '../../../../components/Screenshot'
 
 # Feature flags
 
@@ -14,27 +15,19 @@ which visitors see a change to your site, and you deploy no code.
   alt="The feature flags list for a workspace on the Picked dashboard"
 />
 
-## Create a feature flag
-
-1. Open your project.
-2. Click **Feature flags** in the sidebar.
-3. Click **New feature flag**.
-4. Enter a name.
-5. Click **Create feature flag**.
-
 ## Keys
 
 Each feature flag has a unique key. Your application uses this key to check whether
 Picked allocates a visitor to the feature flag. You set the key when you create the
 feature flag, and you cannot change it later.
 
-## Configure allocation
+## Set the allocation
 
 Set the allocation from the detail page of the feature flag:
 
 | Control | What it does |
 | --- | --- |
-| **Enabled** | Whether Picked allocates a visitor to the feature flag. A feature flag that is off allocates nobody, and it records nothing. See [Turn a feature flag off](#turn-a-feature-flag-off). |
+| **Enabled** | Whether Picked allocates a visitor to the feature flag. A disabled feature flag allocates nobody, and it records nothing. See [Disable a feature flag](#disable-a-feature-flag). |
 | **Weight** | The percentage of visitors that Picked allocates to the feature flag, from 0 to 100. |
 | **Description** | An internal note about what the feature flag tests. |
 
@@ -43,55 +36,40 @@ allocated, or not allocated. A weight of 30 allocates 30% of your visitors. The
 70% stay unallocated. A weight of 0 allocates nobody. A weight of 100 allocates
 everybody.
 
-## How visitors are allocated
-
-The allocation is deterministic. Picked gives each visitor a stable value for each
-feature flag. It derives that value from the visitor ID and from the ID of the feature
-flag. It then compares the value against the weight. When the value is below the
-weight, Picked allocates the visitor.
+## How Picked allocates a visitor
 
-The same visitor always gets the same result for one feature flag, on every visit,
-while the weight stays the same. The version is not part of that value. It controls
-the cache only. See [Feature flag versions](#feature-flag-versions).
+The allocation is deterministic. It derives from the visitor ID, the ID of the feature
+flag, and the weight. Each feature flag gets its own value, so tests that run at the
+same time are independent. See
+[About feature flag allocation](/explanation/feature-flag-allocation).
 
-Each feature flag gets its own value, so tests that run at the same time are
-independent. Two feature flags, both at weight 50, split your visitors into four equal
-parts: allocated to both, to one, to the other, or to neither. Three feature flags at
-weight 50 give eight groups of 12.5%.
+## Disable a feature flag
 
-:::note
-Inside one feature flag, a larger weight only adds visitors. Everybody at weight 30 is
-still allocated at weight 50, so you can make a release wider and move nobody who is
-in it already. A smaller weight removes visitors from the top of the range.
-:::
-
-## Turn a feature flag off
-
-A feature flag that is off allocates nobody, and it records nothing. The difference
+A disabled feature flag allocates nobody, and it records nothing. The difference
 from a weight of 0 matters for your reports. The visitor is **not in the test at
 all**, and the visitor is not in the control group.
 
-The SDK does not evaluate a feature flag that is off. It stores no decision in the
+The SDK does not evaluate a disabled feature flag. It stores no decision in the
 browser of the visitor, and it reports no decision to your analytics. Such a feature
 flag is absent from the feature list on every analytics event.
 
-An experience whose condition points at a feature flag that is off behaves as though
+An experience whose condition points at a disabled feature flag behaves as though
 the visitor is not in the test. The condition reads as not allocated, and Picked
 records no assignment.
 
 This state is temporary, and it discards no decision that Picked made already. A
-visitor who was allocated before keeps that decision in the browser. When you turn the
-feature flag on again, Picked continues from that decision and does not allocate the
-visitor again.
+visitor who was allocated before keeps that decision in the browser. When you enable the
+feature flag again, Picked continues from that decision, and the visitor stays in the
+group they were already in.
 
 :::note
-Expect a step change in your reports when you turn a feature flag off: fewer feature
+Expect a step change in your reports when you disable a feature flag: fewer feature
 flags for each visitor, and fewer decision events. That is the feature flag that drops
 out, and you lose no data.
 :::
 
-A feature flag that is off stays visible in the developer tools, and a
-[URL override](/sdk/features#overrides-in-the-url) still turns one on for QA.
+A disabled feature flag stays visible in the developer tools, and a
+[URL override](/reference/sdk/features#overrides-in-the-url) still turns one on for QA.
 
 ## Feature flag versions
 
@@ -127,3 +105,10 @@ decision.
 To apply a weight change only to a visitor that Picked does not allocate yet, change
 the weight and leave the version as it is. An allocated visitor keeps the current
 allocation.
+
+## Related
+
+- [About feature flag allocation](/explanation/feature-flag-allocation)
+- [How to run an A/B test](/how-to/run-an-ab-test)
+- [How to read a feature flag](/how-to/read-a-feature-flag)
+- [How to add a step, a field, an action, or a condition](/how-to/add-a-step-field-or-action)

package/dist/docs/{fields.mdx → reference/dashboard/fields.mdx}

@@ -1,8 +1,9 @@
 ---
+type: reference
 layout: docs
 ---
 
-import { Screenshot } from '../../components/Screenshot'
+import { Screenshot } from '../../../../components/Screenshot'
 
 # Fields
 
@@ -11,22 +12,13 @@ information such as a name, an email address, a preference, or a choice.
 
 This page covers the experience field, which collects visitor input. An experience
 field is not the same as a content field. A content field is part of the schema of a
-CMS layout. See [Page and Step Layouts](/content/layouts) for those.
+CMS layout. See [Page and Step Layouts](/reference/dashboard/content/layouts) for those.
 
 <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, a key, and a label.
-5. Choose a type.
-6. Click **Create**.
-
 ## Field types
 
 A field has one of many types. These are the common ones:
@@ -63,7 +55,7 @@ it. Your visitors do not see it.
 continue.
 
 **Validation rules**: Conditions for a constraint such as a smallest value, a largest
-value, or a pattern. See [Condition Builder](/flow-builder/condition-builder) for how
+value, or a pattern. See [Condition Builder](/reference/dashboard/flow-builder/condition-builder) for how
 to build a validation rule.
 
 ## More than one value
@@ -78,17 +70,31 @@ buttons, add options. Each option has a value, and the response carries that val
 
 Each option can also carry a condition. When you set one, the option appears only to
 a visitor who matches the condition. See
-[Condition Builder](/flow-builder/condition-builder) for more detail.
+[Condition Builder](/reference/dashboard/flow-builder/condition-builder) for more detail.
 
 ## Privacy
 
-**Do Not Track**: When this is on, Picked keeps the data of this field out of your
-analytics.
+Two policies control where the value of a field can go. They are independent, and a
+sensitive field usually needs both.
+
+| Policy | What it does |
+| --- | --- |
+| **Do Not Track** | Picked keeps the value out of your analytics events. The events carry the field ID only. |
+| **Do Not Store** | The SDK reads the value but does not put it in browser storage. |
+
+Neither policy stops the flow from the use of the value inside the page. A field with both
+policies set still holds its value there. The flow validates the step with it, and it
+evaluates the conditions after the step with it. The policies control what leaves the
+page.
+
+Set both for a password, a tax number, or a payment detail. A field that only takes a
+branch in a flow needs neither.
 
-**Do Not Store**: When this is on, Picked reads the data of this field but does not
-keep it. Use it for sensitive information such as a password or payment detail.
+## Related
 
-## Reuse fields
+- [How to add a step, a field, an action, or a condition](/how-to/add-a-step-field-or-action)
 
-A field is a project-level entity. Assign the same field to steps in more than one
-experience. A change to the options of a field applies at every place that uses it.
+- [How to validate a field](/how-to/validate-a-field)
+- [How to write a condition](/how-to/write-a-condition) — for a validation rule or an
+  option condition.
+- [SDK fields](/reference/sdk/fields) — the `policies` object.

package/dist/docs/{flow-builder/overview.mdx → reference/dashboard/flow-builder/canvas.mdx}

@@ -1,8 +1,9 @@
 ---
+type: reference
 layout: docs
 ---
 
-import { Screenshot } from '../../../components/Screenshot'
+import { Screenshot } from '../../../../../components/Screenshot'
 
 # Flow builder
 
@@ -12,14 +13,14 @@ inspector panel.
 
 <Screenshot
   route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/experiences/{experienceId}"
-  alt="The flow builder with the entity browser, canvas, and inspector panels"
+  alt="The flow builder with the library, canvas, and inspector panels"
 />
 
 ## Layout
 
 The flow builder has three panels, from left to right.
 
-**Entity browser**, on the left: it lists every step, action, condition, and field in
+**Library**, on the left: it lists every step, action, condition, and field in
 your project. Drag an item from here onto the canvas.
 
 **Canvas**, in the middle: the area where you build your flow. A node stands for a
@@ -50,14 +51,8 @@ Click the auto-layout button in the toolbar. The flow builder then arranges ever
 node into a clean hierarchy. This is useful after you add many nodes, and when the
 canvas becomes messy.
 
-## Save your work
+## Related
 
-Click **Save** in the toolbar to save your flow. The button is active when you have
-an unsaved change.
-
-The flow builder also saves by itself after a period of inactivity. A dot on the save
-button means that you have an unsaved change.
-
----
-
-**Flow Builder** · [Nodes](/flow-builder/nodes) · [Build Flows](/flow-builder/building-flows) · [Keyboard Shortcuts](/flow-builder/keyboard-shortcuts) · [Condition Builder](/flow-builder/condition-builder)
+- [How to build a flow](/how-to/build-a-flow) — add, connect, and branch.
+- [Keyboard shortcuts](/reference/dashboard/flow-builder/keyboard-shortcuts)
+- [Nodes](/reference/dashboard/flow-builder/nodes)

package/dist/docs/{flow-builder → reference/dashboard/flow-builder}/condition-builder.md

@@ -1,4 +1,5 @@
 ---
+type: reference
 layout: docs
 ---
 
@@ -12,7 +13,7 @@ places. With it you define a rule and you write no code.
 The dashboard uses the condition builder here:
 
 - **Condition nodes** — they set which branch the flow takes in the
-  [flow builder](/flow-builder/overview).
+  [flow builder](/reference/dashboard/flow-builder/canvas).
 - **Experience conditions** — they control when an experience starts for a visitor.
 - **Initialize open conditions** — they control when an experience opens by itself as
   the page loads.
@@ -50,16 +51,7 @@ branch on whether Picked allocates a visitor to a flag.
 **Location** — the parts of the current page URL of the visitor. These are the
 pathname, the search parameters, the hostname, and the hash.
 
-## Example
+## Related
 
-To show a step only to a visitor who is on one page and who accepted marketing:
-
-1. Create an AND group.
-2. Add a rule: **Location → pathname** equals `/pricing`.
-3. Add a rule: **Responses → `marketing_opt_in`** equals `true`.
-
-The rule group matches only when both conditions are true.
-
----
-
-[Overview](/flow-builder/overview) · [Nodes](/flow-builder/nodes) · [Build Flows](/flow-builder/building-flows) · [Keyboard Shortcuts](/flow-builder/keyboard-shortcuts) · **Condition Builder**
+- [How to write a condition](/how-to/write-a-condition) — a worked example.
+- [About conditions and the logic engine](/explanation/conditions-and-the-logic-engine)

package/dist/docs/{flow-builder → reference/dashboard/flow-builder}/keyboard-shortcuts.md

@@ -1,4 +1,5 @@
 ---
+type: reference
 layout: docs
 ---
 
@@ -63,4 +64,9 @@ These shortcuts work when the canvas of the flow builder holds the keyboard inpu
 
 ---
 
-[Overview](/flow-builder/overview) · [Nodes](/flow-builder/nodes) · [Build Flows](/flow-builder/building-flows) · **Keyboard Shortcuts** · [Condition Builder](/flow-builder/condition-builder)
+[Overview](/reference/dashboard/flow-builder/canvas) · [Nodes](/reference/dashboard/flow-builder/nodes) · [Build Flows](/how-to/build-a-flow) · **Keyboard Shortcuts** · [Condition Builder](/reference/dashboard/flow-builder/condition-builder)
+
+## Related
+
+- [How to build a flow](/how-to/build-a-flow)
+- [Canvas](/reference/dashboard/flow-builder/canvas) — the panels and the view controls.

package/dist/docs/{flow-builder → reference/dashboard/flow-builder}/nodes.md

@@ -1,4 +1,5 @@
 ---
+type: reference
 layout: docs
 ---
 
@@ -19,7 +20,7 @@ You cannot move the origin, delete it, or make a copy of it. It is always there.
 A step node stands for a screen that a visitor sees. It appears as a blue rectangle
 on the canvas.
 
-A step holds fields. Drag a field from the entity browser onto a step node to assign
+A step holds fields. Drag a field from the library onto a step node to assign
 it. The subtitle of the node gives the number of assigned fields.
 
 Each step has a `layoutName`. It tells the SDK which visual layout to use for this
@@ -43,7 +44,7 @@ right connects to the path for a true result. The red handle at the bottom right
 connects to the path for a false result.
 
 Define the rule in the inspector, with the visual condition builder. See
-[Conditions](/conditions) for more detail.
+[Conditions](/reference/dashboard/conditions) for more detail.
 
 ## Handles
 
@@ -53,4 +54,10 @@ nodes.
 
 ---
 
-[Overview](/flow-builder/overview) · **Nodes** · [Build Flows](/flow-builder/building-flows) · [Keyboard Shortcuts](/flow-builder/keyboard-shortcuts) · [Condition Builder](/flow-builder/condition-builder)
+[Overview](/reference/dashboard/flow-builder/canvas) · **Nodes** · [Build Flows](/how-to/build-a-flow) · [Keyboard Shortcuts](/reference/dashboard/flow-builder/keyboard-shortcuts) · [Condition Builder](/reference/dashboard/flow-builder/condition-builder)
+
+## Related
+
+- [How to build a flow](/how-to/build-a-flow)
+- [Canvas](/reference/dashboard/flow-builder/canvas)
+- [About how Picked works](/explanation/how-picked-works) — why a flow is a graph.

package/dist/docs/reference/dashboard/projects.mdx

@@ -0,0 +1,44 @@
+---
+type: reference
+layout: docs
+---
+
+import { Screenshot } from '../../../../components/Screenshot'
+
+# Projects
+
+A project is one site or one application that you want to measure with Picked. Each
+project has its own experiences, content, and options.
+
+<Screenshot
+  route="/{orgSlug}"
+  alt="The organization home page on the Picked dashboard, with the projects in an organization"
+/>
+
+## Workspaces
+
+Each project holds one or more [Workspaces](/reference/dashboard/workspaces). In a workspace you set the
+options for an experience and you see a preview of it before you make it live.
+
+## Project home
+
+When you open a project, you land on the project home page. It shows your SDK
+snippet and a list of the setup tasks that are still open.
+
+Copy the snippet and add it to your site. The snippet connects your site to the
+project and lets Picked serve experiences to it. See
+[SDK Installation](/reference/sdk) for the setup detail.
+
+## Project navigation
+
+The sidebar shows the sections of your project: **Feature flags**, **Fields**, **Flows**,
+**Pages**, and **Workspace settings**. **Flows** holds **Step Layouts**, and **Pages**
+holds **Page Layouts** and **Sections**.
+
+A step, an action, and a condition have no sidebar entry. You reach all three from the
+library in the flow builder, because each one belongs to a flow.
+
+## Related
+
+- [How to create a project](/how-to/create-a-project)
+- [How to install the SDK](/how-to/install-the-sdk)

package/dist/docs/reference/dashboard/reports.mdx

@@ -0,0 +1,43 @@
+---
+type: reference
+layout: docs
+---
+
+import { Screenshot } from '../../../../components/Screenshot'
+
+# Reports
+
+A report is an embedded Metabase dashboard or question, attached to a Picked project. Use
+a report to see how your visitors move through your experiences and your feature flags.
+
+<Screenshot
+  route="/{orgSlug}/{projectId}/reports"
+  alt="The reports list for a project on the Picked dashboard"
+/>
+
+## Report options
+
+| Option | Description |
+| --- | --- |
+| **Report name** | The name that the reports list shows. |
+| **Description** | An optional note about what the report shows. |
+| **Metabase report type** | `Dashboard` or `Question`. |
+| **Metabase report ID** | The numeric ID from the Metabase URL. |
+| **Display order** | Optional. It controls the position of the report in the list. |
+
+The create form has a link that opens the report, so you can check that the ID is
+correct before you save.
+
+## Permissions
+
+A member needs permission in the organization to create, edit, or delete a report. The
+dashboard hides those actions from a member without it.
+
+## Delete a report
+
+Open the report settings page and click **Delete report**. You cannot reverse a delete.
+
+## Related
+
+- [Analytics queries](/how-to/analytics) — query the same data with SQL.
+- [About PickedQL](/explanation/how-pickedql-works) — what the query layer expands.

package/dist/docs/reference/dashboard/steps.mdx

@@ -0,0 +1,37 @@
+---
+type: reference
+layout: docs
+---
+
+import { Screenshot } from '../../../../components/Screenshot'
+
+# Steps
+
+A step is one screen or card that a visitor sees during an experience. Each step
+holds one or more fields. A field collects data or shows content.
+
+<Screenshot
+  route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/steps"
+  alt="The steps list for a workspace on the Picked dashboard"
+/>
+
+## Set up a step
+
+**Name**: The name that the dashboard shows. Your visitors do not see it.
+
+**Key**: The identifier that your application uses for this step. Your
+visitors do not see it.
+
+**Layout Name**: The name of the component layout that renders this step. Examples
+are `card`, `modal`, and `fullscreen`.
+
+A step can also carry a **Step Layout**. A step layout is a reusable CMS schema, and
+it gives the step a Content Entry. See [Page and Step Layouts](/reference/dashboard/content/layouts).
+
+## Related
+
+- [How to add a step, a field, an action, or a condition](/how-to/add-a-step-field-or-action)
+
+- [How to build a flow](/how-to/build-a-flow) — add a step and assign fields to it.
+- [How to reuse a step, a field, or an action](/how-to/reuse-a-step-field-or-action)
+- [Page and step layouts](/reference/dashboard/content/layouts) — the step layout schema.

package/dist/docs/{team-management.md → reference/dashboard/team-management.md}

@@ -1,4 +1,5 @@
 ---
+type: reference
 layout: docs
 ---
 
@@ -15,28 +16,6 @@ to more than one organization.
 To move between organizations, use the organization control at the top of the
 sidebar.
 
-## Invite members
-
-1. Open your organization.
-2. Click **Members**.
-3. Click **Invite**.
-4. Enter an email address.
-5. Choose a role.
-6. Click **Send Invite**.
-
-The person that you invite receives an email with a link to join your organization.
-A person without a Picked account must create one first.
-
-## Remove members
-
-1. Open your organization.
-2. Click **Members**.
-3. Find the member that you want to remove.
-4. Click **Remove** next to the name of the member.
-5. Confirm.
-
-The member loses access to every project in the organization immediately.
-
 ## Roles and permissions
 
 Each member holds a role, and the role controls what the member can reach. A role
@@ -44,3 +23,7 @@ decides whether a member can create a project, edit an experience, control other
 members, or read a report.
 
 Give each member the smallest role that the work of that member needs.
+
+## Related
+
+- [How to invite and remove members](/how-to/invite-and-remove-members)

package/dist/docs/{workspace-versioning.mdx → reference/dashboard/workspace-versioning.mdx}

@@ -1,8 +1,9 @@
 ---
+type: reference
 layout: docs
 ---
 
-import { Screenshot } from '../../components/Screenshot'
+import { Screenshot } from '../../../../components/Screenshot'
 
 # Workspace versioning
 
@@ -22,13 +23,8 @@ The **Publish history** page lists each published version of every workspace in
 project, the newest first. The version that Picked serves now carries a **Live**
 badge.
 
-## Roll back to an earlier version
+## Related
 
-1. Open **Publish history** from the project sidebar.
-2. Find the version that you want to restore.
-3. Click **Restore**.
-4. Read the diff preview. It shows what changes between the current live version and
-   the version that you chose.
-5. Click **Restore this version** to confirm.
-
-The restored version is live immediately. Your current draft does not change.
+- [About workspaces and versions](/explanation/workspaces-and-versions) — why a roll-back
+  changes no data.
+- [How to roll back a published version](/how-to/roll-back-a-published-version)

package/dist/docs/reference/dashboard/workspaces.mdx

@@ -0,0 +1,76 @@
+---
+type: reference
+layout: docs
+---
+
+import { Screenshot } from '../../../../components/Screenshot'
+
+# Workspaces
+
+A workspace is one version of the configuration of your project. Use a workspace to hold
+a change, to see a preview of it, and to publish it when it is ready.
+
+<Screenshot
+  route="/{orgSlug}/{projectId}/workspaces"
+  alt="The workspaces list inside a project on the Picked dashboard"
+  hide={['[data-testid="workspace-row-relative-time"]']}
+/>
+
+## How workspaces work
+
+Each project has a workspace that holds your experiences, feature flags, steps, fields,
+actions, and conditions. When you make a change in the dashboard, that change stays in
+the workspace until you publish it. A change to a flow, to a feature flag, or to a step
+all behave the same way.
+
+A workspace is in one of three states:
+
+- **Live** — the workspace that the SDK serves to your visitors. Each project has
+  exactly one live workspace.
+- **Draft** — a workspace that no visitor sees. You can edit a draft, see a preview
+  of it, and publish it to make it live.
+- **Archived** — a draft that you put to one side. An archived workspace is still
+  editable, but it does not appear in the default workspaces list.
+
+## Change previews
+
+The publish modal shows a side-by-side change preview. It compares the current
+workspace against the last published snapshot. Use it to see exactly what your
+visitors get after you publish.
+
+<Screenshot
+  route="/{orgSlug}/{projectId}/workspaces/{workspaceId}/experiences?action=publish"
+  alt="The publish modal with a change preview of added experiences, steps, and conditions"
+  selector='[role="dialog"]'
+  wait='[role="dialog"]'
+  hide={['[data-testid="publish-diff-replaces-version"]']}
+  renderWidth={720}
+  renderHeight={579}
+/>
+
+The preview puts the changes into groups: experiences, feature flags, steps, fields,
+actions, and conditions. Each row shows whether the record was **added**, **removed**,
+or **modified**. For a modified record, expand the row to see which properties changed.
+
+Some changes break other records. An example is a field that you remove while other
+steps still point at it. The change preview shows a banner above the diff for these
+entries, so that you can look at them again before you publish.
+
+The first publish of a workspace has no earlier snapshot to compare against. The
+publish modal shows the contents of the workspace as the first publish, with no diff.
+
+## Unpublished changes
+
+The workspace records whether anything changed since the last publish. The toolbar then
+shows a warning badge. It counts a change to any of these:
+
+- An experience or a feature flag.
+- A step, a field, an action, or a condition.
+
+## Related
+
+- [About workspaces and versions](/explanation/workspaces-and-versions) — why a draft and
+  a version are separate.
+- [How to see a preview of a workspace](/how-to/preview-a-workspace)
+- [How to publish a workspace](/how-to/publish-a-workspace)
+- [How to archive or delete a workspace](/how-to/archive-or-delete-a-workspace)

package/dist/docs/{delivery-api → reference/delivery-api}/experience-content.md

@@ -1,4 +1,5 @@
 ---
+type: reference
 layout: docs
 ---
 
@@ -44,7 +45,7 @@ GET /api/v1/projects/:projectId/experiences/:id/content
 
 ## An HTML asset comes back in the response
 
-A layout can have an [HTML asset](/content/asset-library) field. The value of that
+A layout can have an [HTML asset](/reference/dashboard/content/asset-library) field. The value of that
 field arrives inside the response. The endpoint changes the reference to
 `{ id, content }`. There, `content` holds the HTML that you uploaded, as a string. It
 is `null` when the endpoint cannot resolve it:
@@ -85,6 +86,12 @@ curl https://api.picked.app/api/v1/projects/proj_123/experiences/exp_123/content
 }
 ```
 
-See [Project Config](/delivery-api/project-config) for the endpoint that links a step
-to an entry. See [Asset Library](/content/asset-library) for an HTML asset. See
-[Server Snapshot](/sdk/ssr/serialize) for how the SDK reads this content.
+See [Project Config](/reference/delivery-api/project-config) for the endpoint that links a step
+to an entry. See [Asset Library](/reference/dashboard/content/asset-library) for an HTML asset. See
+[Server Snapshot](/reference/sdk/ssr/serialize) for how the SDK reads this content.
+
+## Related
+
+- [About the two APIs](/explanation/the-two-apis)
+- [Project config](/reference/delivery-api/project-config)
+- [Preview, cache, and crawlers](/reference/delivery-api/preview-caching-crawling)