Aggie UX 2.0 now live on aggieux.tamu.edu
In Aggie UX 2.0, we are releasing mega menu functionality for our navigation options, removing the reliance on external JavaScript libraries, and optimizing our code.
It’s official — Aggie UX 2.0 is live on aggieux.tamu.edu and on the AUX CDN!
Aggie UX 2.0 includes major changes and optimizations to our codebase (HTML, CSS and JavaScript). These changes:
- Speed up load times for sites using Aggie UX by making our CSS file 6x smaller and reducing the number of JavaScript files — even after adding functionality
- Eliminate reliance on external JavaScript libraries (jQuery)
- Increase consistency across class names, especially for component containers
- Improve accessibility through structural HTML updates across the system that are difficult to implement outside of a major change
This release also adds mega menu functionality to our site header and navigation options. While we were modifying the navigation code, we also simplified the way we talk about the different options to focus on the site identity type: lockup identity or text identity.
More Aggie UX 2.0 Roll Out Information
- March 30–31 | Upgrade all Cascade AUX sites
- April 3 | Release Figma 2.0 file
- Late March / Early April | Beta test the WordPress 2.0 theme
- April | Release the WordPress 2.0 theme
For Cascade Site Owners
Aggie UX Cascade sites will be updated on Monday, March 30 – Tuesday, March 31. No edits will be able to be made to Aggie UX Cascade sites during this time.
If you’re planning to launch a website in Cascade using the Aggie UX theme or make critical content updates between March 30–31, please email us at web@tamu.edu. We’d like to connect to discuss a planned upgrade and any potential impacts to your timeline.
For WordPress Site Owners
WordPress beta testing will be in late March/early April. We are planning on releasing the Aggie UX v2 theme in April, date dependent on any issues discovered during testing.
You will not have to install the Aggie UX v2 WordPress theme immediately when it is released. You are able to choose the time that works best for your team to test the theme in a testing environment, and then apply the theme to your production website after you have confirmed the new theme doesn’t introduce issues to your site.
For Custom Development
If you are working on custom development based on Aggie UX v1, you will still be able to reference our v1 code and documentation at aggieux.tamu.edu/v1/. However, Aggie UX v1 will no longer receive support from our team outside of critical security bug fixes.
If you are referring to any of our v1 code (CSS or JS), you will not need to update your ref links. All CDN links to v1 CSS and JS are remaining the same.