Repository navigation
design: filter the content list by taxonomy term - #4087
Open
eisenbruch wants to merge 1 commit into
Open
eisenbruch wants to merge 1 commit into
eisenbruch wants to merge 1 commit into
Conversation
Feature plan recording the design of emdash-cms#3046 retrospectively, per proposals/README.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
eisenbruch
marked this pull request as ready for review
October 10, 2026 17:04
12 of 19 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Design proposal
Proposal: proposals/content-list-term-filters.md
A collection's content list can be filtered by status, byline, date, text and indexed fields, but not by a taxonomy term, in the admin or over the API. This feature plan adds a
termFiltersquery parameter to the content list route and one dropdown per applied taxonomy in the admin list.It is a retrospective plan, as the transition section of
proposals/README.mdallows: #3046 was opened on September 10, 2026 and is a working prototype of the design. It stays a draft until this is accepted.Proposal type
Related work
Discussion: #3055
Implementation prototype: #3046. Original report: #3043.
Readiness
accepted(check only when ready to merge)AI assistance