<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-4386741367813179428</id><updated>2011-07-30T20:04:45.849-04:00</updated><title type='text'>My Cool Job: Web Developer</title><subtitle type='html'>This is a companion blog to &lt;a href="http://mycooljob.org/"&gt;mycooljob.org&lt;/a&gt;, a site designed to give middle-school and early high school students a chance to consider some career choices. Visit my &lt;a href="http://www.robynness.com"&gt;portfolio&lt;/a&gt;.</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://webmacguffin.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>20</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-6955222276827487959</id><published>2010-05-23T13:49:00.000-04:00</published><updated>2010-05-23T13:50:29.528-04:00</updated><title type='text'>Categories and Tags: Using Blog Metadata for Better Findability</title><content type='html'>We're wrapping up a project to update an entire blog with more usable tags and categories, and I've learned a lot in the process. &lt;br /&gt;&lt;br /&gt;A little history about this project...the blog we were working on started with a focus on cool technology in general, but has transitioned to a stronger learning technology focus. The old categories didn't really work anymore and tags were inconsistently used.&lt;br /&gt;&lt;br /&gt;However, at nearly 200 posts, it was time to make to restore information order. To begin, a colleague and I met with one of Ohio State's librarians to talk about categorization and metadata (data about data), and then worked out a plan that would highlight the focus of the blog without overwhelming casual readers.&lt;br /&gt;&lt;br /&gt;&lt;!--Here's a before and after image of the tag cloud and categories for comparison:--&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Key lessons I learned are:&lt;br /&gt;&lt;br /&gt;1. &lt;span style="font-weight:bold;"&gt;There is no right answer, but there are different approaches for creating categories and tags.&lt;/span&gt; We wanted to use our new categories and tags to shape reader expectations and show at a glance what topics are featured. That meant close attention to our choice of words and how to use categories vs. tags. &lt;br /&gt;&lt;br /&gt;2. &lt;span style="font-weight:bold;"&gt;Don't use categories and tags interchangeably.&lt;/span&gt; Categories are the "big buckets" that different posts can be put in, while tags are additional keywords that describe each post. To keep the category list manageable, we decided to create a few categories for big concepts and to use tags for specific products, projects, programs, etc.&lt;br /&gt;&lt;br /&gt;3. &lt;span style="font-weight:bold;"&gt;Use tags to connect similar posts.&lt;/span&gt; When applying tags, that means focusing on important themes that might be shared in other posts and reviewing past tags to apply them to new posts. &lt;br /&gt;&lt;br /&gt;4. &lt;span style="font-weight:bold;"&gt;Don't be too vague when adding tags.&lt;/span&gt; Focus on what make an article unique, rather than using vague terms that apply to nearly everything. Otherwise, tags and categories all blend together. For example, when we first introduced the new system, one writer tagged an article as "information," but since that *should* apply to all posts we removed it and left only tags about the topic of the post.&lt;br /&gt;&lt;br /&gt;We just finished the recoding, and the difference is striking. There are still some challenges in this project -- mainly that it's hard to bring everyone up to speed about the new guidelines in a shared group blog -- but we'll see how it goes.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-6955222276827487959?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/6955222276827487959'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/6955222276827487959'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2010/05/categories-and-tags-using-blog-metadata.html' title='Categories and Tags: Using Blog Metadata for Better Findability'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-4227355886805333341</id><published>2010-05-01T06:07:00.005-04:00</published><updated>2010-05-01T07:30:51.788-04:00</updated><title type='text'>Social Media and Me: My Trip to KipCamp</title><content type='html'>It's been over a year since I posted to this blog. I have done and learned a whole bunch of new web things in that time, but making time to talk about projects when you're in the middle of them is tough. &lt;br /&gt;&lt;br /&gt;I've spent the past two days at the Kiplinger Program's &lt;a href="http://kiplingerprogram.org/training/"&gt;KipCamp&lt;/a&gt;, an intensive course about social and digital media in communication. I'll be starting the last day of KipCamp in a couple hours and wanted to note a few things I've learned.&lt;br /&gt;&lt;br /&gt;1. &lt;span style="font-weight:bold;"&gt;Old friends miss me.&lt;/span&gt; I've have old accounts on both Twitter and Facebook, but never spent time in them. During KipCamp's Twitter lesson, two long-time acquaintances who DO twitter (apparently often) wrote to welcome me back. Then, approximately one minute after logging into Facebook, my best friend from junior high messaged me. We haven't spoken in 20 years and haven't communicated even electronically more than 4 times since. (Maybe my real lesson is &lt;span style="font-weight:bold;"&gt;social networking is a powerful connector&lt;/span&gt; -- something I had resisted acknowledging when I was shunning it as a waste of time.)&lt;br /&gt;&lt;br /&gt;2. &lt;span style="font-weight:bold;"&gt;The point of social media p.r. is less to tell the whole story than to be interesting.&lt;/span&gt; Or at least interesting enough that your social network forwards your message to their networks, and so on, and so on... Its strengths are forming a baseline of awareness across a large group. This realization struck when a fellow camper and I were trying to revise a factual "tweet" into something more lively -- neither of us disliked the original version, but we also wouldn't think to forward, or "retweet," it.&lt;br /&gt;&lt;br /&gt;3. &lt;span style="font-weight:bold;"&gt;There's no quick solution to creating an online persona.&lt;/span&gt; The people who do it well are adaptive and responsive and probably naturally witty. They pay attention to what works and model what they like in others.&lt;br /&gt;&lt;br /&gt;4. &lt;span style="font-weight:bold;"&gt;Organizations, and even individuals, have online identities whether they create them or not.&lt;/span&gt; Products, services, and brands are talked about on social networks. Most individuals are findable either through simple Google searches or searches of the deep web (information databases that haven't previously been widely searchable). If you want a say in what's out there, you have to be out there saying it.&lt;br /&gt;&lt;br /&gt;5. &lt;span style="font-weight:bold;"&gt;Savvy media people build marketing into everything they do.&lt;/span&gt; My session of KipCamp is being filmed for a television short on the OHIO network and we're encouraged to tweet about the program to practice what we're learning. (And here I am on my own time blogging about it!) These things record the experience so other people will choose to attend the program. The media experts who run the program know that it's not enough to do great work if no one else knows it.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-4227355886805333341?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/4227355886805333341'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/4227355886805333341'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2010/05/social-media-and-me-my-trip-to-kipcamp.html' title='Social Media and Me: My Trip to KipCamp'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-2528171762188995957</id><published>2009-02-05T07:06:00.009-05:00</published><updated>2009-02-05T07:28:27.322-05:00</updated><title type='text'>Designing a Fun Site, Pt. 2</title><content type='html'>The "Teach Online" project is now &lt;span style="font-style:italic;"&gt;mostly&lt;/span&gt; done. You can visit it at &lt;a href="http://telr.osu.edu/teachonline"&gt;http://telr.osu.edu/teachonline&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;As you may recall, the design goal for this site is to be inviting and easy to skim, while providing a lot of information. We've created short video clips from interviews with instructors who teach online in additional to the initial JavaScript slideshows.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_LM34ajk5MRM/SYrYHItNt9I/AAAAAAAAAEs/sa0v8AKqZ6c/s1600-h/teachonline.png"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 247px;" src="http://2.bp.blogspot.com/_LM34ajk5MRM/SYrYHItNt9I/AAAAAAAAAEs/sa0v8AKqZ6c/s400/teachonline.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5299285528662620114" /&gt;&lt;/a&gt;The videos required quite a lot of editing, but have an impact far greater than the equivalent text. Using video also:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;models our recommended practice of accommodating different learning styles, as some people prefer audio or video to written text.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;literally shows our target audience that others like them are doing the types of things they want to be doing.&lt;/li&gt;&lt;br /&gt;&lt;/ul&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-2528171762188995957?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/2528171762188995957'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/2528171762188995957'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2009/02/designing-fun-site-pt-2.html' title='Designing a Fun Site, Pt. 2'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_LM34ajk5MRM/SYrYHItNt9I/AAAAAAAAAEs/sa0v8AKqZ6c/s72-c/teachonline.png' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-6508463803825386349</id><published>2008-10-28T06:50:00.006-04:00</published><updated>2008-10-28T07:44:27.526-04:00</updated><title type='text'>Trends in Web Design</title><content type='html'>The web is like any designed media -- fads come and go. Here are some I've noticed in the past few years:&lt;br /&gt;&lt;br /&gt;About two years ago, online publications like Wired and CNN.com led the way away from strong background graphics, switching to largely gray layouts where the content and accompanying images draw the most attention. (In relation to technology, this shift makes good sense; as download speeds have gotten better, large graphics specific to the stories are feasible. Using repeating background images for an entire site was an efficient way to add color and visual appeal in the early days of the web.)&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_LM34ajk5MRM/SQb5LPkuB6I/AAAAAAAAAD4/cqwUSvUO1cs/s1600-h/wired.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 279px;" src="http://3.bp.blogspot.com/_LM34ajk5MRM/SQb5LPkuB6I/AAAAAAAAAD4/cqwUSvUO1cs/s400/wired.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5262167186183423906" /&gt;&lt;/a&gt;Over the past year, more sites are incorporating JavaScript-based interactivity, such as scrolling panels and hovering windows, that don't take the visitor away from their starting point. These elements shift considerations in information design and layout away from discrete pages and toward user-friendly controls&lt;br /&gt;&lt;br /&gt;This summer as  I was working on a freelance book project that required updating screen captures of websites, I noticed another more subtle shift. Although only a year had passed, the featured sites had changed to make room for much more ad placement–-nearly every site had been reworked to show Google ads in multiple places on the page even if the rest of the design was the same. &lt;br /&gt;&lt;br /&gt;Maybe the big lesson is that web site design, like fashion, is not timeless. Even sites that were the height of cool in their day might end of the web equivalent of a 1970s polyester leisure suit. It will be interesting to see what comes next.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-6508463803825386349?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/6508463803825386349'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/6508463803825386349'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2008/10/trends-in-web-design.html' title='Trends in Web Design'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_LM34ajk5MRM/SQb5LPkuB6I/AAAAAAAAAD4/cqwUSvUO1cs/s72-c/wired.jpg' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-6910037133903577034</id><published>2008-10-16T07:59:00.005-04:00</published><updated>2008-10-16T08:39:48.056-04:00</updated><title type='text'>Designing a Fun Site</title><content type='html'>The goal of my current web project is to present a lot of information in a non-threatening way. &lt;br /&gt;&lt;br /&gt;To avoid overwhelming people, I'm trying out some interactive page elements – slideshows that scroll sideways and, hopefully, sections that open and close vertically when clicked.&lt;br /&gt;&lt;br /&gt;Here's a picture, but you can visit the draft version at &lt;a href="http://telr.osu.edu/teachonline/tour.htm"&gt;http://telr.osu.edu/teachonline/tour.htm&lt;/a&gt; to try it.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_LM34ajk5MRM/SPc1T_DgqrI/AAAAAAAAADs/Q91yqpsSQ14/s1600-h/teachonline_large.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;" src="http://1.bp.blogspot.com/_LM34ajk5MRM/SPc1T_DgqrI/AAAAAAAAADs/Q91yqpsSQ14/s400/teachonline_large.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5257729707438287538" /&gt;&lt;/a&gt;The slideshow uses a language called JavaScript, which allows clicks on the screen to cause changes in what appears there. (To be more specific, I'm using some special JavaScript libraries called jQuery that includes prebuilt bits of code (also known as functions) to control different parts of the page in different situations.) &lt;br /&gt;&lt;br /&gt;My goal with this design is to encourage people to click to the information that interests them and perhaps read other parts that are within easy reach. The less work it is to move through the content, the more likely our audience will be to learn what we're teaching.&lt;br /&gt;&lt;br /&gt;I'll keep you posted as this site progresses.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-6910037133903577034?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/6910037133903577034'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/6910037133903577034'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2008/10/designing-fun-site.html' title='Designing a Fun Site'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_LM34ajk5MRM/SPc1T_DgqrI/AAAAAAAAADs/Q91yqpsSQ14/s72-c/teachonline_large.jpg' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-260758843387611176</id><published>2008-07-02T07:26:00.003-04:00</published><updated>2008-12-08T22:10:18.111-05:00</updated><title type='text'>Learning New Things</title><content type='html'>Two challenges for web developers (and all technology professionals) are teaching themselves new skills and keeping up to date with current trends. &lt;br /&gt;&lt;br /&gt;It's for those reasons that I started my personal website, &lt;a href="http://www.floraphotographs.com"&gt;Flora Photographs&lt;/a&gt;, about 5 years ago.&lt;br /&gt;&lt;br /&gt;At the start, I used Flora Photographs to learn database basics and improve my programming skills. A couple years later, I updated it to a new style of layout using only CSS. Just this week, I redesigned to bring in more CSS and some interesting/interactive features that use CSS and JavaScript.&lt;br /&gt;&lt;br /&gt;Here's a picture of the latest version -- but you really have to visit and try a search to get the full effect:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_LM34ajk5MRM/SGtpAiDnF0I/AAAAAAAAACc/3M3kZCaO25k/s1600-h/flora.gif"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;" src="http://3.bp.blogspot.com/_LM34ajk5MRM/SGtpAiDnF0I/AAAAAAAAACc/3M3kZCaO25k/s320/flora.gif" border="0" alt=""id="BLOGGER_PHOTO_ID_5218380051101718338" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-260758843387611176?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/260758843387611176'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/260758843387611176'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2008/07/learning-new-things.html' title='Learning New Things'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_LM34ajk5MRM/SGtpAiDnF0I/AAAAAAAAACc/3M3kZCaO25k/s72-c/flora.gif' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-4688625284804171954</id><published>2008-06-08T21:34:00.004-04:00</published><updated>2008-06-08T21:42:49.903-04:00</updated><title type='text'>Displaying International Fonts and Characters on the Web</title><content type='html'>&lt;span style="font-style:italic;"&gt;How do you display web content in languages other than English?&lt;/span&gt; &lt;br /&gt;&lt;br /&gt;The quick answer is to use unicode. &lt;a href="http://www-306.ibm.com/software/globalization/topics/unicode/index.jsp"&gt;Unicode&lt;/a&gt; is a standard that includes character representations encompassing all living languages. &lt;br /&gt;&lt;br /&gt;When using unicode, appropriate fonts have to be available on each viewer's computer. Otherwise, the unicode characters won't be rendered. You can &lt;a href="http://unicode.coeurlumiere.com/"&gt;test which unicode characters are available on your system&lt;/a&gt; – unknown characters show up as rectangles or squares rather than characters.) &lt;br /&gt;&lt;br /&gt;There are also additional factors to consider. &lt;a href="http://www.robynness.com/international/"&gt;Details...&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-4688625284804171954?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/4688625284804171954'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/4688625284804171954'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2008/06/displaying-international-fonts-and.html' title='Displaying International Fonts and Characters on the Web'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-3930081912535616980</id><published>2008-05-24T09:06:00.006-04:00</published><updated>2008-12-08T22:10:18.330-05:00</updated><title type='text'>Wikis</title><content type='html'>One of my big projects at work right now is refining the user interface for a wiki service at Ohio State. &lt;br /&gt;&lt;br /&gt;A wiki is a kind of website that allows users to add and edit content collectively (read more about &lt;a href="http://en.wikipedia.org/wiki/Wiki"&gt;wikis&lt;/a&gt;), so it's important to make it easy for visitors to understand what they are allowed to do. It's also important to our users who set up their own wiki spaces in our service to change the interface to show their own personalities.&lt;br /&gt;&lt;br /&gt;I started my interface improvements by activating several theme add-ins written by other people for the wiki software. These themes offer variety so all the wiki spaces don't have to look exactly the same. Here's an example of one that let's space owners change the background color:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_LM34ajk5MRM/SDgXbZkYZ4I/AAAAAAAAACU/2oPVsX8VkDU/s1600-h/Picture+2.png"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;" src="http://4.bp.blogspot.com/_LM34ajk5MRM/SDgXbZkYZ4I/AAAAAAAAACU/2oPVsX8VkDU/s320/Picture+2.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5203935128913995650" /&gt;&lt;/a&gt;I've also been working with a templating language called Velocity to restructure the wiki's introduction page, or Dashboard. Because we offer wiki space to a lot of unrelated projects, the list of recent changes for all wikis that normally appears isn't very helpful!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-3930081912535616980?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/3930081912535616980'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/3930081912535616980'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2008/05/wikis.html' title='Wikis'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_LM34ajk5MRM/SDgXbZkYZ4I/AAAAAAAAACU/2oPVsX8VkDU/s72-c/Picture+2.png' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-4751410385408398962</id><published>2008-04-25T12:59:00.009-04:00</published><updated>2008-12-08T22:10:18.543-05:00</updated><title type='text'>Sending HTML Email</title><content type='html'>Earlier this week, I wrapped up an HTML-formatted newsletter project. It was challenging because every email reader renders HTML slightly differently. &lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_LM34ajk5MRM/SBI5_-copJI/AAAAAAAAAAo/8zOTifO2wWE/s1600-h/htmlemail.gif"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;" src="http://4.bp.blogspot.com/_LM34ajk5MRM/SBI5_-copJI/AAAAAAAAAAo/8zOTifO2wWE/s320/htmlemail.gif" border="0" alt=""id="BLOGGER_PHOTO_ID_5193277091569247378" /&gt;&lt;/a&gt;&lt;br /&gt;Also, the type of HTML that works in email differs from what's typically written for the web. Here are some of the big differences:&lt;br /&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;Images displayed in HTML email are stored on a webserver and read remotely by the message recipient. That means files paths to the images have to absolute paths, like a link to an external website.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;CSS (Cascading Style Sheets) works differently, too. Usually, CSS files are external to a page, but inline styles are needed for HTML email.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;Also, only a limited set of CSS selectors work reliably in HTML email. Margins, padding, and other positioning settings fail. Unfortunately, this means arranging elements of the page has to be done the old-fashioned way -- with HTML tables.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;The biggest lesson I learned is that even a simply formatted HTML-email template like this one requires a lot of testing.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-4751410385408398962?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/4751410385408398962'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/4751410385408398962'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2008/04/sending-html-email.html' title='Sending HTML Email'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_LM34ajk5MRM/SBI5_-copJI/AAAAAAAAAAo/8zOTifO2wWE/s72-c/htmlemail.gif' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-5529550566560005222</id><published>2008-03-21T10:51:00.013-04:00</published><updated>2008-12-08T22:10:18.701-05:00</updated><title type='text'>How I Spent My Vacation</title><content type='html'>Last week, I met up with a college friend to attend South by Southwest Interactive in Austin, Texas. In addition to enjoying good food, great conversation, and a trip to the LBJ Presidential Library to see animatronic LBJ, I attended sessions on teamwork in web design, designing user-focused sites, and whether video games have a place in higher education.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_LM34ajk5MRM/SBR2iOcopOI/AAAAAAAAABY/0-aC7AnnO7g/s1600-h/web.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;" src="http://3.bp.blogspot.com/_LM34ajk5MRM/SBR2iOcopOI/AAAAAAAAABY/0-aC7AnnO7g/s320/web.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5193906600630854882" /&gt;&lt;/a&gt;&lt;br /&gt;Three observations:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Great web development comes from teamwork--even "famous" web designers are surrounded by colleagues they respect and rely on.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;All web developers, no matter their location or who they work for, struggle to get content from their clients.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;All website owners struggle to understand who is visiting their site and why.&lt;/li&gt;&lt;/ul&gt;&lt;br /&gt;Although these may not seem like earth-shattering revelations, it was comforting to realize that corporate web professionals experience the same general conditions as those of us in universities and non-profits.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-5529550566560005222?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/5529550566560005222'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/5529550566560005222'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2008/03/how-i-spent-my-vacation.html' title='How I Spent My Vacation'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_LM34ajk5MRM/SBR2iOcopOI/AAAAAAAAABY/0-aC7AnnO7g/s72-c/web.jpg' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-6164823415474128238</id><published>2007-11-01T23:12:00.008-04:00</published><updated>2008-12-08T22:10:18.841-05:00</updated><title type='text'>Eliciting Participation in Collaborative Content Design</title><content type='html'>In October, I presented a poster at the HighEd WebDev conference in Rochester, NY to share how my colleagues and I collaborated to develop content in three recent web/information projects.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_LM34ajk5MRM/SBR3Q-copPI/AAAAAAAAABg/fdCWSU4KlTk/s1600-h/web-1.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;" src="http://2.bp.blogspot.com/_LM34ajk5MRM/SBR3Q-copPI/AAAAAAAAABg/fdCWSU4KlTk/s320/web-1.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5193907403789739250" /&gt;&lt;/a&gt;&lt;br /&gt;Here's a summary:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;For one of the projects, we used a wiki to co-write the content and edit each other's drafts. This method allowed everyone a chance to see how the site was forming and add any information they had.&lt;/li&gt;&lt;br /&gt;&lt;li&gt;For another project, pairs of people arranged keywords to help define the focus of a site.&lt;/li&gt; &lt;br /&gt;&lt;li&gt;For the third project, we gathered as many people as possible to test a new software system and make notes about updates needed to the old online help pages. This would have taken the usual documentation team a month to complete, but having everyone help sped up the process and gave us a wider perspective about what was and wasn't working.&lt;/li&gt;&lt;br /&gt;&lt;/ul&gt;&lt;p&gt;&lt;a href="http://www.robynness.com/ness_poster.pdf"&gt;See more details. (pdf)&lt;/a&gt;&lt;/p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-6164823415474128238?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/6164823415474128238'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/6164823415474128238'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2008/04/eliciting-participation-in.html' title='Eliciting Participation in Collaborative Content Design'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_LM34ajk5MRM/SBR3Q-copPI/AAAAAAAAABg/fdCWSU4KlTk/s72-c/web-1.jpg' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-2764229668945899980</id><published>2007-04-10T10:27:00.004-04:00</published><updated>2008-12-08T22:10:18.987-05:00</updated><title type='text'>Launching the Site</title><content type='html'>Well, after months of planning and development, we finally launched the new site. It features a home page with space for news and announcements, an RSS feed of news and events, clearly labeled services and site navigation, and a bright, shiny new look!&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_LM34ajk5MRM/SBJBQ-copKI/AAAAAAAAAAw/aK0TEs3CTr4/s1600-h/telr.gif"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;" src="http://4.bp.blogspot.com/_LM34ajk5MRM/SBJBQ-copKI/AAAAAAAAAAw/aK0TEs3CTr4/s320/telr.gif" border="0" alt=""id="BLOGGER_PHOTO_ID_5193285080208417954" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-2764229668945899980?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/2764229668945899980'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/2764229668945899980'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2007/04/launching-site.html' title='Launching the Site'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_LM34ajk5MRM/SBJBQ-copKI/AAAAAAAAAAw/aK0TEs3CTr4/s72-c/telr.gif' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-8764727212399794106</id><published>2007-03-21T17:06:00.002-04:00</published><updated>2008-04-26T11:18:27.096-04:00</updated><title type='text'>Coding and Testing the Site</title><content type='html'>After a few tweaks to the design, I've begun building the site in HTML and CSS. Because different web browsers sometimes show pages differently, I'm testing each change I make to ensure I don't break what I've already done.&lt;br /&gt;&lt;br /&gt;The hardest thing right now is aligning some navigation links that run along the top of the page -- it's a tight fit and I want to be sure they don't shift around and create gaps when the page is resized.&lt;br /&gt;&lt;br /&gt;If you are interested in how CSS is used to make websites, here's a link to visit:&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.w3schools.com/css/css_examples.asp"&gt;W3 Schools - CSS Examples&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Sorry this is so short...I have a lot of work to do!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-8764727212399794106?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/8764727212399794106'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/8764727212399794106'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2007/03/coding-and-testing-site.html' title='Coding and Testing the Site'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-7497235261661619279</id><published>2007-03-13T08:56:00.002-04:00</published><updated>2008-04-27T09:11:11.266-04:00</updated><title type='text'>Writing for the Web</title><content type='html'>When people think "web design," they often focus on the visual design. But the design of the content is equally important. A pretty site without substance is just an empty frame!&lt;br /&gt;&lt;br /&gt;One of my big challenges is to understand what my customers want their sites to say. In this case, the customer is the group I work with. I've been meeting regularly with several of them to get opinions about what our group has to offer the people who come to us for help. &lt;br /&gt;&lt;br /&gt;After settling on topics to include, part of my job is to locate the information, writing and edit it, and share it back with my coworkers for revisions and corrections.&lt;br /&gt;&lt;br /&gt;A few words about writing for the web... Because the web makes it so easy for our attention to wander--there's always a new site to explore--most web writing has to be quick and to the point. I write in a style to help my online readers recognize quickly whether they will find the information they need, so they can decide whether to try another page.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-7497235261661619279?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/7497235261661619279'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/7497235261661619279'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2007/03/writing-for-web.html' title='Writing for the Web'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-1879487985237688263</id><published>2007-03-05T23:55:00.001-05:00</published><updated>2008-12-08T22:10:19.123-05:00</updated><title type='text'>Working with Visual Design</title><content type='html'>For this site, I've been working with a visual designer on the appearance of the pages. She came up with several options that use the site structure I designed, and presented them to the director of our group.&lt;br /&gt;&lt;br /&gt;Here's the design that was selected:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_LM34ajk5MRM/SBJHJ-copLI/AAAAAAAAAA4/CJd2x5czESA/s1600-h/telr-old.gif"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;" src="http://4.bp.blogspot.com/_LM34ajk5MRM/SBJHJ-copLI/AAAAAAAAAA4/CJd2x5czESA/s320/telr-old.gif" border="0" alt=""id="BLOGGER_PHOTO_ID_5193291557019100338" /&gt;&lt;/a&gt;&lt;br /&gt;The next step is to test the design with users to see if they respond positively to it.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-1879487985237688263?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/1879487985237688263'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/1879487985237688263'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2007/03/working-with-visual-design.html' title='Working with Visual Design'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_LM34ajk5MRM/SBJHJ-copLI/AAAAAAAAAA4/CJd2x5czESA/s72-c/telr-old.gif' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-3856796414674794726</id><published>2007-03-01T13:58:00.000-05:00</published><updated>2008-04-27T15:12:07.185-04:00</updated><title type='text'>Testing for Usability</title><content type='html'>After drawing a basic plan for the site pages, I tested it with a few people to see if they understood the navigation. &lt;br /&gt;&lt;br /&gt;These volunteers clicked through a simplified version of the site to perform some common tasks we'd expect our regular visitors to do.&lt;br /&gt;&lt;br /&gt;One interesting finding was related to a version of the site that had a special section called "Research" to highlight the research and exploration performed by the group I work for. When viewing the site, some of testers interpreted it to mean THEIR research and how our group could help. Because of this, I chose to remove the section and fold that content into sections called "Online Resources" and "News and Events."&lt;br /&gt;&lt;br /&gt;Our test users also preferred a simpler page header with fewer supplemental links to other Ohio State services. For this reason, we moved them to the bottom of the page.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-3856796414674794726?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/3856796414674794726'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/3856796414674794726'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2008/03/testing-for-usability.html' title='Testing for Usability'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-4782022114161440600</id><published>2007-02-21T10:07:00.004-05:00</published><updated>2008-12-08T22:10:19.221-05:00</updated><title type='text'>Creating a Wireframe</title><content type='html'>After sketching a site structure, my next step was to create a wireframe to fit everything needed into each page. A wireframe is sketch that shows the basic form of a product. In engineering and product design, it might be a computer-generated 3-d model. In web design, it is a sketch of the pages that shows the major elements, such as navigation links, content, and any logos or brand elements. &lt;br /&gt;&lt;br /&gt;Here's a snapshot of the first wireframe, which I drew with a basic drawing program:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_LM34ajk5MRM/Rdxgb-MpcmI/AAAAAAAAAAY/EjsvHowb0A4/s1600-h/wireframe.gif"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;" src="http://3.bp.blogspot.com/_LM34ajk5MRM/Rdxgb-MpcmI/AAAAAAAAAAY/EjsvHowb0A4/s320/wireframe.gif" border="0" alt=""id="BLOGGER_PHOTO_ID_5034004517162152546" /&gt;&lt;/a&gt;&lt;br /&gt;By sketching out a typical page, I formed a sense for the visual hierarchy. "Visual hierarchy" basically means focusing attention so that important things are the most noticeable and less important ones aren't as obvious. &lt;br /&gt;&lt;br /&gt;In developing the wireframe, I carefully considered how the parts of the page would be positioned. I tried to create clearly defined areas for navigation and content that would be easy to skim. (Studies of web use show that most people quickly scan pages to see what interests them, rather than reading every word.) I planned the site navigation to leave room for subsections along the left side of the screen. (Using left side for subsections gives a lot of flexibility for future growth of the site because it's easier to add items to a vertical list than it is to add to a horizontal list--scrolling horizontally is a very bad thing in web design.) I also placed a search box at the top of every page just in case people felt lost. &lt;br /&gt;&lt;br /&gt;The sidebar on the right side also serves a purpose. First, it narrows the main content area so pages with a lot of text won't seem as text-heavy and hard to read.  Second, it gives buffer for people who's screens are smaller than average so they won't have to scroll horizontally to read the main content. (Horizontal scrolling = Very Bad!) Finally, it gives another area of the page for special types of information--if something needs to be said but doesn't fit the flow of the main content, there's room in the sidebar.                                                                          &lt;br /&gt;&lt;br /&gt;Based on the wireframe, the decision makers in my group had an idea of my plan for the web site and approved it, and I could build a web version of the wireframe in HTML. Web wireframe comes in handy for exploring page interaction and performing basic usability testing, which I'll talk about in my next posting.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-4782022114161440600?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/4782022114161440600'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/4782022114161440600'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2007/02/creating-wireframe.html' title='Creating a Wireframe'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_LM34ajk5MRM/Rdxgb-MpcmI/AAAAAAAAAAY/EjsvHowb0A4/s72-c/wireframe.gif' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-2083842119740661001</id><published>2007-02-15T11:46:00.002-05:00</published><updated>2008-12-08T22:10:19.447-05:00</updated><title type='text'>Designing a New Site Structure</title><content type='html'>After doing research on what people hoped to see in the new site, my focus turned to site structure.&lt;br /&gt;&lt;br /&gt;My goal was to produce a drawing of the new site's pages--the sections and subsections and how they would be arranged. (Structural drawings can show how deeply buried important information is, as well as show if some sections are too cumbersome and need to be split into subsections. They also act as visual aids to make it easier to describe site ideas to other people.)&lt;br /&gt;&lt;br /&gt;From surveys I had learned that people wanted easier navigation in the new site. Their comments showed that they weren't finding things where they expected them in the existing site. (This wasn't surprising -- a structural drawing of the existing site suggested it would be hard to find some important pages, and some of pages in the main navigation weren't important.)&lt;br /&gt;&lt;br /&gt;One specific problem seemed to be too many categories that weren't different enough from one another. For example, the existing site navigation includes links to Services as well as to Grants (which we offer) and eLearning (which is what we support). Site visitors sometimes had to click through all three to see how we could help them.&lt;br /&gt;&lt;br /&gt;Another trouble spot was the Resources section, which provides online information related to eLearning and technology. Over time, it had grown to be several linked pages without a central organizing theme. Site visitors who visited Resources had to work had to locate the information they wanted or, more likely, they gave up.&lt;br /&gt;&lt;br /&gt;After examining the content we had and comparing it to the suggestions from the surveys, I created a structural drawing that organized the pages of the site. Here's a snapshot:&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_LM34ajk5MRM/RdSQ2eMpclI/AAAAAAAAAAM/O8ZRA6E5YSM/s1600-h/sitemap_5-2006.gif"&gt;&lt;img style="margin: 0px auto 10px; display: block; text-align: center; cursor: pointer;" src="http://1.bp.blogspot.com/_LM34ajk5MRM/RdSQ2eMpclI/AAAAAAAAAAM/O8ZRA6E5YSM/s320/sitemap_5-2006.gif" alt="" id="BLOGGER_PHOTO_ID_5031805949173133906" border="0" /&gt;&lt;/a&gt;&lt;br /&gt;This structural diagram was just a starting point. My ideas for site structure changed over time as I tested it with people inside my group and people who come to my group for services. (I'll discuss how it changed as a result of user testing later on.)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-2083842119740661001?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/2083842119740661001'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/2083842119740661001'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2007/02/designing-new-site-structure.html' title='Designing a New Site Structure'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_LM34ajk5MRM/RdSQ2eMpclI/AAAAAAAAAAM/O8ZRA6E5YSM/s72-c/sitemap_5-2006.gif' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-6295218094258452856</id><published>2007-02-07T09:34:00.001-05:00</published><updated>2008-04-25T16:49:04.105-04:00</updated><title type='text'>Assessing the Old Site</title><content type='html'>Most of the web projects I've worked on have been redesigns of previous sites. My first step is always to carefully examine the existing site to see what is or isn't working for the web site's owner.&lt;br /&gt;&lt;br /&gt;When I examined the existing site for my current project, I could see that the web site didn't match my group's goals. The content was a bit outdated and the section navigation didn't reflect what we do here. It was hard to find information on our current projects, which was frustrating to people outside our group who used the site as a reference.&lt;br /&gt;&lt;br /&gt;After I examined the old site myself, I surveyed other people about what they thought should be in the new website and what they valued in the existing site.  I included both people inside my group and people who come to my group for services.  The list of suggestions was long, and some of the items were not practical -- but there were also suggestions that a lot of people gave, such as:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;a clear list of our services&lt;/li&gt;&lt;li&gt;a showcase to highlight projects and new technologies at OSU&lt;/li&gt;&lt;li&gt;easier navigation&lt;br /&gt;&lt;/li&gt;&lt;li&gt;more online resources&lt;/li&gt;&lt;li&gt;an RSS feed of our news and events&lt;/li&gt;&lt;/ul&gt;In developing the new site, I based my decisions about content and features on this information.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-6295218094258452856?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/6295218094258452856'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/6295218094258452856'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2007/02/assessing-old-site.html' title='Assessing the Old Site'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry><entry><id>tag:blogger.com,1999:blog-4386741367813179428.post-726693165955631947</id><published>2007-02-07T09:23:00.001-05:00</published><updated>2008-04-25T16:49:25.372-04:00</updated><title type='text'>What I've Been Working On</title><content type='html'>Sorry for the slow start on this blog. I've been hard at work on a web site redesign for the group I work with at Ohio State.&lt;br /&gt;&lt;br /&gt;This project has been underway for several months now, and we're planning to launch the finished site in mid-March. In my next several posts, I'll share information about the steps my group has worked through in the site development, including&lt;br /&gt;&lt;ul&gt;&lt;li&gt;assessing the old site&lt;/li&gt;&lt;li&gt;designing a new site structure&lt;/li&gt;&lt;li&gt;creating a "wireframe" of the page layout&lt;/li&gt;&lt;li&gt;testing for usability&lt;br /&gt;&lt;/li&gt;&lt;li&gt;collecting and editing content&lt;/li&gt;&lt;li&gt;working with visual designers&lt;/li&gt;&lt;li&gt;coding the final site&lt;/li&gt;&lt;li&gt;testing on browsers&lt;br /&gt;&lt;/li&gt;&lt;/ul&gt;In the last post, I hope to unveil the final site. But I have a lot of work to do for that to happen--so time to get back to work!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/4386741367813179428-726693165955631947?l=webmacguffin.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/726693165955631947'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4386741367813179428/posts/default/726693165955631947'/><link rel='alternate' type='text/html' href='http://webmacguffin.blogspot.com/2007/02/what-ive-been-working-on.html' title='What I&apos;ve Been Working On'/><author><name>Robyn Ness</name><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author></entry></feed>
