Current analysis suggests that Search, Taxonomy, and Atlas are not fundamentally different page types. Each acts as a content context that assembles collections of entries and displays them grouped by content type. The primary differences exist in how the collections are populated, not how they are rendered.
The goal of this task is not a visual redesign but an architectural refactor. The objective is to identify common rendering patterns and extract reusable components that can be shared across all three systems. Potential candidates include section rendering, card rendering, content grids, section headers, and template resolution logic.
Search currently appears to provide the strongest content browsing experience and may serve as the baseline for future collection presentation. Atlas currently maintains separate rendering logic despite displaying content in a very similar structure, creating unnecessary divergence and increasing long-term maintenance costs.
Desired outcome:
- Create a shared collection rendering layer.
- Standardize section and card rendering across Search, Taxonomy, and Portal views.
- Keep query-building and context logic separate from presentation logic.
- Reduce duplicate templates and rendering code.
- Preserve portal-specific elements such as hero sections, metrics, and navigation while sharing the underlying content display system.
- Evaluate whether Atlas should adopt the same collection presentation patterns currently used by Search and Taxonomy.
Priority: Low. Architectural cleanup and future maintainability task rather than an immediate user-facing issue.