Review the parent feature CRCPLAN-399 for additional context, including the feature overview, goals, user stories and use cases, acceptance criteria, designs, dependencies, risks, assumptions, pending questions and documentation callouts.

Summary and goal

This epic describes the work to integrate and apply the PatternFly 6 motion design standards across the Hybrid Cloud Console's core user interface components.

Purpose and Intent (The "Why")

The primary goal is to raise the overall quality and usability of the Hybrid Cloud Console experience by aligning with PatternFly 6's motion design. This work ensures:  

• Consistency: All front-end transitions will utilize standardized PatternFly motion tokens (duration, easing, properties) to ensure a unified and predictable experience.
• Inclusivity/Accessibility: The implementation will respect the user's operating system preferences, specifically the prefers-reduced-motion setting, by providing fallbacks or disabling effects for users who require them.
• Modernization: This work solidifies the core console's adoption of the PatternFly 6 ecosystem, allowing us to leverage future component updates and best practices.

Scope

In scope

• Motion Token Integration: Implement and make accessible the complete set of PatternFly 6 motion design tokens (e.g., short/long durations, specific easing curves) within the Hybrid Cloud Console’s core styling layer.
• Core Component Application: Apply the PatternFly 6 motion patterns (Slide in/out, Fade in/out) to key global, platform-managed components:
  • Primary Side Navigation (drawer/context panel behavior).
  • Global Modals and Wizard transitions.
  • System-level Alerts and Toast notifications.
• Accessibility Implementation: Ensure all applied motion effects are conditional and disabled/reduced when the user's OS or browser preference for reduced motion is detected.
• Initial Audit: Completion of an initial audit to prioritize application of motion to high-traffic components.
• Documentation: Update internal developer documentation for utilizing the new tokens and update the Tenant Guide for app builders.

Out of scope

• Per-Tenant Component Migration: This epic excludes the audit and application of motion to components within individual tenant bundles. Tenants are responsible for updating their own bundles to the extent enabled by self-service facilities.
• Custom Animations: Creating new, non-standard animations or motion effects outside of the PatternFly 6 guidelines is excluded.
• Back-end/Performance: Work related to API response times or server-side rendering is a separate concern.
• User Preference Override: Implementing a user-facing setting to override the OS/browser's reduced motion preference is excluded; this work may be specified in a successor epic if demand signal warrants.

Size and dependencies

• Estimated Effort/Complexity: Large (Foundational work impacting core UI across the platform).
• Dependencies: This Epic depends on the completion of CRCPLAN-326 to ensure the core components are on the correct version.
• Risks: No material risks are anticipated. PatternFly motion effect classes degrade gracefully if in-scope components have not completed their PF6 migration in time.

Acceptance Criteria 

* Code Complete: PatternFly 6 motion tokens are successfully integrated and accessible across all relevant core console UI packages.

• Core Components Updated: Motion effects are successfully implemented on the Primary Side Navigation, Global Modals, and System Alerts, in full alignment with PatternFly 6 Motion principles.
• Visual Validation: A Design/UX sign-off is secured, confirming the motion effects (timing, easing, type) match the official PatternFly 6 guidelines.
• Accessibility Verified: A QE sign-off is secured, confirming that all applied motion effects correctly respect the prefers-reduced-motion setting to ensure an inclusive experience.
• Documentation: Both internal documentation for engineers (outlining how to use the new tokens) and the Tenant Guide for app builders are updated accordingly.

Checklist

Open Questions

Input from UXD and the PatternFly team, expected in the near future, will inform the initial audit scope item and provide further guidance on prioritization of specific effects.