The Mayflower Component Libraries are using Semantic Versioning to convey meaning about the underlying code and what has been modified from one version to the next to help consumers keep their sites up to date with the latest features and bug fixes.
- Markup - The twig, JSX, or html code for a pattern
- Assets - The SVG icons, fonts, CSS, and JavaScript files
- Data Object - The JSON data variables used for a pattern
- Patch: consumer doesn't need to re-write any Markup, things just get better, nothing breaks just by updating
- Minor: consumer doesn't need to re-write any Markup unless specifically stated in the release notes, has access to new features available, maybe an option to do something a better way, nothing breaks just by updating
- Major: consumer has to walk through a 'migration' step to update since this will break things
Versions of Mayflower are denoted by three values 1.0.0 that represent Major, Minor, and Patch changes respectively. Major changes can contain Minor changes which can contain Patch changes. When Major and Minor versions are made the numbers to the right will always be reset to zero.
A Patch version is created to resolve issues found within a pattern in Mayflower. The changes made will only be done to Mayflower's Assets in a manner that doesn't require changes to the Markup or Data Object.
How to upgrade
A Patch version may require updating your site to use one or more newer files within Mayflower's Assets.
Example of possible changes
- CSS or JavaScript modified to resolve a styling or interaction issue (ie: link color or button trigger).
- SVG icon replaced with a new version
- Fonts changed to include additional font weights
Example Version
5.1.1 - Was done to resolve a issue found with the Rich Text Pattern. When a Table atom was added, it would appear un-styled. To resolve the issue, we corrected one of the CSS selectors from .rich-text table to .ma__rich-text table.
A Minor version is created when new features are added to an existing Pattern, a new Pattern is created, or an issue has been resolved that required Markup changes. New features will always be written as an optional extension of the existing pattern without requiring any modifications to the existing Markup or Data Object.
How to upgrade
A Minor version may require updating your site to use one or more newer files within Mayflower's Assets, enhancing an existing Pattern with new Markup or Data Object, creating new Markup and Data Object for a new Pattern, or modifying existing Markup to resolve an issue. Markup changes made to resolve an issue, will be noted in the release notes.
Example of possible changes
- New Pattern created (ie: a new button atom).
- Additional Markup or Data Object for a new feature added to an existing Pattern (ie: an optional title added to the Link List organism).
- Existing Markup enhanced to work with a new optional feature (ie: new 'ma__comp-heading--centered' css class added to the Comp Heading pattern to center the heading).
- Broken Markup, CSS, or JS changed to resolve an issue (ie: typo found in a class name, twig variable, or CSS selector)
Example version
5.4.0 - We introduced several new patterns and resolved a few issues with existing patterns. The new patterns were introduced to facilitate new Executive Order and Policy Advisory pages. We also resolved several issues we found in the previous 5.3 version.
A Major version is created when the new code will break existing code unless updates are made to the Markup or Data Object.
How to upgrade
A Major version will require carefully updating your site's Assets, Markup, or Data Object. A full site wide regression test is advised.
Example of possible changes
- Data Object updated to replace an existing variable (ie: renaming 'url' to 'href').
- Data Object changed to use a different data Type (ie: switching the 'centered' value from Type String to Type Boolean).
- Patterns renamed or moved to a new folder (ie: renaming Action Map to Google Map).
- Markup changed so it becomes dependent on new variables (ie: new 'color' variable required to set existing background).
Example Version
5.0.0 - We had to change the Data Object to introduce a new Announcement Page and fix some issues with our patterns. This page required a new pattern with a socialLinks Data Object, but that Data Object was already being used in the Footer pattern so we had to rename the existing one to footerSocialLinks. We also found inconsistency with patterns using url instead of href variables so those were all updated to use href.
The Mayflower Component Libraries are using Semantic Versioning to convey meaning about the underlying code and what has been modified from one version to the next to help consumers keep their sites up to date with the latest features and bug fixes.
- Markup - The twig, JSX, or html code for a pattern
- Assets - The SVG icons, fonts, CSS, and JavaScript files
- Data Object - The JSON data variables used for a pattern
- Patch: consumer doesn't need to re-write any Markup, things just get better, nothing breaks just by updating
- Minor: consumer doesn't need to re-write any Markup unless specifically stated in the release notes, has access to new features available, maybe an option to do something a better way, nothing breaks just by updating
- Major: consumer has to walk through a 'migration' step to update since this will break things
Versions of Mayflower are denoted by three values 1.0.0 that represent Major, Minor, and Patch changes respectively. Major changes can contain Minor changes which can contain Patch changes. When Major and Minor versions are made the numbers to the right will always be reset to zero.
A Patch version is created to resolve issues found within a pattern in Mayflower. The changes made will only be done to Mayflower's Assets in a manner that doesn't require changes to the Markup or Data Object.
How to upgrade
A Patch version may require updating your site to use one or more newer files within Mayflower's Assets.
Example of possible changes
- CSS or JavaScript modified to resolve a styling or interaction issue (ie: link color or button trigger).
- SVG icon replaced with a new version
- Fonts changed to include additional font weights
Example Version
5.1.1 - Was done to resolve a issue found with the Rich Text Pattern. When a Table atom was added, it would appear un-styled. To resolve the issue, we corrected one of the CSS selectors from .rich-text table to .ma__rich-text table.
A Minor version is created when new features are added to an existing Pattern, a new Pattern is created, or an issue has been resolved that required Markup changes. New features will always be written as an optional extension of the existing pattern without requiring any modifications to the existing Markup or Data Object.
How to upgrade
A Minor version may require updating your site to use one or more newer files within Mayflower's Assets, enhancing an existing Pattern with new Markup or Data Object, creating new Markup and Data Object for a new Pattern, or modifying existing Markup to resolve an issue. Markup changes made to resolve an issue, will be noted in the release notes.
Example of possible changes
- New Pattern created (ie: a new button atom).
- Additional Markup or Data Object for a new feature added to an existing Pattern (ie: an optional title added to the Link List organism).
- Existing Markup enhanced to work with a new optional feature (ie: new 'ma__comp-heading--centered' css class added to the Comp Heading pattern to center the heading).
- Broken Markup, CSS, or JS changed to resolve an issue (ie: typo found in a class name, twig variable, or CSS selector)
Example version
5.4.0 - We introduced several new patterns and resolved a few issues with existing patterns. The new patterns were introduced to facilitate new Executive Order and Policy Advisory pages. We also resolved several issues we found in the previous 5.3 version.
A Major version is created when the new code will break existing code unless updates are made to the Markup or Data Object.
How to upgrade
A Major version will require carefully updating your site's Assets, Markup, or Data Object. A full site wide regression test is advised.
Example of possible changes
- Data Object updated to replace an existing variable (ie: renaming 'url' to 'href').
- Data Object changed to use a different data Type (ie: switching the 'centered' value from Type String to Type Boolean).
- Patterns renamed or moved to a new folder (ie: renaming Action Map to Google Map).
- Markup changed so it becomes dependent on new variables (ie: new 'color' variable required to set existing background).
Example Version
5.0.0 - We had to change the Data Object to introduce a new Announcement Page and fix some issues with our patterns. This page required a new pattern with a socialLinks Data Object, but that Data Object was already being used in the Footer pattern so we had to rename the existing one to footerSocialLinks. We also found inconsistency with patterns using url instead of href variables so those were all updated to use href.