Content entities - Admins can customize columns (especially using custom fields)

[kodster28]

Description

Publishing teams frequently will have custom metadata that they add to different content types, such as internal ticket numbers. They often want the ability to see this metadata from the content entity listing view, as well as to search that field too.

Steps to reproduce

n/a

Environment

emdash: 0.29.0, Cloudflare Workers

Logs / error output

[saariuslystoned]

I checked current main and the related work. Discussion #1717 already proposes the smallest collection-wide design for custom field columns, while #1133/#1973 separately cover configurable Title/Date fields.

Current list rows already include all custom field data, and the manifest includes field labels/types/options, so v1 should not require extra per-row requests. I propose:

• collection-level admin.listColumns with at most four supported scalar fields;
• existing Title/Status/Locale/Date/Actions unchanged;
• no custom sorting, filtering, references, plugin cells, or per-user preferences in v1;
• field visibility remains separate from the existing searchable flag.

Search infrastructure already indexes fields marked searchable, and D1's FTS path searches them. The remaining gap is that the fallback path only searches slug/title/name. I would separately make it include all fields marked searchable, preserving the current FTS path and query count.

Could a maintainer confirm whether #1717's collection-wide design is approved for this issue, whether v1 needs Content Type UI configuration, whether search should include every searchable field rather than only visible columns, and whether #1973 should land first?

[logelog]

Quick update: I split the work into focused PRs so each part can be reviewed independently.

• fix(content): search searchable custom fields #2191 makes configured custom fields searchable
• feat(admin): show configured fields in content lists #2194 shows configured custom fields as content-list columns
• feat(admin): allow trusted plugins to add content list columns #2195 adds typed, fail-safe content-list columns for trusted plugins
• feat(content): support indexed custom field sorting #2212 adds server-side sorting for indexed custom fields
• feat(content): filter indexed custom fields #2213 adds server-side filtering for indexed custom fields

The goal is to support custom metadata such as ticket numbers, priority/status fields, SEO scores, and similar plugin or collection fields without client-side full-table scans. Display, search, sorting, and filtering are split so pagination stays server-driven and each contract remains reusable by collections and plugins.

[kimberly-WY]

Confirmed reproducible on Node 20 + macOS. Interestingly it doesn't happen if you set NODE_OPTIONS=--max-old-space-size=512.