Issue #3443349: Update Changelog
Compare changes
+ 525
− 0
@@ -5,6 +5,531 @@ All notable changes to this project will be documented in this file.
@@ -5,6 +5,531 @@ All notable changes to this project will be documented in this file.
This release updates the supported node to v22.11, introduces JS Linting, and new UI menu animation options that allow users to select sliding out from left/right or top down. Updated form styles and icons resolve several bug issues. Also in this release the project README file has been split it into two files, one that supports generating a theme and the other for leveraging prototype development features like build tools.
With this release the previous accordion_group component has been removed, and the accordion component has been updated with a new structure and improved styles. Enhancements have been made to the pager component, including a more comprehensive README, an updated component.yml file, and a simplified template. Theme view suggestions, which were removed in an earlier version, have now been reintroduced to improve flexibility in theme customization. The menu component has been upgraded to support more complex, nested menu structures, including menus that function without button controls.
This release includes a major overhaul of the folder structure for components and libraries as well as an updated WYSIWYG file setup. In addition the menu component has been simplified with its library files and split for better readability, this also includes new README files explaining how to best leverage the menu component. Fixes an issue with the type-scale not placing breakpoint styles in the correct order.
This release includes a fix for the typography map not taking into account differences in breakpoints. This was resulting in missing custom properties or incorrect order of typography for different breakpoints when CSS is finally built for production. The Typography CSS Custom Property mixin was rewritten to include all breakpoints and build them in the correct order.
This release includes a major overhaul of the menu components, removing the menu--navigation component and provided a more robust menu converted into vanilla JavaScript. The menu component supports setting custom mobile controls and breakpoints, and out of the box now supports arrow keys for menu navigation for better accessibility.
This release introduces several new features including Tugboat support for Drupal.org development, Cypress testing, a new slideshow component, and a new default spacing function for styling. Additionally this resolves some issues with the default teaser component and build steps failing. Gulp tasks have been converted to the new format away from the deprecated settings.
There has been a need to test and update components so that they support themes using the enforce_schema functionality with their themes. Prior to this release there were several structural and schema issues that had not been addressed that when enforce_schema was enabled caused sites to display a WOD. This release includes an overhaul of component structures and schemas to addresses those errors.
This release introduces theme configuration in Prototype for the first time, including both install defaults for block region positioning and a new setting feature that allows users to enable/disable a back to top button through the UI. With the introduction of configuration the theme generator was updated to reflect the new folder structure so that future themes are provided this functionality by default.
This release includes a major performance improvement for Prototype build tools that now listen to individual components and update changed files only, this drastically improves build time on large scale projects and a huge shoutout goes to pixelwhip for making these changes. Please note that this change can be implemented into older versions of the 5.x theme, see the update section at the bottom of this changelog.
This release includes a major fix that removes several unused props within components related to this Drupal Core issue that caused fresh installs of Prototype to only show a white screen. In addition, we included accessibility improvements such as adjusting the skip-link styles for better visibility and updating the way Prototype handled setting aria-labels within blocks.
This release includes major changes to the site header & menu components in which it replaces the site-header & site-footer with reusable menu components and removes several regions in favor of a single navigation region. This change removes the header, & progress-bar as they are no longer going to be maintained.
This update brings Prototype inline with updated SDC syntax structure. With this release there was a new branding region that was added to account for updates made to support Drupal core branding blocks. Previously deprecated code from the 4.x version of Prototype has now been removed. A new default reset file has replaced the previous Normalize file, this should offer basic reset options while preserving browser defaults for accessibility.
This update brings Prototype inline with utilizing the SDC module supported in Drupal core 10.1. There have been structural changes between the contrib module and that which now lives in core, to account for these we have updated those files to account for these changes. The composer file for Prototype no longer requires the contrib module to resolve potential module conflicts.
The 4.x release marks a move from Prototype as a starter-kit to Prototype as an actual base theme. It also shifts away from a heavy use of custom Sass mixins and functions, instead embracing future enhancements to the CSS spec enabled by the [PostCSS Env](https://github.com/csstools/postcss-preset-env) plugin. *It is not recommended to update from Prototype 8.2.x to 4.x.* Without creating a brand new sub theme. There are too many breaking changes. In reality, if you are already using Prototype 2.x, there is very little code in Prototype that would not already be overriden by your existing sub-theme.
The 4.x release marks a move from Prototype as a starter-kit to Prototype as an actual base theme. It also shifts away from a heavy use of custom Sass mixins and functions, instead embracing future enhancements to the CSS spec enabled by the [PostCSS Env](https://github.com/csstools/postcss-preset-env) plugin. *It is not recommended to update from Prototype 8.2.x to 4.x.* Without creating a brand new sub theme. There are too many breaking changes. In reality, if you are already using Prototype 2.x, there is very little code in Prototype that would not already be overriden by your existing sub-theme.