<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
   <channel>
      <title>Web</title>
      <link>http://blog.buffalostate.edu/collegerelations/web/</link>
      <description>Orange you glad we&apos;re doing a refresh?</description>
      <language>en</language>
      <copyright>Copyright 2008</copyright>
      <lastBuildDate>Mon, 25 Aug 2008 10:55:25 -0500</lastBuildDate>
      <generator>http://www.sixapart.com/movabletype/?v=3.21</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <item>
         <title>Now Hiring for the position of Web Programmer</title>
         <description><![CDATA[<p>If you've been following along at home, you already know that <a href="http://blog.buffalostate.edu/collegerelations/web/archives/2008/06/24/refreshing_news/">we are short one Web Applications Developer</a>. That will soon change, however, as we are now hiring for this position! The title has changed, and is now Web Programmer.</p>

<p>You can apply online at:<br />
<a href="https://jobs.buffalostate.edu/applicants/jsp/shared/frameset/Frameset.jsp?time=1219675740212">https://jobs.buffalostate.edu/applicants/jsp/<br />
shared/frameset/Frameset.jsp?time=1219675740212</a></p>

<h2>Here's some of the basic information:</h2>

<p>Brief Job Description:<br />
Responsible for developing, implementing, testing, and maintaining<br />
database-based applications, forms, and other interactive applications<br />
featured on/connected to the college's official Web site. Work closely and<br />
regularly with the College Relations Web team on data integration,<br />
customization, and display. Provide campus template users with content<br />
management system technical support.</p>

<p>Required Qualifications:<br />
Proficiency developing advanced, easy-to-use database-driven applications<br />
using PHP and SQL; experience developing applications that operate<br />
consistently on multiple platforms and browsers; ability to manage numerous<br />
projects simultaneously in a fast-paced environment; completion of some<br />
college-level coursework; two years related work experience.</p>

<p>Preferred Qualifications:<br />
Bachelor's degree; experience working in an Oracle environment; technical<br />
support experience; experience working in a higher education environment;<br />
basic Windows and/or Unix server administration experience; three years<br />
related work experience; familiarity with W3C Web Accessibility<br />
Guidelines/Section 508; familiarity with ASP, Perl, PL/SQL, Oracle 9i or<br />
above, XML/XHTML, CSS, SOAP, or Javascript.</p>

<p>Special Instructions to Applicants:<br />
Provide two live PHP and SQL application development work samples and a<br />
description of their role and responsibility for each project.</p>

<p>Take a look at our past entries, and you'll get a feel for where we are, and where we're going as a team. There's a lot of exciting things coming up, and we want you to be a part of it. Apply now!</p>

<p>Questions can be left in the comments, or by e-mailing <a href="mailto:kruczypt@buffalostate.edu">kruczypt at buffalostate dot edu</a>.</p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/08/25/now_hiring_for_the_position_of_web_programmer/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/08/25/now_hiring_for_the_position_of_web_programmer/</guid>
         <category>Web Team</category>
         <pubDate>Mon, 25 Aug 2008 10:55:25 -0500</pubDate>
      </item>
            <item>
         <title>Friday Highlight: Always Know What&apos;s Happening by Using Calendar Subscriptions</title>
         <description><![CDATA[<p>As mentioned <a href="http://blog.buffalostate.edu/collegerelations/web/archives/2008/08/15/friday_highlights_alumni_photos_and_handset_memories/">last week</a>, I was going to start a Friday Highlight series in order to showcase things that may be a bit different than our normal blog postings. I've already gotten some great feedback on the last post, so the series continues. Hooray! Throw your hats in the air, put your feet up, then take them back down because the boss is coming down the hall, and read on for this week's Friday Highlight. </p>

<h2>The Magic in Your Calendar</h2>

<p>Calendars aren't often considered very sexy applications when compared against other online offerings. "Calendars?," people say, "I think those are stupid compared to this YouTube video. Look how awesome it is!". And, like many things in life, unless it's <a href="http://www.youtube.com/watch?v=3q98WrVhaTg&feature=related">a video of Charles Nelson Riley dressed as a banana</a>, they're wrong.</p>

<p>Traditionally, one of the major problems with calendar applications was getting the information in there in the first place. Who wants to re-enter a bunch of information that may already exist someplace else? That's idiotic, and a waste of time. Luckily, you no longer have to waste your time.</p>

<p>The <a href="http://en.wikipedia.org/wiki/ICalendar">iCalendar file format</a> was invented to allow you to publish (share) and/or subscribe to calendars you find online. If a calendar is published in iCalendar format, just click on the link and faster than you can say Bic Banana: instant calendar data.</p>

<p>The great thing about subscriptions is that the data in your calendar is updated as soon as it's updated online. Subscribed to the <a href="http://www.buffalostate.edu/theater/">Theater Department</a> calendar? As they add events to their schedule throughout the year (or years to come), those events will show up on your calendar automatically. It's an easy way to keep track of U.S. holidays, local weather, and, most importantly, <a href="http://www.buffalostate.edu/events.xml">Buffalo State events</a>.</p>

<h2>Wait, Does Buffalo State Have This Available?</h2>

<p>You bet we do! In fact, we've had it available since <strong>2004</strong>! Unfortunately, while programs such as <a href="http://www.apple.com/ical/">iCal</a>, <a href="http://www.google.com/calendar">Google Calendar</a>, <a href="http://www.mozilla.org/projects/calendar/">Mozilla Calendar</a>, <a href="http://www.mozilla.org/projects/calendar/sunbird.html">Sunbird</a>, <a href="http://korganizer.kde.org/">KOrganizer</a>, <a href="http://www.horde.org/kronolith/">Kronolith</a>, and <a href="http://www.novell.com/products/evolution/">Novell Evolution</a> have supported subscriptions for years, previous versions of Outlook didn't completely support all the features available. With Outlook 2007, and its subsequent rollout on campus, these features are now available to you in the privacy of your public work area.</p>

<p>Subscribing is easy! I won't go into details, but <a href="http://www.buffalostate.edu/calendarsubscriptions.xml">details are available on our Web site</a>. Pick a calendar, and sign up today!</p>

<h2>Sounds Great, Where Can I Get More?</h2>

<p>There are many places to look, but <a href="http://icalshare.com/">iCalShare</a> is a good place to start. Just remember to look for it when you visits sites with event information--you may be surprised by how many people are using it!</p>

<p>Have a favorite calendar? Suffering from <a href="http://phobialist.com/index.html#N-">numerophobia</a>? Write a comment below, and let us know what you think!</p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/08/22/friday_highlight_always_know_whats_happening_by_using_calendar_subscriptions/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/08/22/friday_highlight_always_know_whats_happening_by_using_calendar_subscriptions/</guid>
         <category>Friday Highlight</category>
         <pubDate>Fri, 22 Aug 2008 11:50:10 -0500</pubDate>
      </item>
            <item>
         <title>Lite But Not Slight: College Emergency Page in Action</title>
         <description><![CDATA[<p>If you visited the Buffalo State Web site yesterday any time between 11:00 a.m. and noon, you may have noticed something very different about the look of the homepage. Well, that was exactly the point! </p>

<p>In case you missed it:</p>

<p><br />
<a href="http://blog.buffalostate.edu/collegerelations/web/archives/emergencypage.jpg"><img alt="emergencypagesmall.jpg" src="http://blog.buffalostate.edu/collegerelations/web/archives/emergencypagesmall.jpg" width="460" height="556" /></a></p>

<p>We chose the occasion of the <a href="http://www.buffalostate.edu/police/">University Police Department</a>’s <a href="http://www.buffalostate.edu/dailyarchive.xml?tyear=2008&tmonth=8&date=8/19/2008&deid=6605">Emergency Response Training (ERT) exercise</a> to try out the college’s emergency “lite” Web page. I’m proud to report that the test went off without a hitch.<br />
 <br />
The college has had an emergency Web notification system in place for many years, but the lite Web page is something the team has been working on for the past few months. What is it? Put simply, it is a no-frills method of presenting important information on the Web during a crisis. <br />
 <br />
Back in October, members of the Web team attended the <a href="http://www.highedweb.org/2007/">HighEdWebDev conference</a> in Rochester. Michael Dame, director of Web communications at <a href="http://www.vt.edu/">Virginia Tech</a>, delivered a presentation on crisis communications that was both moving and alarming. Dame’s lecture provided the inspiration for the design and development of this page.</p>

<p>In the event of an emergency, the regular Buffalo State homepage would be exchanged with this streamlined page which provides brief, time-stamped news entries and safety instructions. By including few graphics and no database pulls, there is less stress on the server in the event of a sudden spike in Web traffic. This ensures that the site stays up and that critical information can be updated.</p>

<p>All in all, the exercise was a complete success and campus got its first (and hopefully last) glimpse of the emergency page. <br />
</p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/08/20/lite_but_not_slight_college_emergency_page_in_action/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/08/20/lite_but_not_slight_college_emergency_page_in_action/</guid>
         <category></category>
         <pubDate>Wed, 20 Aug 2008 14:55:06 -0500</pubDate>
      </item>
            <item>
         <title>Friday Highlights: Alumni Photos and Handset Memories</title>
         <description><![CDATA[<p>One of the things that people always mention about Buffalo State is the strong sense of community people feel on campus. This sense of community is something we also see online in our <a href="http://www.buffalostate.edu/collegerelations/x1198.xml">forums</a>. However, it also continues after students graduate. So, I thought I'd try something new, a Friday Highlight, to showcase items a little different from our regular posts. We'll see how it goes, pending comments and feedback. Our first (only?) Friday Highlight is on Alumni.</p>

<h2>Theater Alumni</h2>

<p>The arts have a strong tradition at Buffalo State, and alumni are understandably proud of the work they and their peers have done. Theater alumni are no different. That's why it should be no surprise that there was recently a <a href="http://forum.buffalostate.edu/index.php?showtopic=3840">request for more photos of past productions</a> posted in the <a href="http://forum.buffalostate.edu/index.php?showforum=37">Theater Alumni forum</a>.</p>

<p>It's great to see people using tools such as the <a href="http://forum.buffalostate.edu/">Buffalo State Forums</a> and <a href="http://view.buffalostate.edu/">View</a> to stay in touch and share memories. It's also great to see people proud of their time at Buffalo State. Talking, sharing, and posting are all ways to help maintain that sense of Buffalo State community. It also helps to share the message that there is great work being done at Buffalo State--now, and in the past!</p>

<h2>Alumni Roamin' in the Wild</h2>

<p>Obviously, not all alumni discuss Buffalo State in our forums. They also do it on their own sites. We recently ran across a great story discussing <a href="http://roambuffalo.blogspot.com/2008/08/steppin-to-am.html">an alumni's first published logo as an undergrad at Buffalo State, for the 10th Annual Dance Marathon</a>. That student? Mark Wisz, co-owner of <a href="http://www.otherwisz.com/">Otherwisz</a> and <a href="http://www.wheretoroam.com/">Where to Roam</a>. This isn't the first time he's written about his early design experiences--just the first time that he happened to do so when I was making a new feature for our blog. You can find more at the <a href="http://roambuffalo.blogspot.com/">Roam Buffalo</a> blog.</p>

<h2>What's all the Hubbub?</h2>

<p>The hubbub is that, as we keep saying, we're focusing on the <a href="http://blog.buffalostate.edu/collegerelations/web/archives/2008/05/14/were_telling_stories/">story of Buffalo State</a>. One of the greatest disappointments, as a staff member, is knowing that many people here--students, faculty, and staff--are working or have worked on great projects that too few people know about. The only way to change that is to talk about what you do or have done--and shine a spotlight (or highlight) on those that are talking about Buffalo State.</p>

<h2>So, What About You?</h2>

<p>Are you an alumni or current student? Working on something great or inspiring? We always want to know what exciting things you may be doing. Comment below, or <a href="http://www.buffalostate.edu/collegerelations/x493.xml">contact us</a>!</p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/08/15/friday_highlights_alumni_photos_and_handset_memories/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/08/15/friday_highlights_alumni_photos_and_handset_memories/</guid>
         <category>Alumni</category>
         <pubDate>Fri, 15 Aug 2008 10:47:35 -0500</pubDate>
      </item>
            <item>
         <title>Blog to School: Do You Have Your Bloggers Yet?</title>
         <description><![CDATA[<p>As summer rudely begins its transformation into the school year, allow me to rudely interrupt your lazy August with this question: Do you have a blog yet? What about people to write those blogs?</p>

<p>No?</p>

<p>Well, <a href="http://blog.buffalostate.edu/fashion/">Fashion</a> and <a href="http://blog.buffalostate.edu/theater/">Theater</a> have blogs, to name <a href="http://blog.buffalostate.edu/">a few</a>, so why don't you?</p>

<p>If you're interested in a blog for the upcoming semester, I'll point you over to <a href="http://www.buffalostate.edu/collegerelations/x943.xml">College Relations Blog Information Area</a> (It's not really called that, but it sounds better than "the blog page") for more information.  This will give you the basic information you need about blogs on campus. Pay particular attention to the numbered list at the bottom of the page, <strong>especially</strong> the timeframes.</p>

<p>If it's a new blog, we need to know <strong>one month before</strong> the <strong>beginning</strong> of a semester. "But Paul," you say, "you're telling us this less than a month before school starts!". And, of course, I'll not let on that I was hoping you wouldn't notice. Which is why I'll tell you that we're having a Blog Blowout! Request your blog now! Quick! This sale only last through the end of next week!</p>

<p>If you already have a blog, then we'd like to remind you of equally important point number three: <strong>Your blog administrator will select student bloggers for a single semester or full academic year. The blog administrator will inform College Relations of the names of the student bloggers within the first 2 weeks of a new semester.</strong>. That's only three weeks away!</p>

<p>If you are interested in having a blog, please <a href="mailto:webadmin@buffalostate.edu">contact us</a>. If you're a student, and you love to write frequently, especially about your experiences here at Buffalo State, then <a href="mailto:webadmin@buffalostate.edu">contact us</a> and/or your <a href="http://www.buffalostate.edu/departments.xml">department chair</a>. Let's see what we can work out together. We love to have bloggers!</p>

<p>Thoughts on blogging? Thoughts on the writing style of this post? Thoughts? Share them below in the comments. Thanks!</p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/08/14/blog_to_school_do_you_have_your_bloggers_yet/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/08/14/blog_to_school_do_you_have_your_bloggers_yet/</guid>
         <category>Blogs</category>
         <pubDate>Thu, 14 Aug 2008 15:56:29 -0500</pubDate>
      </item>
            <item>
         <title>Our Refreshed Heading, Still Not Posted Online</title>
         <description><![CDATA[<p>Boy, do I have blog post on my face. Last time I posted, <a href="http://blog.buffalostate.edu/collegerelations/web/archives/2008/07/29/our_refreshed_heading_version_two/">I said</a> that I was going to have an update for you by last friday with the newest version of our heading in it. Well...</p>

<p>That didn't happen.</p>

<p>But: That's ok.</p>

<p>Why?</p>

<p>When refreshing or designing a site, it's normal to have things change. It's also normal to expect that if one design element changes, other parts of the page need to change as well. This is what happened to us last week. That, coupled with a crush of work brought on by Sue's impending vacation, meant that this just couldn't be completed to everyone's satisfaction by last friday.</p>

<p>Without an updated version of the header to share with you, I want to focus on the navigation we unveiled in the last post and highlight one item in particular:</p>

<p><a href="http://blog.buffalostate.edu/collegerelations/web/archives/header2.jpg"><img alt="header2small.jpg" src="http://blog.buffalostate.edu/collegerelations/web/archives/header2small.jpg" width="350" height="77" /></a></p>

<h3>News and Events</h3>
<p>After a several year absence, news and events are returning to a prominent place in our main navigation. Sue said it before, but <a href="http://blog.buffalostate.edu/collegerelations/web/archives/2008/05/14/were_telling_stories/">we're telling stories</a> in this new site. One of the lost stories about our campus, is just how much is going on, <strong>on campus</strong>! There are always <a href="http://www.buffalostate.edu/events.xml">events</a>, <a href="http://www.buffalostate.edu/news.xml">news</a>, and more going on at Buffalo State College. Unfortunately, what we often hear, is that people don't always know what's happening on campus. We highlight items on <a href="http://www.buffalostate.edu/">our homepage</a>, list them in the <a href="http://www.buffalostate.edu/events.xml">events calendar</a>, <a href="http://www.buffalostate.edu/daily.xml">the <em>Daily</em></a>, <a href="http://www.buffalostate.edu/deptoffice.xml">department and office</a> sites, as well as <a href="http://www.buffalostate.edu/students.xml">throughout our main site</a>. Despite this, we still hear a need for <strong>more information</strong>.</p>

<p>Pulling out news and events into their own section is exciting! It will help first-time visitors to the site, as well as the campus community, have a very visible overview of what's happening on campus. It will also allow us to showcase the news and community we have--in the <a href="http://www.buffalostate.edu/bulletin/"><em>Bulletin</em></a>, <a href="http://blog.buffalostate.edu/">Blog Central</a>, the <a href="http://view.buffalostate.edu/">View photo gallery</a>, the <a href="http://ask.buffalostate.edu/">Ask Buffalo State</a> and <a href="http://forum.buffalostate.edu/">Buffalo State Forums</a>, and more--that make up such a vital part of the story of Buffalo State, both on- and offline.</p>

<p>Of course, we can't do it without you. If you have an event to promote, <a href="http://www.buffalostate.edu/submitevent.xml">submit it to the events calendar</a>, then <a href="http://www.buffalostate.edu/createpodcasts.xml">record it for a podcast</a>. Have an announcement? Put it in the <a href="http://www.buffalostate.edu/dailysubmit.xml"><em>Daily</em></a>! News can be shared via our <a href="http://www.buffalostate.edu/news.xml">news releases</a>. There are <a href="http://www.buffalostate.edu/rss.xml">a lot of tools</a> that already exist for you to promote your event, yourself, and Buffalo State, to the world--and there are more to come!</p>

<p>This is a basic overview of where we're going. More specifics will come soon--which, I've learned, is the safest timeframe to give sometimes.</p>

<p>How does this sound to you? Good? Bad? Somewhere in the middle? Leave a comment below and let us know.</p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/08/06/our_refreshed_heading_still_not_posted_online/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/08/06/our_refreshed_heading_still_not_posted_online/</guid>
         <category>Refresh</category>
         <pubDate>Wed, 06 Aug 2008 11:18:06 -0500</pubDate>
      </item>
            <item>
         <title>Our Refreshed Heading, Version Two</title>
         <description><![CDATA[<p>As much as I have been keeping track of time, it's unbelievable how quickly this summer is flying by for us. When time flies, updates walk, which means the latter get later and later. There is a good reason for the delay, however.</p>

<h2>A Funny Thing Happened on the Way to the Blog Post</h2>

<p>A few weeks ago, I was ready to post an entry on our refresh. Content and concepts were being worked on. Features were being refined. Navigation was being renamed. The site was really taking shape, with all the different page types beginning to hang together. Watching a site come to life is one of the most exciting parts of working on a project. No matter how much you plan ahead, those plans change once you begin building a site. So, once it begins to come together, it's great. To celebrate, I wanted to share what we'd been working on!</p>

<p>Unfortunately, it wasn't good enough.</p>

<p>As good as the heading had become, we decided it just wasn't good enough. Back to the drawing board (or Photoshop, as the case may be).</p>

<p>This doesn't mean I don't have an update for you, because I do. <strong>It's not the current version of the header.</strong> This is the header we had <em>before</em> we made some changes. <strong>The current version will be up later this week.</strong> In the meantime, here are <a href="http://blog.buffalostate.edu/collegerelations/web/archives/2008/03/31/new_views_1/">versions one</a> and two presented for you to compare. Click on the thumbnails for larger versions:</p>

<p><br />
Here's what you saw before:<br />
<a href="http://blog.buffalostate.edu/collegerelations/web/archives/header1.jpg"><img alt="header1small.jpg" src="http://blog.buffalostate.edu/collegerelations/web/archives/header1small.jpg" width="350" height="98" /></a></p>

<p><br />
And here's where we were before starting over (again, <strong>not the current version of the header</strong>):<br />
<a href="http://blog.buffalostate.edu/collegerelations/web/archives/header2.jpg"><img alt="header2small.jpg" src="http://blog.buffalostate.edu/collegerelations/web/archives/header2small.jpg" width="350" height="77" /></a></p>

<p>Among the changes to this design: the main navigation was redesigned, the search box refined, and, overall, the header was streamlined.</p>

<p>Here they are again, compared top to bottom:<br />
<img alt="headerentry.jpg" src="http://blog.buffalostate.edu/collegerelations/web/archives/headerentry.jpg" width="350" height="175" /></p>

<p><br />
The other big change is that we've included our new navigation, <a href="http://blog.buffalostate.edu/collegerelations/web/archives/2008/03/31/new_views_1/">previously omitted</a>. There will be posts with more information about the navigation, as well as the new and improved site design, coming soon.</p>

<p>Otherwise, we are working away our summer. This isn't the only exciting thing we're working on right now. We'll all be writing more about forthcoming features in the days and weeks to come.</p>

<p>We want to know what you think about the design so far. Do you like the direction we're heading in? What would you like to know more about? This blog is to help us know what the community is interested in, so please leave a comment below.</p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/07/29/our_refreshed_heading_version_two/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/07/29/our_refreshed_heading_version_two/</guid>
         <category>Refresh</category>
         <pubDate>Tue, 29 Jul 2008 10:43:04 -0500</pubDate>
      </item>
            <item>
         <title>Refreshing News</title>
         <description><![CDATA[<p>There are a few big news items to report as we forge ahead on our refresh of the Buffalo State Web site. First, Aaron Knoll, our intrepid Web Applications Developer, has left Buffalo State to return to school. As sad as this makes us, we wish Aaron nothing but the best on his future endeavors. "Yes," you may say, "we know that already. What about the refresh?". A good (hypothetically posited) question.</p>

<p>Here's the non-hypothetical answer: we are still doing a refresh. Although certain aspects of the project have changed in the short-term, we're still committed to refreshing the main Buffalo State Web site. We're still <a href="http://blog.buffalostate.edu/collegerelations/web/archives/2008/05/14/were_telling_stories/">telling stories</a> and bringing <a href="http://blog.buffalostate.edu/collegerelations/web/archives/2008/03/31/new_views_1/">new views</a> to the site.</p>

<p>We are also still committed to updating our blog, I swear. Watch this space for more updates as the summer progresses.</p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/06/24/refreshing_news/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/06/24/refreshing_news/</guid>
         <category>Refresh</category>
         <pubDate>Tue, 24 Jun 2008 15:25:39 -0500</pubDate>
      </item>
            <item>
         <title>We&apos;re Telling Stories</title>
         <description><![CDATA[<p><img alt="stories.jpg" src="http://blog.buffalostate.edu/collegerelations/web/stories.jpg" width="350" height="175" /><br /><br />
Whenever we ask someone what makes Buffalo State so special, so great, so different, we almost always get the same answer: “We do!” In the upcoming refresh, we’ll be telling stories about what make us so interesting—people, places, and things on campus that stand out and have a story to tell, things that are unique to us. Things that are <a href="http://blog.buffalostate.edu/collegerelations/web/archives/2008/01/29/id_never_buy_an_orange_car/">orange</a> I guess! Stay tuned…</p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/05/14/were_telling_stories/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/05/14/were_telling_stories/</guid>
         <category></category>
         <pubDate>Wed, 14 May 2008 13:05:30 -0500</pubDate>
      </item>
            <item>
         <title>Web 2.0 Webinar</title>
         <description><![CDATA[<p>The College Relations Web Team hosted a webinar on April 24, 2008. Here's a brief summary and the handouts incase you were unable to attend.</p>

<p><strong>Web 2.0: What It Means, How It Works, And How To Use It To Your Advantage</strong<br />
Web 2.0 is significantly altering the higher education marketing landscape. As a social and cultural phenomenon, it's transforming nearly every aspect of digital communication, from Web site design and content creation to search. This session will clarify the phenomenon and its ramifications, and explore the 2.0 tools, strategies, and tactics colleges and universities should add to their marketing, recruiting, and advancement arsenals.</p>

<p>You'll gain an understanding of: <br />
•	The similarities and differences among the key social media platforms and technologies <br />
•	The rules for engagement that underlie any effective 2.0 strategy <br />
•	How to build your own 2.0 community and be part of existing communities <br />
•	How to integrate 2.0 principals and tactics into traditional marketing</p>

<p>Download the handout: <a href="http://blog.buffalostate.edu/collegerelations/web/socialmediawebinarhandouts.pdf">Web 2.0 Webinar  (PDF, 800KB)</a></p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/04/25/web_20_webinar/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/04/25/web_20_webinar/</guid>
         <category></category>
         <pubDate>Fri, 25 Apr 2008 13:29:56 -0500</pubDate>
      </item>
            <item>
         <title>Finding Ways to be Found</title>
         <description><![CDATA[<p>One thing that has come up on this blog, are people's <a href="http://blog.buffalostate.edu/collegerelations/web/archives/2008/03/11/searching_for_search_results/#comment-96">feelings about the search engine</a>. This reminded me of an incident I encountered recently, that I thought I would relate here.</p>

<p>A user contacted College Relations about their site, which wasn't showing up in the search results. "Surely," thought the user, "the search engine must be broken, right?". I can understand this line of thinking, if only because I think the same thing sometimes. Search, as a tool, has gotten so much better, and become so pervasive to our computing lives (like Mark's example in his linked comment, above), that when it doesn't work, one assumes the fault lies in the search engine.</p>

<p>This is not always the case.</p>

<p>A search engine is only as good as the content that feeds it. Oh sure, there can be poor search engines. In fact, there have been several search engines at Buffalo State, with the first (circa 2001-2002) being particularly unhelpful. Now, however, we use the Google Mini. This follows the same search methods as Google--you know, <a href="http://www.google.com/">http://www.google.com/</a>. So where was the user's site?</p>

<p>As I said, it's about content. Part of the content is having people link to your site. The user's site didn't show up, because there were no links to it anywhere on the Buffalo State Web site. If there are no links to your Web site, then the search engine isn't going to be able to find it. Thus, no search results for your site. Links are a Web site's word-of-mouth, and without it, a search--like a store or restaurant--is going to fail.</p>

<p>Luckily, it's easy to check who's linking to your site by using the search engine. As I said, it's a Google product, so the tips in <a href="http://www.google.com/help/cheatsheet.html">Google's Cheat Sheet</a> apply to our search as well. To see who's linking to your site, try adding <code>link:</code > ahead of your site, ex. link:www.buffalostate.edu/collegerelations. This shows me <a href="http://search.buffalostate.edu:80/search?q=link%3Awww.buffalostate.edu%2Fcollegerelations&btnG=Google+Search&site=buffalostate&output=xml_no_dtd&client=buffalostate&proxystylesheet=buffalostate">everywhere on our Web site that links to the College Relations index page</a>.</p>

<p>There are other things that affect search rankings. Making sure your site is found, however, is an easy first step. The moral of this story? Next time you can't find something, consider this: it may not exist in the first place.</p>

<p>As part of the refresh, we are adding some exciting new features to our search results. I hope to write more about those soon. In the meantime, do you have any search issues you'd like to share? If so, comment below.</p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/04/22/finding_ways_to_be_found/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/04/22/finding_ways_to_be_found/</guid>
         <category>Search Engine</category>
         <pubDate>Tue, 22 Apr 2008 13:10:34 -0500</pubDate>
      </item>
            <item>
         <title>New Views</title>
         <description><![CDATA[<p><img alt="side-by-side comparison of the current and redesign site layout" src="http://blog.buffalostate.edu/collegerelations/web/archives/prestochango.jpg" width="350" height="175" /><br /></p>

<p><em>"Presto chango!"</em> What an expression, what a concept. Too bad reality doesn't allow for radical change with the mere utterance of a phrase or pressing of an "easy button." Still, sometimes transformations do happen quickly with dramatic results. </p>

<p>Case in point, the comps/initial drafts of the new academic sub pages we've designed.  </p>

<p>You've been patient, dear reader, and absorbed our posts on the philosophy, research, and challenges that have informed our upcoming redesign. Now we have some examples for you to see and are eager to read your feedback.</p>

<p><br />
<strong>Here's an example of a section page from our current site:</strong></p>

<p><br />
<a href="http://www.buffalostate.edu/admissions.xml"><img alt="screen capture of current section page" src="http://blog.buffalostate.edu/collegerelations/web/archives/current.gif" width="460" height="596" /></a></p>

<p><br />
Now with a wave of the wand, and months of design brainstorming, discussions, and creation, watch as we pull a rabbit out of our collective sleeves to reveal the initial designs of our new section page and sub page. </p>

<p>Oh, what the heck? "PRESTO CHANGO!"</p>

<p></p>

<p><strong>Section page</strong>  <br />
<a href=" http://blog.buffalostate.edu/collegerelations/web/sectionpage.jpg" alt="section page with expanded nav and Flash piece"><img alt="redesigned section page" src="http://blog.buffalostate.edu/collegerelations/web/archives/section.jpg" width="460" height="465" /></a><br />
<a href=" http://blog.buffalostate.edu/collegerelations/web/sectionpage.jpg" alt="section page with expanded nav and Flash piece">View larger image >></a></p>

<p></p>

<p><br />
<strong>Sub page</strong>  <br />
<a href=" http://blog.buffalostate.edu/collegerelations/web/subpage.jpg" alt="sub page with photos"><img alt="redesigned sub page" src="http://blog.buffalostate.edu/collegerelations/web/archives/schoolssub.jpg" width="460" height="540" /></a><br />
<a href=" http://blog.buffalostate.edu/collegerelations/web/subpage.jpg" alt="sub page with photos">View larger image >></a></p>

<p></p>

<p><br />
Pretty dramatic, huh? As always we've kept an eye for clean, accessible, and efficient designs that are standards-compliant. However, we're also looking to draw the visitor into a page that presents needed information clearly while highlighting some of the Web 2.0 content features (podcasts, blogs, etc.) contained in the site. </p>

<p><strong><br />
Now, onto the fun stuff (and a caveat*)</strong></p>

<p><em>Section page</em><br />
This new section page contains all of the useful features you're accustomed to, but allows for the page navigation to be contained neatly on the left while giving prominent real estate to highlighting academic programs, events, announcements, and more on the right. The images in the large photo box on the right represent flash pieces that will rotate automatically or may be navigated through. </p>

<p>Without sounding too abstract, I've come to think of the section page as containing the "guts and the glory" of our new vision. On the left, visitors will be presented with the "guts" of the section: usable, searchable, functional content. On the right, the "glory" is represented by sites, sounds, and stories of Buffalo State. Those unique and compelling people, places, and things that make Buffalo State tick. I think there's plenty of overlap in both sections, but enough focus to keep both succinct.</p>

<p><em>Sub page</em><br />
The sub page currently has a fairly bare bones design. There's a lot of whitespace in that right hand column, but we're looking to fill it with needed, useful content. In the particular case, the main content area of this sub page highlights the various schools at Buffalo State. It is very likely that these highlights would contain links to the <a href="http://view.buffalostate.edu/main.php?g2_itemId=24310">photo gallery</a>, <a href="http://www.buffalostate.edu/podcastcategories.xml?podcatid=1">podcasts</a>, <a href="http://blog.buffalostate.edu/">blogs</a>, and more.</p>

<p>Of course, I know what I think, but am eager to hear your thoughts on these new pages. Please take a look at these comps and let us know what you think.</p>

<p><strong>*A Caveat</strong><br />
We've intentionally left out the real/current content out of this comp in order to focus on design. Fear not, this is intentional. Hence, the "Navigation" headings and "lorem ipsum" text will be replaced well in advance of the launch of these pages!</p>

<p>These comps represent a look, or a feel, if you will-not necessarily the final design. As we work with our content and move onto other pages and page types being redesigned, there’ll be some tweaks, changes, and "Aha!" moments. The Web is like a plant, a living, breathing thing, and we’re always on the look-out for ways to make it grow.</p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/03/31/new_views_1/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/03/31/new_views_1/</guid>
         <category>Refresh</category>
         <pubDate>Mon, 31 Mar 2008 11:25:09 -0500</pubDate>
      </item>
            <item>
         <title>The Size of the fight in the dog?</title>
         <description><![CDATA[<p><em>“The true test of civilization is, not the census, nor the size of the cities, nor the crops, but the kind of man that the country turns out.”</em> -Ralph Waldo Emerson</p>

<p>I love new technology. We all do on the web team, and we alike many other web design teams grapple with the classic ‘catch 22’ of web design: how to support as many new technologies, while keeping your content accessible to everyone regardless of the type or age of the computer they have? </p>

<p>(Wondering what screen resolution is? <a href="http://en.wikipedia.org/wiki/Display_resolution">Wikipedia has a solid introduction</a>)</p>

<p>Monitor technology has come a long way from when I first started developing websites in the 1990s. Most people’s screen resolutions were 640 x 480, which limited the amount of design real estate you had available. Slowly, but surely, technology advanced and by the turn of the new millennium the web design community was noticing that the number of users using <a href="http://evolt.org/640_x_480_Isnt_Dead_Just_Yet">640 x 480 was dropping down to critically low numbers</a>. Slowly, web designers began to drop support for the older resolutions and <a href="http://www.w3schools.com/browsers/browsers_display.asp">wider more robust designs became the norm</a>.</p>

<p><strong>Back to the Present</strong></p>

<p>Just nine years later, web designers are again having a similar discussion, but this time about 800 x 600. Can we design a larger site for larger resolutions? To find out, we went to the numbers, and there were a few surprises.</p>

<p><img src="http://wwwu.buffalostate.edu/blogimages/pi-chart.png"></p>

<p>An ongoing test of the <a href="http://view.buffalostate.edu">Buffalo State Gallery</a> has revealed that only 2.17% of users were using our website with a screen resolution of 800 x 600. Nearly 98% of our users had resolutions of 1024 x 768 or greater (<a href="http://wwwu.buffalostate.edu/blogimages/numbers.png">view numbers here</a>). Others have found <a href="http://web-design-book.com/2007/10/13/should-i-support-800-by600-resolution/">similar results</a> when surveying their own websites. The wider monitors mean more space to deliver content, which allows us to make the design more readable and more usable. </p>

<p><strong>But what about that 2.17%?!</strong></p>

<p><img src="http://wwwu.buffalostate.edu/blogimages/800x600.png"></p>

<p>We haven’t forgotten. As I said above, we strive to keep our content accessible to all people regardless of their browser size. Therefore, we need a plan if we want to design a site wider than 800 pixels, and for inspiration we sometimes have to look in unusual places (maybe some may find this surprising, but I’m a huge fan of hockey, so this is an example I see every day). ESPN.com has a great example of design for resolutions greater than 800 pixels wide, while still providing all the primary content within the first 700 pixels. </p>

<p><a href="http://wwwu.buffalostate.edu/blogimages/espnat800.jpg">Espn.com viewed on an 800 x 600 resolution monitor</a><br />
<a href="http://wwwu.buffalostate.edu/blogimages/espnat1024.jpg">Espn.com viewed on a 1024 x 768 or higher resolution monitor</a></p>

<p>All of the content to the right of the “horizontal fold” for users on 800 x 600 is extra content. The top news stories, navigation, and features are all safely to the left of the page, so that if you don’t have a larger monitor- you don’t miss anything. </p>

<p><strong>And now on to the future…</strong></p>

<p>So with this knowledge in hand, and positive examples from other major websites including <a href="http://www.cnn.com">CNN</a>, <a href="http://cbs.com">CBS</a>, <a href="http://Amazon.com">Amazon.com</a>,<a href="http://msn.com"> MSN</a>, <a href="http://www.yahoo.com">Yahoo</a>, and other colleges like<a href="http://www.cmu.edu/index.shtml"> Carnegie-Melon</a> and<a href="http://www.unl.edu/"> UNL</a>, we here on the web team feel that it’s time to design a wider site to support the larger monitor resolutions that our users are using. Onward! As we continue to embrace technology while supporting all of our users! <br />
</p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/03/20/the_size_of_the_fight_in_the_dog/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/03/20/the_size_of_the_fight_in_the_dog/</guid>
         <category>Refresh</category>
         <pubDate>Thu, 20 Mar 2008 16:25:51 -0500</pubDate>
      </item>
            <item>
         <title><![CDATA[Searching for Clich&eacute;s? Now You'll Find Them!]]></title>
         <description><![CDATA[<p>The third time's a charm! Good things come in threes, but why should that be a surprise? After all, three is the magic number. It's also true that a Google Mini in the rack is worth two on the FedEx truck back to Cali. Of course, like my grandpa always said, don't count your queries before the crawl's hatched! Phew. Ok, enough of that.</p>

<p>As discussed recently, <a href="http://blog.buffalostate.edu/collegerelations/web/archives/2008/03/11/searching_for_search_results/">we've been having some problems with our search engine</a>. After many rounds of e-mail (and one terse message left with Google's voicemail), we now have a solution in place.</p>

<p>The culprit? A software bug that Google is currently tracking. Unfortunately, that meant installing another Google Mini (the third in the last month). Then, troubleshooting an apparent delay in the search engine beginning its crawl again. A support ticket is still out on that particular issue. However, it's currently re-indexing the site as we speak, so search results should be back to normal by the end of the day.</p>

<p>The lesson to take away from this? That although the Web is awesome and magical, there isn't always a fast solution. Even when dealing with what may be a known bug to a vendor, having to co-ordinate with support that is at least three time zones away can be challenging. Once the issue has been identified, a new machine has to be shipped, arrive, get configured, have magic incantations said over it, and installed. For installation, we first have to co-ordinate with Computing and Technology Services to find a time in both our schedules when we can install the new machine (the incantations can really take up a lot of time).</p>

<p>As much as I may wish there was a magic wand for these issues, one isn't always available. For the end users, as well as our own team, this can be frustrating. I, for one, appreciate everyone's patience so far.</p>

<p>Off to the searches!</p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/03/18/searching_for_cliches_now_youll_find_them/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/03/18/searching_for_cliches_now_youll_find_them/</guid>
         <category>Search Engine</category>
         <pubDate>Tue, 18 Mar 2008 10:40:34 -0500</pubDate>
      </item>
            <item>
         <title>Revisiting Content Management</title>
         <description><![CDATA[<p>In addition to undertaking a site-wide redesign, the Web team is also exploring CMS options. </p>

<p>Why are we revisiting CMS? At a crossroads of sorts, we are contemplating either a significant upgrade to Ingeniux, our current content management system (CMS), or possibly moving to a new package. Both actions will require us to retrain campus users, so we're exploring all options. </p>

<p>And options there are. There are more than 50 CMSs out there now (not so in 2004 when we implemented). Further, we are now fully staffed and have UNIX in the mix (again, not the case when we first implemented). </p>

<p>We felt our very first step in this process should be to check in with campus users. Last week, the team had the pleasure of meeting with two groups of highly engaged faculty and staff to discuss their experiences with Ingeniux and/or self-publishing. We reached out to more than 30 CMS users and campus technology advocates for their input; nine met with us across two sessions. We enjoyed our discussions! The atmosphere was intimate; everyone got a chance to share on almost all topics covered.  </p>

<p>This is the feedback we received, which will help us develop our feature list: </p>

<p><strong>Tuesday, March 11, 2008, 1:30-3:00 p.m.:</strong><br />
1) Make sure Mac users can access the CMS using any Mac and many browsers <br />
2) Offer the capability to make Web forms<br />
3) Will there be space for large media files? How will video work?<br />
4) Can we use the CMS for individual faculty pages or department intranets?<br />
5) How to stop some code I put in from being stripped out<br />
6) Be able to just cut and paste content in (not have to save as plain text first)<br />
7) Can the look and feel be more blog-like? <br />
8) I'd like integrated podcasts, RSS, etc.<br />
9) Easy to use, but enough tools for the power user<br />
10) Faster save<br />
11) Easier to upload PDFs<br />
12) Upload my own images</p>

<p><strong>Friday, March 14, 2008, 9:30-11:00 a.m.:</strong><br />
1) Make sure Mac users can access the CMS using any Mac and many browsers <br />
2) Offer the capability to make Web forms<br />
3) Make it really easy to use -- drag and drop<br />
4) Shorter training sessions<br />
5) Can we use the CMS for individual faculty pages? Can students use it?<br />
6) Upload my own images<br />
7) Faster save<br />
8) Be able to just cut and paste content in (not have to save as plain text first)</p>

<p>Much of what we heard was stuff we, too, would like to change. And we think we can. What was interesting--and heartening--was to hear that both groups wanted to be a part of the process as it unfolds. So, we agreed to start a discussion via the blog. Please keep in mind, continued feedback on CMS likes/dislikes/wish list items is welcome; add a comment here. Note: If a third feedback session is of interest, we'll certainly hold one.</p>

<p>We will use the feedback we received last week, as well as our own experiences with CMS, to develop user-centered specifications. We'll also be connecting with our colleagues in Computing and Technology Services for help in developing server and technical specifications.</p>

<p>My next post will include information on what other people are doing when it comes to CMS (both user groups were eager to know what other campuses ran). I can share a little now--this March 11, 2008, UWeb-D round table on <a href="http://uwebdroundtable.wordpress.com/2008/03/11/choosingcomparing-cmss/">Choosing/Comparing CMSs</a> offers a glimpse at what some institutions are using or thinking about using... and why... and how...</p>]]></description>
         <link>http://blog.buffalostate.edu/collegerelations/web/archives/2008/03/17/revisiting_cms/</link>
         <guid>http://blog.buffalostate.edu/collegerelations/web/archives/2008/03/17/revisiting_cms/</guid>
         <category>CMS</category>
         <pubDate>Mon, 17 Mar 2008 16:05:05 -0500</pubDate>
      </item>
      
   </channel>
</rss>
