Infrastructure Exploratory

[dlabaj]

Description

This initiative is around exploring possible solutions (AKA: Spikes) for problems within our build and release infrastructure. The main focus of the epics within this initiative are build improvements that will achieve one or more of the following:

• Reduce build time by 10% or more to allow the team to deliver software faster
• Considerably improve the design and development experience either internally (PattenFly team) or externally (Consumers of PatternFly)
• Improve the quality of products by reducing the number of bugs, providing data that will allow us to improve the customer experience, provide data that will improve the teams reaction time to issues. Some examples of this include ability track mean time between build failures, overall user engagement, notifications via tools such as IM / email.

This initiative is focused on spikes only and not on the delivering of the final products / procedures.

[dlabaj]

Possible Areas to improve (these may already have issues):

• Surge replacement for PR preview.
• Bundle size improvements, public facing API
• Build improvement for documentation site to improve speed.
  • Typescript build takes awhile
  • TSDoc build time
  • File size might be a little to large see during migration
• Automatic release so it's not manual
• Dashboard
  • Move away from github authentication to get information for github queries.
  • A way to store the results the runs of the last time it ran to show that to the user (micro db)
  • Add snyk if possible ...
  • Notification of build failure (slack, email)
• DRY up - CI config
• Core updates
  • Handle bars replacement (syntax is area of concern, how easy is it to move from our current solution to handle bars)
  • Astro / Svelte integration
• A11y parallel testing
• Building out replacement for sematic release and manage release from the dashboard
  • Do a release (e.g. Release button)
• React 19 support
  • React compiler
• Visual Regression Testing
  • Have as part of CI across all repos
  • CORE: Automation of visual regression testing (Play wright, Console dot regression tool, Percy)
• Analytics
  • What do we do with the analytics we have?
  • Additional information we can collect?
    • Google Analytics (Fix this currently broken)
    • Angola search (Site collection)
    • UI for analyzing the json data for how PatternFly is used in products