Plan

A deal’s or account’s plan in a context panel: its written sections in full, each folding under its heading, then its milestones. The text is designed; the milestone timeline has no design yet, so it needs design review.

Installation

import { Plan } from "@o/pipeline/experimental/blocks/plan";

Usage

2d ago via slack

Susanna confirmed pricing and platform fit, but the Salesforce evaluation is blocking progress. Pricing presented; formal demo agreed, still pending.

Design partner agreement signed, with implementation aligned to their CRM timeline.

Pass the written sections as sections, each an id, a title and its content, in order and as many as the plan has. An editable plan passes its empty sections too, with a placeholder in place of their text; a read-only one leaves them out. updated says when and by whom the plan last changed, at the header’s end. Nothing truncates; the whole plan renders in place. With onSeeAll, “See all” follows the plan, as every block’s does, where the app opens its fuller view.

The block is open by default and collapses from its header; open, defaultOpen and onOpenChange control it.

Editing

With onEdit, clicking or focusing a section’s text calls it with the section’s id; pass that id back as editingId with your editor, which shows in place of the section’s text. Without onEdit, the plan is read-only. footer adds controls under the plan, such as its history and whether Operate suggests edits.

2d ago by Jane Cooper

Susanna confirmed pricing and platform fit, but the Salesforce evaluation is blocking progress. Pricing presented; formal demo agreed, still pending.

Design partner agreement signed, with implementation aligned to their CRM timeline.

Add a note…

Read-only

In a chat, the plan is read-only, with a button in footer that opens it to edit.

5h ago by Operate

Susanna confirmed pricing and platform fit, but the Salesforce evaluation is blocking progress. Pricing presented; formal demo agreed, still pending.

Design partner agreement signed, with implementation aligned to their CRM timeline.

Milestones

Pass the plan’s milestones as PlanMilestones in milestones. Each is a PlanMilestoneRow on one timeline, with PlanMilestoneNow where today falls and history folded into older. The rows’ marks, dates, assignees and menus are the app’s, as slots: this part only lays them out. The Figma has no design for it yet, so it needs design review.

2d ago by Operate

Susanna confirmed pricing and platform fit, but the Salesforce evaluation is blocking progress. Pricing presented; formal demo agreed, still pending.

Text

PlanText is the text body on its own, for any block that reads as a short document under headings.

import { PlanText } from "@o/pipeline/experimental/blocks/plan";

Loading

While the plan loads, the block draws its sections as placeholders, in place, inside a loading SkeletonGroup.

Empty

With no sections and no milestones, the block is one row: its title and empty (“Nothing planned yet.” by default), which can hold a control, such as one that opens an archived plan. With a footer or onSeeAll too, empty sits under the header with them after it, so their controls and the way to the app’s fuller view stay.

Deal plan
No plan yet.