Skip to content

Compass - Address feedback & updates from design #273

@nicolethoen

Description

@nicolethoen

Epic: Compass - Address Feedback & Updates from Design


1. Problem Statement & Goal

What problem are we solving or opportunity are we seizing for our users?
The initial drop of the Compass PoC components (Epic #269) was a fantastic starting point. However, the design work is constantly evolving, and concurrently, early adopter teams are now finding functional gaps, bugs, and usability issues as they implement Compass in their own Proofs of Concept (POCs). The risk is twofold: the PatternFly implementation falls behind the live Compass design, and it doesn't meet the real-world functional needs of the teams trying to use it. Our UI Engineers and Designers can't truly test or adopt this theme until we close the feedback loop from both design and implementation teams, integrate key design polish, and start tackling responsiveness and accessibility. We need to stabilize and refine what we have to support early adoption.

What's our main objective?
We want to empower Design, Product, and early adopter teams to provide detailed, actionable feedback so we can get these PatternFly prerelease components much closer to the final Compass vision. The goal is a stable, high-fidelity, and functionally complete foundation for the theme, ready for broader early adoption and further iteration.

How will we measure success?

  • Design Alignment: Successfully implement and get initial acceptance on the highest priority design iteration issues filed against the prerelease.
  • Adopter Readiness: Successfully address the highest priority functional and feature gap feedback reported by the early adopter teams (from the linked spreadsheet).
  • A11y Headstart: Complete a preliminary A11y review and fix any immediately obvious, high-severity keyboard or WCAG issues. We want to clear the major speed bumps.
  • Responsiveness Implemented: Ship the initial implementation of the mobile layout designs to ensure components scale correctly.

2. Scope & Completion

High-Level Acceptance Criteria / Definition of Done: What does "good enough" look like for this scrappy epic?

  1. All highest priority design feedback issues raised against the Compass prerelease (as filed by the Design team) are implemented and merged.
  2. The highest priority functional/bug/feature gap issues identified by the early adopter POC teams (tracked in the linked spreadsheet) are triaged, implemented, and merged.
  3. The team completes a visual fidelity check-in with the Design team and receives their acceptance that the refinements are tracking in the right direction. (We're skipping a "formal" sign-off for now.)
  4. A preliminary accessibility review is completed, and all critical (severity 1 & 2) issues identified during this review are resolved. (Initial sign-off from A11y specialist required, confirming no major blockers.)
  5. Mobile layout designs are implemented and functional.
  6. The updated, polished, and functionally improved components are delivered and released in a new PatternFly prerelease version (e.g., v6.5.0-prerelease.x).

Child Stories/Issues:

  • Primary Stories (Design): All issues filed by the Design team to capture necessary implementation work, linked here: [Link to JIRA/GitHub Project Board Filter for Compass Design Issues]
  • Primary Stories (Adopter Feedback): Dedicated stories to capture and implement the highest priority feedback from the early adopter spreadsheet.
  • A11y Story: Dedicated story for the preliminary A11y review and remediation.
  • Mobile Story: Dedicated story for implementing mobile-specific responsiveness and designs.

3. Supporting Information & Communication

Key Relevant Links

Communication Plan

  • Twice a week, dev and design will have optional team working sessions for feedback gathering, problem solving, and ongoing communication.

4. Effort & Open Questions

This epic is timeboxed to one sprint worth of work.

Sub-issues

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions