Author: Digital Solutions
Deployment
We usually push new code to the platform on Thursdays, however this sprint the code will deploy on Saturday. One of our customer websites is changing from .com to .gov and they were concerned about this taking place during the work week. Sprint 56 will launch on Saturday, May 31, 2025.
New Features
- Platform responsiveness: Code was improved to conditionally load Paragraph Component JavaScript and CSS assets only when necessary to increase responsiveness. We did a lot behind the scenes, moving paragraphs around in the code, so that when you visit a page, only the JavaScript and CSS needed for that particular page is loaded. Your site will load much faster now.
- The Event Creator role only has permission to create and publish the Event content type. Events can include a main image, but Event Creators did not have the ability to upload media to the library. Event Creators can now add new images to the media library and delete images they have uploaded themselves. They cannot delete others' media. Thanks to Web Manager Kaytee Smith for bringing this to our attention.
- Profile Cards with Links and the Blog Grid View have a new border upon rollover consistent with the new styling released in Sprint 55.
Updates & Fixes
- Accordions were behaving inconsistently. When a user expands an accordion, the named anchor (#anchor) should appear in the browser's address bar at the end of the URL. Sometimes the anchor appeared, and many times it did not; this made it difficult to link directly to an Accordion item. We've corrected this. Thanks to Web Manager Jim Webb for reporting this issue via ServiceNow.
- Catalogue Items were showing the link and computer icon in the wrong place when viewed on mobile. This was corrected.
- Button Links had inconsistent spacing when viewed in Edit mode after the changes to button styling we made during Sprint 54. We corrected it so that now Edit mode and View have the same spacing.
- Code Cleanup for Sidebar Paragraphs within Tabs/Accordions: The aside element was contained in another landmark and should be at top level. This accessibility issue was fixed within the code.
Incase you Missed it
Improvements shared during our last Sprint Review 55 on