Web Technology @ CCBC

Student driven blog for all things web.

University of Wisconsin Platteville’s Web Development Office

Posted by mashkenes on February 11, 2008

I went to the University of Wisconsin – Platteville’s Web Development Office site to get a copy of the PowerPoint material used in the Daniel Frommelt video. While there, I came across a variety of tutorials, presentation materials, links and other useful web standards and web development information. Some of what’s there is very familar as it is information already discussed or referenced on the class blog. Some items, though, were new to me and I think others may also find them useful.

One of the particulalry interesting pieces was the UWP Web Templates page. In an effort to promote a somewhat standard look and feel across UWP department web pages, the Web Development Office provides an assortment of templates that developers can choose from. In some ways this is analagous to CSS ZenGarden in that the same content can be presented though a variety of skins. Unlike CSS ZenGarden, some of the XHTML in the UWP template code is meant to be altered. If I have a proper sense of what the template code does, its javascript calls in the appropriate stylesheets.

Mike A.


One Response to “University of Wisconsin Platteville’s Web Development Office”

  1. danielmfrommelt said

    Greetings from snowy Platteville, Wisconsin and thanks for the link to UW-Platteville’s Web Team.

    The templates that are used at the university are a combination of things that centralize control of the look and feel, while still giving departments access to their content on their website. I do not like relying solely on javascript to develop the templates, however if you look around HUGE companies (i.e. Google, FaceBook, Microsoft, You Tube) all require javascript in order to have a good user experience. A big benefit of JS files is they are cached, so you download them once on the browser and they are good to go.

    What we use our javascript files at UW-Platteville to do is this:
    – centralize the structure of the website
    – display the appropriate CSS files based on template chosen
    – ensure compliance with the university “image” (eliminates rogue sites)
    – force accessibility tools into the pages
    – control the display specific information (i.e. printer friendly, screen reader access)
    – allow for updates to websites without touching individual department’s content
    – allow for new features to be added (i.e. search engine code, campus wide emergency system, etc.)

    The CSS files are actually a combination of things as well… when in doubt break things into categories (site wide file, group structural files, general design files, specific design files, printer files, icon files, etc.) I try to treat CSS as I treat Lego blocks… build generic parts and use them all over.

    Feel free to ask more specific questions if you have them, but that’s the general view from 50,000 ft.

    – Daniel M. Frommelt

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: