Web Communication will be on campus to help with any WordPress, online registration, or Qualtrics questions that you might have. All are welcome, so please spread the word. As always, please come when you can, and you stay as long as you like.
All sessions will be in SHSB 260
Wednesday March 15th –
10:00 AM – 11:30 AM
1:00 PM – 2:30 PM
3:00 PM – 4:40 PM
Thursday March 16th –
9:00 AM – 11:00 AM
1:00 PM – 3:00 PM
Hello! WSU Web Communication is working on the next generation of a web framework for use as a base throughout the University. This framework will be made up of several different pieces, including the WSU identity, WSU web identity, and a general toolkit for working on the web at WSU.
In many ways this will be similar to what is now the WSU Spine, which has been the central framework for University sites since June of 2014. The Spine provides the vertical navigation, WSU identity, and mobile friendly framework that is behind much of the web at WSU.
We have a lot of great ideas for where we want to take the new WSU Web Framework, and we’ll be sharing and developing those in the open. First, we want to take a look back and apply the lessons we’ve learned from the WSU Spine project over the last several years.
It would be extremely helpful to have your feedback. If you’re a WSU web reader, editor, developer, or have any interest at all in the future of the web at WSU, please consider completing the WSU Spine Feedback form.
The plugin managing analytics on the WSUWP platform has been updated to use Google Tag Manager (GTM) as its method for tracking site, application and global analytics. This change affects sites hosted on the central WordPress platform and is not yet a suggested change for other WSU sites.
Managing these Google Analytics tracking IDs through GTM allows us to make changes to how events are tracked in a central area without requiring code level changes across all WSU sites. Our hope is that experimenting with GTM on WSUWP Platform sites now will allow us to have a more robust tracking system deployed in 2017.
No actual changes have been made to how the data is being collected. When these changes are made, we’ll communicate them here so that you’re familiar with the reporting possibilities for your site.
The Google Tag Manager interface only affects how the data is collected. To see a site’s analytics, you will still use the standard Google Analytics interface.
If you notice any issues with analytics tracking on your site, please reach out via Slack, Open Lab, or email to Bob Frank and we can work with you to make any required changes.
A dramatic increase in spambot / ghost referral traffic was noticed over the past two months in Google Analytics reports. To block the spambot / ghost data from corrupting your sites’ analytics, a substantially expanded spambot / ghost filter was developed and tested.
The previous filter was designed to stop about 25 of the biggest spambot / ghost offenders. The new filter is designed to stop about 225 of the leading culprits.
Web Communication will continue to monitor GA data/reports for new spambot/ghost offenders, and eventually will create a second filter. (We hit Google’s character limitation with this expansion.)
Website/Google Analytics account managers are strongly encouraged to deploy the updated filter as soon as possible. (Please note: Departments that are partnering with Web Communications to help maintain Google Analytics accounts/properties have already had their spambot/ghost filters updated.)
If you are maintaining your own GA accounts/properties, here are the steps involved. (Estimated time: 1-2 minutes)
Log into your Google Analytics account.
Select a Google Analytics account.
Click on “All Filters.”
Select the ‘referral spam bots ghosts’ filter.
Highlight and DELETE the old “Filter Pattern.”
Copy and paste in the following filter pattern in the same field:
The 109th release of the WSUWP Spine Parent Theme, version 0.27.1, was deployed earlier today. It finally adds helper links for screen readers that make skipping straight to the main content or the primary navigation much more pleasant.
Hit “Tab” on your keyboard once when a page first loads to see a Skip to main content link. Hit “Tab” a second time to see Skip to navigation. Hitting “Enter” on either of these will focus your keyboard on that area of the page, making it easier to navigate through other portions from there. Note that if you’re logged in, you’ll get a Skip to toolbarlink first to help with WordPress navigation.
This release contains a handful of things that may be interesting to anyone spending time editing CSS on their site.
Edit CSS now supports easy saving via AJAX. Rather than click “Save Stylesheet” every time you have a change to save, you can use CMD-s or CTRL-s on your keyboard. A message will briefly show at the top of the screen showing the progress of the save and then you’ll be able to continue working.
Support for full screen editing is also available. Hit ESC on the keyboard whenever the cursor is focused on the Edit CSS window and the code editor will fill the browser window. AJAX saving with CMD-s and CTRL-s works in this view as well.
Thanks to Nate Owen for both of those changes!
Also of note:
The CSS preprocessor settings have been removed. These never actually worked in our implementation, so now the clutter is gone. 🙂
The font-feature-settings property is now supported.
Multiple display properties are supported in a single CSS rule.