The plan ladders page and a ladder's own page hold their parts in no considered order #89

New Issue

2026-09-21T07:18:27Z

cgalo5758 commented

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

The question

The ladders page carries the topology grid, a create form, the list of ladders and four further topology subsections on one URL. The parts were normalized in the anatomy sweep and the page is still a mess: nothing says why the grid comes before the list, why four subsections belong here, or what a person is meant to do first. A ladder's own page needs the same treatment. What is each of the two pages for, and what belongs on it?

What depends on the answer

Whether the topology grid stays on the same page as the list, what moves to a ladder's page, and whether the grid can gain its second axis. Reordering tiers by dragging them inside their ladder's column requires the grid to be rebuilt from a table into columns, because a cell cannot be dragged between table rows, and the rank rows are what make it read as a grid. Today the division is stated instead: columns are dragged to order ladders, tiers are reordered on the ladder's own page.

Options known so far

One page per concern: the grid and its analyses on a topology page, the list on the ladders page, everything about one ladder on its page.
Keep one page and give it a reading order, with the subsections behind a deliberate disclosure.

Whether the grid should list ladders down the side instead of across the top is its own entry and is answered in the same round.

Decided when

Both pages have a stated purpose and a section order that follows from it, and the grid's shape is settled well enough to say whether tiers will ever be dragged in place.

Migrated from status/issues.md at b7a0e15

## The question The ladders page carries the topology grid, a create form, the list of ladders and four further topology subsections on one URL. The parts were normalized in the anatomy sweep and the page is still a mess: nothing says why the grid comes before the list, why four subsections belong here, or what a person is meant to do first. A ladder's own page needs the same treatment. What is each of the two pages for, and what belongs on it? ## What depends on the answer Whether the topology grid stays on the same page as the list, what moves to a ladder's page, and whether the grid can gain its second axis. Reordering tiers by dragging them inside their ladder's column requires the grid to be rebuilt from a table into columns, because a cell cannot be dragged between table rows, and the rank rows are what make it read as a grid. Today the division is stated instead: columns are dragged to order ladders, tiers are reordered on the ladder's own page. ## Options known so far - One page per concern: the grid and its analyses on a topology page, the list on the ladders page, everything about one ladder on its page. - Keep one page and give it a reading order, with the subsections behind a deliberate disclosure. Whether the grid should list ladders down the side instead of across the top is its own entry and is answered in the same round. ## Decided when Both pages have a stated purpose and a section order that follows from it, and the grid's shape is settled well enough to say whether tiers will ever be dragged in place. 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#89