Proposal: add category/tag filters to admin content list

[khiemnguyendinh]

Problem

The admin content list supports search, status, author and date filters, but it does not provide category/tag filters.

For sites with many posts, editors need to find content by taxonomy before editing, reviewing or publishing.

Proposed scope

Add taxonomy filters to the admin content list:

• Category filter
• Tag filter
• Support collections that have custom taxonomies
• Preserve existing search, status, author, date and locale filters
• Store filters in the URL so the view can be shared or refreshed
• Apply filtering server-side before pagination
• Preserve cursor pagination and nextCursor
• Provide a clear/reset filters action
• Show a useful empty state when no content matches

Proposed filter semantics

• Multiple terms within the same taxonomy: OR
• Different taxonomies: AND
• Category descendant behavior: open for maintainer decision
• No taxonomy assigned: preserve current unfiltered behavior

Implementation direction

Reuse the existing taxonomy model and taxonomy APIs instead of adding a second taxonomy system.

Likely admin integration points:

• packages/admin/src/components/ContentList.tsx
• packages/admin/src/router.tsx
• packages/admin/src/lib/api/content.ts
• The server-side content list query/endpoint
• Integration and end-to-end tests

The current taxonomy editor already exposes taxonomy and term APIs through TaxonomySidebar, so this proposal is primarily about list-query support and admin UX.

Acceptance criteria

• Filtering happens before pagination, not only on the currently loaded rows
• Category and tag filters work together
• Existing filters continue to work
• Empty, invalid and cleared filters are handled safely
• Tests cover filtered and unfiltered queries
• Tests cover cursor pagination
• Tests cover the supported database adapters
• Admin strings use the existing Lingui workflow

Related context

• Issue fix(admin): content list only loads 50 items, no infinite scroll for large datasets #129 highlights the importance of preserving server-side content-list pagination.
• Issue Taxonomy filter on collections fails silently on Postgres: SELECT DISTINCT * is invalid when content table has a json column (e.g. portableText field) #1355 shows that taxonomy filtering needs coverage across supported database adapters.

Questions for maintainers

1. Should the first version support only category and tag, or every taxonomy attached to a collection?
2. Should selecting a parent category include descendant categories?
3. Is OR-within-taxonomy and AND-between-taxonomies the preferred behavior?
4. Is a generic taxonomy query structure preferred for the API?
5. Is a changeset required for this admin feature?

AI disclosure

This proposal was prepared with AI assistance. Human review, implementation and testing will be performed before submission.