Browse all documentation

Browse and organize content

Configure useful list titles and columns, then search, filter, sort, select, and navigate collection content.

Open a collection list to search, filter, sort, select, and organize documents. Available columns, workflow and locale states, and actions come from the resolved schema and the current actor’s capabilities.

Give the list a useful default

content/posts.go
ridu.Collection{
  Slug: "posts",
  Admin: ridu.CollectionAdmin{
    UseAsTitle:     "title",
    DefaultColumns: []string{"title", "status", "author", "updatedAt"},
    Group:          "Editorial",
    Description:    "Draft, review, and publish site articles.",
  },
  Fields: []field.Definition{
    field.Text("title", field.Required()),
    field.Select("status", field.OneOf("draft", "review", "published")),
    field.Relationship("author", field.To("users")),
  },
}

UseAsTitle and DefaultColumns must name compatible direct fields. They change presentation only; the API path remains /api/collections/posts, and every list request still evaluates collection and field access.

Work in the list

Open Posts in the admin, then use the toolbar to:

  1. search the configured title field;
  2. add typed filters and combine them with the current locale/workflow state;
  3. sort by a supported field and choose the page size;
  4. show or hide ID, timestamps, status, nested group paths, relationships, and uploads; and
  5. select the current page or resolve a bounded filtered selection for bulk work.

The URL owns page, search, sort, filter, locale, folder, hierarchy, and trash state. Reloading or sharing an allowed URL reproduces the workspace rather than resetting to hidden component state. Per-user column/page-size choices and saved views use authenticated preferences.

Relationship and upload cells resolve readable labels through access-checked requests. A redacted field stays redacted in the table even if another user saved it as a visible column.

A Posts list in the Ridu admin showing one published post with search, filter, column, saved-view, sort, and selection controls.

Empty, failed, and large result sets

  • Clear the current search, filters, folder, locale, and trash mode before assuming content is gone.
  • A list can be empty because the collection access rule contributed a database predicate. The admin cannot reveal the number of inaccessible documents.
  • Bulk resolution accepts at most 100 unique IDs. Narrow the filter or work in reviewed batches.
  • A field absent from column/filter/sort choices may be a presentation field, unsupported nested shape, computed output, or denied by field access.

Continue with Saved views and hierarchy and Bulk actions and trash. See Querying data for the same portable filter vocabulary outside the admin.