Content Drive: Search
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Description
Content Drive lacks advanced search capabilities. Users cannot filter by content type-specific fields, workflow state, or date ranges — finding specific content in large repositories requires knowing exact titles or browsing folder hierarchies manually.
Solution: A chip-based filter bar with dynamic columns, workflow filtering, type-specific searchable fields, and multi-site awareness. Replaces the current search form with a composable filter model where all filters use AND logic and stack as clickable chips. Asset preview is absorbed inline when selecting items.
Information Architecture
Top Bar: Global search input ("Type a name, tag, or metadata to find content..."). Stacks with all active filters — no longer drops the folder selection. Includes "Clear all" inline.
Left Sidebar: Simplified folder tree — no tabs, no search form. Site name as root node with home icon; "Shared Content" node at top for system host content (no sub-folders).
Main Content Area: Filter chips bar + listing table.
Filtering Model
All filters use AND logic and stack as clickable chips.
Default chips always visible: Folders, Base type, Content type, Language, Workflow.
"More" button opens a searchable dropdown picker with:
- Recently used filters
- System filters: Status, Modified date, Created date, Modified by, Owner, Title/Name
- Content type fields (when exactly one content type is selected)
Workflow chip: Two-level selector — scheme (single select) then step (multi-select).
Dynamic Columns
When exactly one content type is selected, fields marked listed: true appear as additional sortable columns (8 field types supported).
System Host Content
Rows from system host display a visual indicator. "Shared Content" node in the folder tree controls visibility.
Dependencies
- Content Drive Phase 1 (base navigation and listing)
- Content type schema API (field definitions, searchable/listed flags)
- Search API support for field-level filtering
- Workflow scheme/step data
Out of Scope (v1)
- Saved/bookmarked searches
- Workflow grouped view (Kanban)
- AI-powered search suggestions
- Calendar view, gallery view
- Full-text content body search
Desired Outcome
Content authors can find specific content quickly using composable filters without losing their folder context — no more manual folder browsing for content they can't exactly name.
Success signals:
- Content teams successfully use filter chips to locate content by type, workflow step, and date range
- Dynamic columns appear correctly when a single content type is selected
- Keyword search stacks with folder selection instead of resetting it
- Site admins can distinguish system host content via visual indicator
User Stories:
- Rose (Content Creator): Filters blog posts by workflow step, uses keyword search without losing folder selection, filters by modified date, sees type-specific fields like "Author" when filtering by Blog.
- Luca (Content Architect): Knows that marking fields as searchable surfaces them in the filter picker; trusts that listed fields appear as dynamic columns.
- Jayden (Site Administrator): Filters by workflow scheme and step; sees system host content clearly marked.
Target Personas
- Content teams
Links
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Content Drive Phase 1, the content type schema API, search API field-filtering support, and workflow scheme/step data. Done means the chip-based AND filters, dynamic columns, preserved folder context, and system-host indicators meet the listed success signals; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, frontend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100