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

package/dist/docs/steps.mdx

@@ -1,53 +0,0 @@
----
-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"
-/>
-
-## Create a step
-
-1. Open your project.
-2. Click **Steps** in the sidebar.
-3. Click **New Step**.
-4. Enter a name and a key.
-5. Click **Create**.
-
-The key is a unique identifier for your application. You set it once, and you cannot
-change it later.
-
-## 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](/content/layouts).
-
-## Assign fields
-
-In the flow builder, drag a field from the entity browser onto a step node. The field
-appears in the **Assigned Fields** list of the step, in the inspector.
-
-You can also choose the step node and expand the **Assigned Fields** section to see
-and control the assigned fields. Click a field to open its inspector.
-
-## Reuse steps
-
-A step is a project-level entity. You can drag the same step into more than one
-experience flow. A change to the options of a step applies at every place that uses
-it.

package/dist/docs/workspaces.mdx

@@ -1,133 +0,0 @@
----
-layout: docs
----
-
-import { Screenshot } from '../../components/Screenshot'
-
-# Workspaces
-
-A workspace is one version of the options for 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, and entity
-options. 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 an entity 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.
-
-## Preview
-
-See a preview of your workspace to learn how a change looks before you publish it.
-
-1. Click **Preview** in the workspace toolbar.
-2. Enter the URL of your site.
-3. Set each feature flag to the **Default**, **On**, or **Off** value. This step is
-   optional.
-4. Click **Open Preview**.
-
-Your site opens in a new tab with the unpublished workspace applied. The preview
-sends the workspace state to the SDK in the query parameters, so the visitors on
-your live site see no change.
-
-## Publish
-
-When you publish, Picked makes an immutable snapshot of your workspace. The SDK then
-serves the new options to your visitors.
-
-1. Click **Publish** in the workspace toolbar.
-2. Read the change preview in the publish modal.
-3. Click **Publish** to confirm.
-
-The publish button is active only when the workspace has an unpublished change. A
-status badge in the toolbar shows whether the workspace has an unpublished change or
-is up to date.
-
-## 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 by entity type: experiences, feature flags,
-steps, fields, actions, and conditions. Each row shows whether the entity was
-**added**, **removed**, or **modified**. For a modified entity, 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. If you create
-or update an experience, a feature flag, or an entity after the last publish, the
-toolbar shows a warning badge.
-
-## Workspace settings
-
-The workspace settings page (**Settings** in the workspace navigation) covers how to
-rename, archive, and delete a workspace.
-
-### Rename
-
-Change the workspace name in the **Name** field and click **Save**. A name is unique
-inside a project. The dashboard rejects a duplicate name with a validation error.
-
-### Archive
-
-To archive a draft workspace is to move it out of the default workspaces list, but
-not to delete it. Use it for a draft that you want to put to one side and keep.
-
-1. Open the workspace settings page.
-2. Click **Archive** in the page header.
-3. Confirm in the modal.
-
-You cannot archive a live workspace directly. Make a different workspace live first,
-then archive the earlier one.
-
-### Unarchive
-
-You can unarchive a workspace from the same page to make it a draft again. The
-settings page finds the archived state and changes the toolbar button to
-**Unarchive**.
-
-### Delete
-
-To delete a workspace is to remove it and its entities permanently. This action is
-destructive and you cannot reverse it. Archive the workspace instead when you are not
-certain.
-
-1. Open the workspace settings page.
-2. In the **Danger zone** card at the bottom, click **Delete**.
-3. Confirm in the modal.
-
-You cannot delete a live workspace. Publish or archive a different workspace first.