<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Webteam</title>
	<atom:link href="http://blogs.uakron.edu/webteam/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.uakron.edu/webteam</link>
	<description>Just another Blogs.uakron.edu weblog</description>
	<lastBuildDate>Fri, 11 Apr 2008 22:00:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>New Site Designs</title>
		<link>http://blogs.uakron.edu/webteam/2008/04/11/new-site-designs/</link>
		<comments>http://blogs.uakron.edu/webteam/2008/04/11/new-site-designs/#comments</comments>
		<pubDate>Fri, 11 Apr 2008 22:00:29 +0000</pubDate>
		<dc:creator>Eric W Kreider</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.uakron.edu/webteam/2008/04/11/new-site-designs/</guid>
		<description><![CDATA[Websites get old and when they get old they get tangled and gnarly. In the past, the solution to this dilemma often was to put up pretty new pictures and change all of the navigation on the site. This would work for a while until the site visitors began to realize that they still couldn’t [...]]]></description>
			<content:encoded><![CDATA[<p>Websites get old and when they get old they get tangled and gnarly. In the past, the solution to this dilemma often was to put up pretty new pictures and change all of the navigation on the site. This would work for a while until the site visitors began to realize that they still couldn’t get to / find what they needed and the shine quickly wore off.</p>
<p>Today, we want to consider what we are changing and why. Who are we trying to reach with our site? How will the experience of the visitor improve? The answers to these questions are about the site architecture, how the site is organized and the content of the pages and not so much about the look and feel.</p>
<p>Beginning in May of 2007 the University engaged a nationally known, educationally focused consulting firm, Dotmarketing. In the ensuing time span we have worked with Dotmarketing to dissect every piece of the current University site at <a href="http://www.uakron.edu">www.uakron.edu</a>.  The site at <a href="http://www.uakron.edu">www.uakron.edu</a> is better known as our homepage and comprises our forward looking face. In other words, the primary audience for this site are visitors who are, generally, from outside the University community; prospective students and their parents, corporate and university researchers, potential employees, the press, etc.</p>
<p>Today, the fruit of that labor is ready to show as we have <a href="http://www.uakron.edu/webteam/newdesigns.php">New Web Page Designs</a>, layered over a much improved architecture available to view and a <a href="https://survey2.uakron.edu/designfeedback.aspx">Design Feedback Survey</a> so you can tell us what you think.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.uakron.edu/webteam/2008/04/11/new-site-designs/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Passwords at the University of Akron</title>
		<link>http://blogs.uakron.edu/webteam/2007/06/13/hello-world/</link>
		<comments>http://blogs.uakron.edu/webteam/2007/06/13/hello-world/#comments</comments>
		<pubDate>Wed, 13 Jun 2007 20:31:09 +0000</pubDate>
		<dc:creator>Eric W Kreider</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[ 
Password policy at the University has changed. There are many good reasons this is being done, but, the most important is to protect your data from people who would steal it.
Passwords now expire
Back in the day, if you were particularly daring, you could get through your entire college career without changing your UANet password. [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://www.uakron.edu/images/ua_logo.gif" alt="UA Logo" /> </p>
<p>Password policy at the University has changed. There are many good reasons this is being done, but, the most important is to protect your data from people who would steal it.</p>
<p><strong>Passwords now expire</strong><br />
Back in the day, if you were particularly daring, you could get through your entire college career without changing your UANet password. No more.</p>
<p>Beginning June 1st of this year, passwords expire every 180 days. An email will be sent to remind you to reset your password as the 180-day expiration<br />
period draws near.</p>
<p>To change your password, go to <a href="https://gozips.uakron.edu/zid/app/">https://gozips.uakron.edu/zid/app/</a>, login with your<br />
UAnet ID and current password. Select the “Password” tab and click on “Change the<br />
password of my UAnet ID.”</p>
<p><strong>Make a strong password</strong><br />
The basic rules for you new UANet password are:</p>
<ul>
<li>Minimum of 8 characters consisting of at least one letter and one number. </li>
<li>Mixed case (upper and lower) and special characters ($ # (&amp; * @, etc.) are acceptable, but not required.</li>
<li>NO Spaces.</li>
</ul>
<p>There are many sites out there that can help with strong password creation like:</p>
<p><a href="http://www.microsoft.com/protect/yourself/password/create.mspx">Strong passwords: How to create and use them</a><br />
<a href="http://en.wikipedia.org/wiki/Password_strength">Password strength &#8211; Wikipedia</a><br />
<a href="http://www.smat.us/sanity/pwdilemma.html">The Strong Password Dilemma &#8211; from the Center for Password Sanity</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.uakron.edu/webteam/2007/06/13/hello-world/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
