Goal
Surface community prioritized collections in the Search view through two integration points to help users discover community-prioritized articles.
Design
This task covers two different surfaces for integrating nominated collections into the search journey:
Surface 1: Default search view (empty state)
Shows community priority articles when user hasn't started searching yet.
 |  | |
Visibility
- Section appears in default search view when no search query is entered
- Priority order: Community Priorities > Recently edited by you > Nearby
- If target language has a nominated collection → show "Community Priorities" (for all users, regardless of translation history)
- Hides when user starts typing a search query
- Only displays when the user's target language has a community nominated priority collection
Section content
Section header:
- Label: "Community Priorities"
- Description: "Articles the community selected as important to translate"
Article Display:
- Shows 3 individual articles from nominated collection(s)
- No collection badge displayed on articles
Placement
- Positioned directly below language selector buttons
- Appears in place of "Nearby" section for new users
- For experienced users, "Recently edited by you" appears first instead
- Clicking an article navigates to translation confirmation step
Visual Design
- Follows existing pattern of "Nearby" and "Recently edited" sections
- Header: @color-subtle (#72777d)
- Description: @color-subtle, @font-size-small
Surface 2: Search Results View (Active Search)
 |  | |
When user enters a search query, show visual indicators on articles that belong to the community-nominated priority collection.
Visibility
- Badge appears on search result articles that are part of the target language's community priority collection
- Shows for all users (both new and experienced) during active search
- Only appears when search query is entered (not in empty state)
- Badge displays regardless of user's translation history
Badge design
Badge label:
- Text: "Community priority"
- Icon: cdxIconUserGroup (user group icon, left of text)
Visual treatment:
- Background: @background-color-progressive-subtle (light blue)
- Text color: @color-progressive (blue)
- Icon color: @color-progressive (blue)
- Border-radius: @border-radius-pill (fully rounded)
- Padding: @spacing-12 (vertical), @spacing-50 (horizontal)
- Font-size: @font-size-small
- Font-weight: @font-weight-normal
- No box-shadow (flat appearance)
Placement
- Badge appears in article metadata row
- Positioned before the language count indicator
- Layout: [Community Priority badge] • [language count]
- Separator: Standard dot separator
Interaction
- Badge is non-interactive (no hover state, no click action)
- Purely informational indicator
- Clicking the article card navigates to translation confirmation step
Below is the updated version with all acceptance criteria consolidated within each test case, while preserving scope, intent, and required formatting. No design-related checks have been introduced.
Derived Requirement
Ensure that community-nominated priority collections are functionally surfaced in the Search view to support article discovery and navigation. When the target language has a nominated collection, eligible articles must be exposed in the default (empty) search state and correctly identified during active search. When no nominated collection exists, search behavior must remain unchanged.
Test Steps
Test Case 1: Surface Community Priority Articles in Default Search View (Empty State)
Preconditions
- The user has selected a target language that has a community-nominated priority collection.
- No search query has been entered.
- Open Wikipedia using the Minerva skin.
- Navigate to the Search view.
- Ensure the search input field is empty.
- Observe the content displayed in the default search view.
- Select one of the surfaced articles sourced from the nominated collection.
- ✅❓❌⬜ AC1: Confirm that community-nominated priority articles are displayed only when no search query is entered and the target language has a nominated collection, and that selecting an article navigates to the translation confirmation step.
Test Case 2: Hide Community Priority Content When Search Becomes Active
Preconditions
- The target language has a community-nominated priority collection.
- Open the Search view with no query entered.
- Begin typing a search query into the search input field.
- Observe the Search view content as results load.
- ✅❓❌⬜ AC2: Confirm that community priority content shown in the empty search state is no longer displayed once a search query is entered.
Test Case 3: Identify Community Priority Articles in Active Search Results
Preconditions
- The target language has a community-nominated priority collection.
- Navigate to the Search view.
- Enter a valid search query.
- Review the list of returned search results.
- Select a result that belongs to the community-nominated priority collection.
- ✅❓❌⬜ AC3: Confirm that community-priority articles are identifiable during active search and that selecting such an article navigates to the translation confirmation step.
Test Case 4: Preserve Default Search Behavior When No Nominated Collection Exists
Preconditions
- The selected target language does not have a community-nominated priority collection.
- Open Wikipedia using the Minerva skin.
- Navigate to the Search view with an empty search query.
- Observe the default search view content.
- Enter a search query and observe the search results.
- ✅❓❌⬜ AC4: Confirm that no community-priority content or indicators are shown in either empty or active search states and that search behavior and navigation match the current implementation.
QA Results - TestWiki
| AC | Status | Details |
|---|---|---|
| 1 | ✅ | T408842#11488153 |
| 2 | ✅ | T408842#11488153 |
| 3 | ✅ | T408842#11488153 |
| 4 | ✅ | T408842#11488153 |