TL;DR – You’re going to need to map your domains to the COOKIE_DOMAIN constant. We run numerous WordPress networks on campus, almost all of which are set up with multiple independent subdomains (e.g. foo.missouri.edu, bar.missouri.edu, etc.). Historically, a WordPress network only supported subdomains based off a root domain (e.g. root domain of mysite.com, child sites of […]
The advent of responsive design and HiDPI (or “Retina”) devices has created a real challenge for web developers: We need a way to provide multiple images to accommodate a variety of window sizes and resolutions.
Here in Web Communications, we’ve been playing with Git as a means to manage versions of our sites. So far, that has been limited to using Git on the local machine, making a remote repository on a shared file space (doit-bfs1), pushing to it occasionally, and then manually transferring the files back over to VH. What we’ve REALLY been wanting to do though is use it to fully manage our sites, allow anyone to work on the site while keeping track of the versions AND publish out to VH, all automatically. We also didnt want to have to store the Git repository in the webroot.
A lot has changed with web typography. We are no longer forced to use a handful of “web safe” fonts or complicated image replacement tricks in order to set beautiful type. This presentation goes over how to learn about type, how properly markup type and how to style it.
In this presentation, we cover Responsive Web Design, going from a basic overview of the concept to common design patterns and pitfalls. This was presented at the April 24, 2012 Web Developers Group Meeting.
In this presentation, we show how Web Communications uses Slideshow Pro Director to manage slideshows. This was presented at the Feb. Web Developers Group. Fun fact: The presentation is run by Slideshow Pro Director.
The University of Missouri makes heavy use of Hannon Hill’s Cascade Server, a XSLT-based content management system. One of the downsides to Cascade is that it doesn’t build live pages on the fly. Changes to files and templates must be published out before they will be live on the server. Even a fairly minor edit, like changing contact information in the footer, may require your entire site to be republished.
Fortunately, there is a solution. We can move our boilerplate content to separate files, and instead configure Cascade to use PHP includes on the live site.
Web design is a field prone to major shifts. For the last few years, the advent of the mobile web has commanded our attention. We must now assume that almost any site we produce will be viewed on a variety of devices—from phones, to tablets, to traditional desktops.
I believe the next major development will be high-definition displays, and this is a shift we should begin preparing for as soon as possible.