Should the two operator pages for plans be one page #90

New Issue

2026-09-21T07:18:27Z

cgalo5758 commented

2026-09-21 07:18:27 +00:00

The question

Plan Ladders configures the ladders and their tiers. Plan Topology reads every ladder at once as a grid. They are two views of one thing and they sit side by side as sibling entries in the navigation. Should they be one surface, where the grid is the overview of the page that also configures, and if so does that page stay a top-level entry or become a child of Products?

What depends on the answer

The navigation contract, which fixes what appears at the top level and forbids children under a rail entry, and the shape of the grid if it becomes a section of a longer page rather than a page of its own.

Options known so far

Keep two entries and cross-link them.
One page that reads and configures, replacing both entries.
One page nested under Products, on the argument that a ladder is a way of arranging products.

Decided when

The operator information architecture states which plan surfaces exist and where each sits. Low priority: nothing is wrong today, the pages are merely two.

Migrated from status/issues.md at b7a0e15

## The question Plan Ladders configures the ladders and their tiers. Plan Topology reads every ladder at once as a grid. They are two views of one thing and they sit side by side as sibling entries in the navigation. Should they be one surface, where the grid is the overview of the page that also configures, and if so does that page stay a top-level entry or become a child of Products? ## What depends on the answer The navigation contract, which fixes what appears at the top level and forbids children under a rail entry, and the shape of the grid if it becomes a section of a longer page rather than a page of its own. ## Options known so far - Keep two entries and cross-link them. - One page that reads and configures, replacing both entries. - One page nested under Products, on the argument that a ladder is a way of arranging products. ## Decided when The operator information architecture states which plan surfaces exist and where each sits. Low priority: nothing is wrong today, the pages are merely two. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

design

area/catalog area/operator-ui labels 2026-09-21 07:18:27 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#90