Release Planning: May 2025

The big, ASU gold "2025" statue in front of ASU's Old Main building against a blue sky.

The May 2025 Pitchfork release updates all components from the Unity Design System following package refactoring efforts from Enterprise Technology that concluded earlier this year.

The May 2025 releases for the Pitchfork theme, Pitchfork Blocks and Pitchfork People updates all components from the Unity Design System following package refactoring efforts from Enterprise Technology that concluded earlier this year. The May release also addresses minor issues uncovered during an accessibility audit also conducted by Enterprise Technology.

Updates

Enterprise Technology Unity announcements

The v2.5.0 release of the Pitchfork theme removes the deprecated component-header and component-footer packages in favor of the combined component-header-footer package. The unity-bookstrap-package package and app-webdir-ui package was also updated to the latest stable version.

These actions were taken as a result of the ASU Enterprise Technology code consolidation and reorganization effort from February 2025 (Slack).

Package version list

  • unity-bootstrap-package from 1.20.2 ➡️ 1.25.0 (latest)
  • component-header-footer introduced at 1.0.9 (latest)
  • app-webdir-ui from 4.2.1 ➡️ 5.0.3 (latest)

Deprecations

  • component-header last at 2.3.3 ➡️ removed
  • component-footer last at 2.2.2 ➡️ removed

Things to know

Image Based Cards

The Pitchfork Blocks plugin now contains new blocks for image based cards. The elements can be seen within the Unity Design Kit as well as the component explorer. There are a few things to note about the block in its current form:

  • Image based cards have fixed widths and aspect ratios as defined by the block properties.
  • When used within a grid or column-based layout, they currently do not align to standard column widths.
  • Future iterations of this element from our design kit should remove the fixed width constrain in favor of responsive options that conform to the width of their container. (Typically a column or a row block.)

Miscellaneous

Cards that represent both a call to action button or call to action link and a set of card tags have been proven to be difficult for users of assistive technology to navigate correctly. To prevent this accessibility issue, card tags created by using the post-terms block within a card context will no longer produce a link. Manual card tags created using the dedicated card-tag block do not currently provide a link option.

To deter users from accidentally altering the order of the inner blocks within any hero block, the default templates for these elements now include positional block locking by default. Altering the order of the inner blocks can cause a keyboard navigation error in which the tab sequence appears visually out of order. (WCMMA-405)