Public Group directory with filtering (topic, location, language)
Problem / Motivation
Discoverability is a major pain point; a filterable directory is Must Have.
Updated 2026-07-22: foundation is the Group module (drupal/group) per André — group entities + group permission mechanism + customized Group membership relationship; OG still excluded.
Proposed resolution
Build a directory page (e.g. /groups) with Views over the group entity:
- Base query: published group entities, not archived, visibility = public (Group access also enforces this — see #3578785).
- Combinable exposed filters: Type/Topic (taxonomy), Location, Primary language.
- Ensure the directory is indexable by external search engines.
Location strategy (phased): (1) free-text “contains” filter; (2) taxonomy-backed regions/countries; (3) geospatial search (future).
Acceptance criteria
- Anonymous users can browse
/groups. - Filters work and can be combined.
- Directory excludes archived and non-public Groups.
- Directory performance is acceptable at expected scale.
Pipeline
Suggested review-rigor: panel — both an access-leak risk (archived/private must never appear) and a performance-at-scale concern.
UI surface: directory page + filter UI (Designer wireframe + UI walkthrough apply).
Source: DA-New Groups — MVP PRD (Google Doc). Target Drupal core version per the project's core-version decision (see #3578750).
Part of the MVP epic #3578778.
Proposed approach (reference — not yet decided)
A proposed approach for this exists in the D11 Migration docs (imported via !28 (merged)), reflecting an Open Social → standard Drupal conversion built on the contrib drupal/group module. Treat it as a reference proposal, not a decision — whether this project adopts that schema is still open (see the data-model decision in #3578779). See: Views & Endpoints, Runbook.