WebTech and University Marketing have been working for the past 10 months on a major visual overhaul of Western's Design system and Drupal/Wordpress/Standalone app theme. The most obvious changes with this update are the with the Western Header and Footer, but there are a number of visual updates to block types and components as well. This update is being rolled out to select sites at the beginning of next week. At the time that it goes live on these sites, it will become available on an opt-in basis to other Drupal sites. In December 2025, we will be rolling the theme update out to all Drupal sites. If you would like to opt-in to the theme update now, fill out this form.
The header has been totally overhauled so that it better utilizes space. Various elements of the header have been rearranged, so quick links, university links, search and display settings toggles are in new locations. The logo and site name have changed locations as well.
The default setting for the new main navigation looks and operates the same way it does now, but with style updates. Quick links and university links appear first on the page, followed by Search, display settings, the site name and logo. After this comes the main page navigation, before the page content.
We have also introduced a "hamburger always on" option, in which the navigation is toggled by the "menu" button. With this option on the quick links, university links, AND main navigation are all placed behind a menu toggle.
Our new footer features a beautiful and graphic illustration of Sehome hill and Bellingham Bay, by local artist Gretchen Leggitt.
This update includes changes to the site footer regions that often contain custom content. Most of this content should adapt well to theme changes, with the content appearing in the same order and visual location as before, but images and identity marks that appear in this area may need to be updated to better suit the background color.
In order to simplify and unify the theme visually, the theme colors have been updated, and essentially reverted to an earlier standard. The medium green has been removed and yellow has been added back. Light green is still available, but it's use on the web has been reduced. For Drupal sites, the available background colors on various block types have changed, to reduce visual clutter. Blocks with background colors that have been removed will default to another available color, e.g. light green blocks will become light blue.
As we roll out the new theme, we are also rolling out a new feature: Section Classes. These allow you to set background colors and styles on layout sections in addition to blocks. This will allow for multiple column layouts with colored backgrounds.
The old set up for "box headlines" has been deprecated, it is now a style variant on banners. In the long run this should be easier to use. WebTech will handle any conversions from the old set up, and new style options will be added in the future.
Some performance improvements around how fonts are loaded
Only essential fonts are preloaded now. The material icons font (which is quite larger) is no longer loaded by default. Instead:
Components with static icons (like the WWU Header and footer, and some components like content switchers) now use SVG versions of the material icons. So these are still packaged with those components
Drupal block types that use material icons in an open ended way (like Call to Action links and Announcements) will load the library when they are included in a page
They are loaded as part of the accordion library. So if you are already loading ashlar/accordion (say, in a view) then you also get material icons
They can also be included by themselves by loading the ashlar/material-icons library (for example, in a view using the Views Attach Library module)
If you notice a page where material icons were loading, but aren't any more, please [mailto:masons7@wwu.edu](contact Stephanie) so she can advise on the best way to get the library loaded in your use case.
Many of the updates are under the hood. We have refactored almost all the SASS/CSS and Javascript, take advantage of the latest features those languages. We have also completely redone the documentation and pattern library. We are moving away from Pattern Lab (which hasn't seen many update and is starting to fall out of maintenance) and into Docusaurus (the website you're looking at now.)
There have also been some changes that you will see reflected in the visual styles on Drupal sites. Most of these are minor, like subtle changes to heading and other text styles.
Some will be more noticeable, like changes to some card styles and Call to Action links. In this post, we outline what to expect.
We don't have an exact timeline for deploying this update, but you can expect to see the changes on Development sites in March, and on Production sites in late March or early April.
This is one of the biggest style changes. Call to action links (or CTAs) have been update so that they no longer resemble buttons. The number of CTA style variants have also been reduced.
There is an important reason for this change, but it is somewhat technical. In short, links (eg <a> elements) and buttons (eg <button> elements) are semantically different in HTML. This means that assistive technology announces them differently, and they have different interactive behaviors. For sited, mouse-using folks, these differences aren't readily apparent. This means that when links are styled to look like buttons, they get called buttons. But when they are called buttons, it can (and does) create confusion for assistive technology users–particularly users who are site impaired and cannot see the visual button styles. In order reduce the barriers produced by that visual styling, we have opted to re-do call to action styles so that they visually resemble links, while still standing out on page to call attention to the text.
It can take some time for us to get configuration on Drupal user interfaces synced up with theme changes. You may still notice block types referred to as Button or Image Button when they should actually be Call to Action Link and Image Link. Please don't hesitate to get in touch if you notice this discrepency!
A custom element has been created for social media icons, to simplify the markup, and the styles have changed slightly. Old instances of social media markup will still be supported, but we recommend switching to the new markup and styles at your earliest convenience.
On both mobile and desktop, the styes for fonts and icons have inherited change from elsewhere in the theme. The site name is also now larger on desktops.
One big change is that we are now using CSS variables to set things like link colors and font sizes. This makes inheritence a lot more logical, so that a lot less overrides are needed to make sure that things like contrast and font sizes are maintained when different user preferences are set, or in different situations like when a background color changes.
Another technical change is that we've converted nearly all of our jQuery to vanilla javscript, and many of our components are now available as custom web elements.
The SASS module Breakpoint has been removed. We are now using vanilla CSS media queries. (Note that the variables are still referred to as breakpoints, we're just not using the sass plugin anymore)
Support for IE has been removed (eg no more -ms- prefixes cluttering things up).
These changes, along with dropping out some extra style variants, has lead to a great overall improvement in the file size for our compiled stylesheets. Our ashlar-base.css stylesheet will go from 11,544 lines of code, and 796 kb to 5991 lines of code, and 452 kb on this release.
Some class names and helper class names have changed. This will not affect any native Drupal blocks, but if you have custom styles, you may need to update them.
The "button" class is no longer supported for links. Use "cta" instead.
We moved .html.twig templates out of the _docs/patterns folders and directly into the templates folder. Since these are no longer being used for both the component library and Drupal, it makes more sense to me to keep them in the Drupal-only part of the theme files. This makes the templates a little less reusable, but easier to find.
With the move away from Pattern Lab, we no longer need YAML files. Component documentation lives in Markdown files, alongside the SASS and any Javascript for a component.
We have also continued to convert components to Custom Elements (eg Web Components, but without shadow DOMs). Generally, anything that requires Javascript to function outside of being a web component (like a content switcher or an accordion) will be scripted as a custom element. What this means is that markup for these types of elements has been greatly simplified, so that they are easier to implement across different platforms. For example, a content switcher previously needed the following markup:
<div class="block--content-switcher" id="example"> <div class="content-switcher" role="tablist" aria-label="Title of Content Switcher"> </div> <div class="content-switcher-container"> <button class="switch-1" role="tab" id="switch-button-1" title="switch-button-1" aria-controls="switch-content-1"> Content 1 </button> <div class="switch-1 content" role="tabpanel" id="switch-content-1" aria-labelledby="switch-button-1" tabindex="0"> We have an infinite amount to learn both from nature and from each other. Science has not yet mastered prophecy. We predict too much for the next year and yet far too little for the next 10. </div> <button class="switch-2" role="tab" id="switch-button-2" title="switch-button-2" aria-controls="switch-content-2"> Content 2 </button> <div class="switch-2 content" role="tabpanel" id="switch-content-2" aria-labelledby="switch-button-2" tabindex="0"> If you could see the earth illuminated when you were in a place as dark as night, it would look to you more splendid than the moon. Curious that we spend more time congratulating people who have succeeded than encouraging people who have not. </div> <button class="switch-3" role="tab" id="switch-button-3" title="switch-button-3" aria-controls="switch-content-3"> Content 3 </button> <div class="switch-3 content" role="tabpanel" id="switch-content-3" aria-labelledby="switch-button-3" tabindex="0"> Astronomy compels the soul to look upward, and leads us from this world to another. </div> </div> </div>
Now, the same switcher can be marked up as:
<wwu-accordion> <wwu-accordion-item label="Cats" heading-level="h3"> <p>Purr when being pet claw at curtains stretch and yawn nibble on tuna ignore human bite human hand this is the day hell is other people meowwww. Jump five feet high and sideways when a shadow moves naughty running cat or crash against wall but walk away like nothing happened scratch the box your pillow is now my pet bed. Lick human with sandpaper tongue miaow then turn around and show you my bum rub face on everything. Somehow manage to catch a bird but have no idea what to do next, so play with it until it dies of shock bleghbleghvomit my furball really tie the room together mew hunt anything. Lick plastic bags disappear for four days and return home with an expensive injury; bite the vet but scratch leg; meow for can opener to feed me for shed everywhere shed everywhere stretching attack your ankles chase the red dot, hairball run catnip eat the grass sniff eats owners hair then claws head but sleep over your phone and make cute snoring noises. Trip owner up in kitchen i want food human give me attention meow.</p> </wwu-accordion-item> <wwu-accordion-item label="Dogs" heading-level="h3"> <p>Doggo ipsum blep corgo doggo smol borking doggo with a long snoot for pats, the neighborhood pupper what a nice floof boofers, wow very biscit he made many woofs. Boofers thicc fluffer big ol very taste wow extremely cuuuuuute, blep thicc clouds shooberino, vvv extremely cuuuuuute ruff waggy wags. You are doin me a concern bork what a nice floof fluffer puggorino, very hand that feed shibe pupper smol borking doggo with a long snoot for pats pupper, heckin good boys and girls shooberino sub woofer. Blep yapper big ol pupper very hand that feed shibe big ol, doggorino blep doing me a frighten. Doing me a frighten adorable doggo ruff ur givin me a spook waggy wags, what a nice floof waggy wags noodle horse, shoober doge pupperino.</p> </wwu-accordion-item> <wwu-accordion-item label="Fish" heading-level="h3"> <p>Rough pomfret lemon shark plownose chimaera southern sandfish kokanee northern sea robin Antarctic cod. Yellow-and-black triplefin gulper South American Lungfish mahi-mahi, butterflyfish glass catfish soapfish ling gray mullet! Warbonnet denticle herring spiny-back cod straptail tailor zebra loach sea lamprey.</p> </wwu-accordion-item> </wwu-accordion>
There are some components (such as Announcements and Cards) that don't require Javascript for their basic functionality. We have opted for less Javascript over simplified markup, though this may change in the future.
Why the changes? As time passes, many new styles (and their accompanying code) get introduced to the theme. Some components become cluttered with many style variants. Some of those style options get added that strayed from the look and feel of the theme, and/or don't see much use.
We've removed certain style variations so that there is more consistency across the theme. This reduces the complexity for the people who are managing the components. It also reduces the amount of CSS, which means pages load faster.
That doesn't mean we don't want to keep innovating and adding new styles. In fact, simplifying makes this easier to do. We're starting from a fresh slate, which means there are less style conflicts and bugs to worry about.
If you have any questions, or notice that something on your page that doesn't just look different, but looks brokenplease reach out to Web.Help@wwu.edu or contact Stephanie directly.
