[#75029] Document Border Box List in Lookbook

Updates Border Box references to point to higher-level Border Box List
component. Also removes old Border Box examples.

https://community.openproject.org/wp/75029

Author: myabc

lookbook/docs/components/border-box-list.md.erb

@@ -0,0 +1,147 @@
+The Border Box List component displays compact, structured list items with
+optional section headers, item actions, empty states, and a footer.
+
+## Overview
+
+<%= embed OpenProject::Common::BorderBoxListComponentPreview, :default %>
+
+## Anatomy
+
+The list is structured in up to four parts:
+
+**Header** *(optional)*
+Names the list section. It can show a count, description, action buttons, an
+action menu, and an optional collapse toggle.
+
+**Items**
+The list rows. Items can render generic row content or a work package card.
+
+**Empty state** *(optional)*
+Shown when the list has no items.
+
+**Footer** *(optional)*
+Shown below the items. Use it for summary or follow-up content.
+
+If a page shows multiple Border Box Lists and one list has a header, all
+comparable lists should use headers.
+
+## Parameters
+
+| Parameter | Type | Default | Description |
+|---|---|---|---|
+| `container` | `String`, `Symbol`, `Class`, `Object` | required | Seed used to derive stable DOM ids for the list, header, and footer |
+| `interactive` | `Boolean` | `false` | Announces counter and configured empty-state updates politely to assistive technologies |
+| `collapsible` | `Boolean` | `false` | Renders the header as a collapsible toggle when a header is present |
+| `current_user` | `User` | `User.current` | User context forwarded to work package item rows |
+| `system_arguments` | `Hash` | `{}` | Forwarded to the underlying `Primer::Beta::BorderBox` |
+
+## Slots
+
+| Slot | Description |
+|---|---|
+| `with_header` | Optional section header with title, count, description, action buttons, and menu |
+| `with_item` | Generic list row that renders the provided block content |
+| `with_work_package_item` | Work package row that renders a work package card |
+| `with_empty_state` | Empty-state content rendered when no items are present |
+| `with_footer` | Optional footer row below the list items |
+
+## Header
+
+Collapsible headers add:
+
+- an **arrow indicator** next to the title to show whether the section is
+  collapsed or expanded.
+- an optional **header description** that gives more context to the section.
+  The description is hidden when the list is collapsed.
+- an optional **counter** that displays the number of items in the section.
+
+When collapsed, the bottom border is slightly thicker to indicate that content
+is hidden.
+
+Both static and collapsible headers can include additional actions. For example,
+a menu button can offer contextual actions such as edit, delete, move up, or
+move down.
+
+<%= embed OpenProject::Common::BorderBoxListComponentPreview, :default, params: { collapsible: true } %>
+
+## Variants
+
+<%= embed OpenProject::Common::BorderBoxListComponentPreview, :playground, panels: %i[params source] %>
+
+### Work package items
+
+Use `with_work_package_item` for rows that should render a work package card.
+
+<%= embed OpenProject::Common::BorderBoxListComponentPreview, :with_work_package_items, panels: %i[source] %>
+
+### Empty state
+
+Use `with_empty_state` when the list can be rendered without items.
+
+<%= embed OpenProject::Common::BorderBoxListComponentPreview, :empty_state, panels: %i[source] %>
+
+## Uses
+
+Use the Border Box List for compact item collections such as:
+
+- meeting agenda items.
+- project attributes in project settings.
+- configured OAuth applications.
+- work package lists with card-style rows.
+
+If the content needs table structure with columns and column headers, use the
+[Border Box Table](./tables/border_box_table) component instead.
+
+## Best practices
+
+**Do**
+
+- Use section headers when the items have logical categories, such as open and
+  planned meetings.
+- Use the built-in header actions and item menus instead of composing raw
+  BorderBox rows by hand.
+- Make headers and items draggable when users need to reorder sections or move
+  items between sections.
+
+**Don't**
+
+- Don't mix sections with and without headers. If one section has a header, they must all have headers.
+- Don't make sections collapsible when users benefit from seeing all content at
+  once.
+- Don't use the Border Box List for data that needs column alignment, sorting,
+  or column headers.
+
+## Technical notes
+
+Use `OpenProject::Common::BorderBoxListComponent` instead of composing
+`Primer::Beta::BorderBox` directly when rendering OpenProject lists.
+
+## Code structure
+
+```ruby
+render OpenProject::Common::BorderBoxListComponent.new(
+  container: "project-attributes",
+  collapsible: true
+) do |list|
+  list.with_header(title: "Project attributes", count: true) do |header|
+    header.with_description { "Visible in the project overview" }
+    header.with_menu(button_aria_label: "Project attribute actions") do |menu|
+      menu.with_item(label: "Edit", href: edit_project_path(@project))
+    end
+  end
+
+  @project_attributes.each do |attribute|
+    list.with_item { attribute.name }
+  end
+
+  list.with_empty_state(
+    title: "No attributes yet",
+    description: "Add attributes to describe this project."
+  )
+
+  list.with_footer { "Last updated: #{helpers.format_date(@project.updated_at)}" }
+end
+```
+
+For lower-level details, see the [Primer BorderBox preview examples](/lookbook/inspect/primer/beta/border_box/playground)
+or the [collapsible header preview examples](/lookbook/inspect/primer/open_project/border_box/collapsible_header/playground).

lookbook/docs/components/border-box.md.erb

@@ -38,7 +38,8 @@ Some places where we already use the Inset Box:
 
 It is useful whenever content should stand out from the page background while staying lightweight.
 
-If content needs more structure (e.g., with headers, actions, or multiple items), consider using the Border Box component instead.
+If content needs more structure, such as headers, actions, or multiple items,
+consider using the Border Box List component instead.
 
 ## Best practices
 
@@ -51,7 +52,8 @@ If content needs more structure (e.g., with headers, actions, or multiple items)
 
 - Don’t apply arbitrary custom background colors in CSS — use the component’s options.
 - Don’t duplicate "grey box" styles manually; always use the Inset Box.
-- Don’t use Inset Box if a more structured component (like Border Box) is better suited.
+- Don’t use Inset Box if a more structured component, such as Border Box List,
+  is better suited.
 
 ## Technical notes
 

lookbook/docs/components/inset-box.md.erb

@@ -31,7 +31,8 @@ Some examples of where we already use the Border Box table:
 - to display a list of configured OpenID providers
 - to display a list of configured SCIM clients
 
-If the content does not need a table structure with column headers and grids, please use the simpler [Border Box](../border_box) component instead.
+If the content does not need a table structure with column headers and grids,
+please use the simpler [Border Box List](../border_box_list) component instead.
 
 ## Technical notes
 

lookbook/docs/components/tables/border-box-table.md.erb

@@ -31,6 +31,7 @@
 module OpenProject
   module Common
     # @logical_path OpenProject/Common
+    # @display min_height 400px
     class BorderBoxListComponentPreview < ViewComponent::Preview
       # @label Default
       # @param interactive toggle