<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>Web Development Blog &#187; Web File Organization and Naming Conventions | Web Development Blog &#8211; Heidi Cool &#8211; Cleveland, Ohio</title>
	<atom:link href="http://www.heidicool.com/blog/category/planning-your-website/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.heidicool.com/blog</link>
	<description>web • content • marketing • navigation • seo • social media</description>
	<lastBuildDate>Thu, 17 Feb 2011 21:09:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<!-- podcast_generator="podPress/8.8" -->
		<copyright>&#xA9; </copyright>
		<managingEditor>gravity69@gmail.com ()</managingEditor>
		<webMaster>gravity69@gmail.com()</webMaster>
		<category></category>
		<itunes:keywords></itunes:keywords>
		<itunes:subtitle></itunes:subtitle>
		<itunes:summary>content bull; architecture bull;nbsp;marketing bull;nbsp;seo bull; social media</itunes:summary>
		<itunes:author></itunes:author>
		<itunes:category text="Society &amp; Culture"/>
		<itunes:owner>
			<itunes:name></itunes:name>
			<itunes:email>gravity69@gmail.com</itunes:email>
		</itunes:owner>
		<itunes:block>No</itunes:block>
		<itunes:explicit>no</itunes:explicit>
		<itunes:image href="http://www.heidicool.com/blog/wp-content/plugins/podpress/images/powered_by_podpress_large.jpg" />
		<image>
			<url>http://www.heidicool.com/blog/wp-content/plugins/podpress/images/powered_by_podpress.jpg</url>
			<title>Web Development Blog</title>
			<link>http://www.heidicool.com/blog</link>
			<width>144</width>
			<height>144</height>
		</image>
		<item>
		<title>Web File Organization and Naming Conventions</title>
		<link>http://www.heidicool.com/blog/2006/06/20/web-file-organization-and-naming-conventions/</link>
		<comments>http://www.heidicool.com/blog/2006/06/20/web-file-organization-and-naming-conventions/#comments</comments>
		<pubDate>Wed, 21 Jun 2006 00:03:02 +0000</pubDate>
		<dc:creator>Heidi Cool</dc:creator>
				<category><![CDATA[Heidi's Entries]]></category>
		<category><![CDATA[How-to]]></category>
		<category><![CDATA[Planning Your Website]]></category>
		<category><![CDATA[Tips and Tricks]]></category>

		<guid isPermaLink="false">http://www.heidicool.com/blog/?p=49</guid>
		<description><![CDATA[At home, entropy reigns supreme. My friends will attest that a visit to Heidiland&#8212;replete with obstacles ranging from art supplies to Pisa-like stacks of books&#8212;is an adventure that would be considered overly-taxing by the neat freaks of the world. My computers, however, are another story. Given that my active Web development folder has over 14,000 files within, and that this is but one of many folders on one of three computers, I've had to take a more logical approach.
]]></description>
			<content:encoded><![CDATA[<p>At home, entropy reigns supreme. My friends will attest that a visit to Heidiland&mdash;replete with obstacles ranging from art supplies to Pisa-like stacks of books&mdash;is an adventure that would be considered overly-taxing by the neat freaks of the world. My computers, however, are another story. Given that my active Web development folder has over 14,000 files within, and that this is but one of many folders on one of three computers, I've had to take a more logical approach. </p>

<p>Organizing files in a methodical manner is even more important when it comes to the files that make up a Web site. On the Web server this structure must make sense not only to me, but also to end users and anyone who contributes content to the site. Below I'll walk you through the concepts I use to organize my files. You may find that another system works better for you and the needs of your site, but if you consider the following issues it may help you enhance your system as well.</p>
<h5>Create a directory somewhere on your computer or network that will be the master directory for your site. </h5>
<p class="photoright"><img alt="folders.jpg" src="http://blog.case.edu/webdev/2006/06/20/folders.jpg" width="220" height="246" />
</p>
<p>Try to keep all files related to the site in this directory. While Dreamweaver and other programs will let you create links to files almost anywhere on your computer or network, these stray files can cause problems when the time comes to upload the site to the Web server. I find it is also helpful to include working files such as Word and Photoshop documents here, so that I can refer back to them as necessary.</p>
<h5>Match your file structure to your site map.</h5>
<p>In my earlier entry, <a href="http://blog.case.edu/webdev/2005/08/25/organizing_acquiring_and_creating_content_for_your_website_part_one"><em>Organizing,
acquiring, and creating content for your website</em></a>, I wrote about creating
a site map that would organize your content and navigational structure. The
fictional <a href="http://blog.case.edu/webdev/2005/08/25/cartooningmap.pdf">Department
of Cartooning's map</a> showed us 6 main content areas that would be reflected
in our menus. Thus when I began building this site, I started by creating folders
for each of these content areas. I also created three additional folders; css,
images and ssi, in which I store my cascading style sheets, photographs, and <a href="http://www.case.edu/webdev/webtoolkit/quick/index.html#ssi">server-side
includes</a> files. Categories such as Academics and Resources that have multiple
subcategories will similarly have multiple subfolders within. As I build my site
I'll store my files in the appropriate folders&mdash;rather than loose in one main
folder&mdash;for the following reasons.</p>
<ul>
<li>In the future it will be easier to find the page I must edit if I am looking in a folder containing only 10 files, than it will be if I have to sort through all 50, 100 or possibly even more files.</li>
<li>I can use shorter url's that include only the filename for links between pages
in the same directory.</li>
<li>Filenames such as index.html can be re-used in different folders</li>
<li>When editing an element common to all pages within a given category I can use Dreamweaver's find and replace tool to replace all instances of the change within the folder at once.</li>
<li>The address of the page when posted to the server will reflect this structure thus offering a locational cue to users of the page.</li>
<li>Directories and subdirectories allow me to use shorter filenames because some of the description is implied in the directory name.</li>
</ul>

<h5>File naming conventions: simpler is better</h5>
<p>Descriptive filenames help you recognize what content the file contains and offer
clues to users who stumble upon a page via a search. However, overly descriptive
filenames create very long url's. To reduce url size without losing meaning I
recommend:
<ul>
<li><strong>Name the main page, in any given directory, index.html</strong>. This file name is the default on most Web servers including Case's main server. Some servers use default.html; when in doubt ask your server administrator. When you use index.html as your default page, the server recognizes this to be the main page of the directory and thus does not require you to type the file name at the end of the address. Instead of linking to a page called http://www.case.edu/events/ford/lecturehome.html, I could therefore link to the shorter <a href="http://www.case.edu/events/ford/">http://www.case.edu/events/ford/</a>.</li>
<li><strong>Abbreviate file and directory names.</strong> This can be done without losing meaning. Instead of naming a subdirectory <em>tools_of_the_trade</em> just call it <em>tools</em>.  Similarly http://www.case.edu/webdev/hactest/cartoon/resources/tools/print.html is long, yet far more manageable than http://www.case.edu/webdev/hactest/cartoon/resources/<br />tools_of_the_trade/techniquesofprinting.html.</li>
<li><strong>Don't use blank spaces in your file names.</strong> While most browsers will substitute %20 for the space, some browsers may not recognize these. Blank spaces can also cause links sent in e-mail programs to break, thus confusing the recipient.</li>
<li><strong>Most Web servers are case sensitive, so it helps to be consistent in your usage.</strong> I tend to use all lowercase names, however it is acceptable to use uppercase when referring to an acronym such as <a href="http://www.case.edu/provost/UCITE/">http://www.case.edu/provost/UCITE/</a>.</li>

</ul>
<p class="photoright"><img alt="files.jpg" src="http://blog.case.edu/webdev/2006/06/20/files.jpg" width="400" height="482" /></p>
<h5>Your local directory structure should mirror the directory structure on the Web server&mdash;but not completely</h5>

<p>When you create links between the pages on your site, the path to the links is predicated on the organization of your files and your directories. If you link to pages outside of your main directory, then these links won't work when you upload your site to the server. If you keep all of the files and directories for your site in one parent directory, you won't have this problem.</p>
<p>Although most of your directories and files will be the same on your local directory
as they are on the server, there are some exceptions.</p>
<p class="clear"> </p><ul>
<li>The Web server has no use for that rough draft of text you stored in a word file or the .psd (Photoshop) file of your masthead image. Upload the .html pages you built, images such as .gif's or .jpg's and other files required by your pages, but leave the extra files behind. You can save space on the server by not uploading any unnecessary files.</li>
<li>The Web server also relies on a few files or directories that you didn't create. Such directories may include bin, etc and usr. Leave these as they are on the server. </li>
</ul>
<p>As you've now realized, all of these suggestions are fairly simple and easy to implement. But as your site grows from 4 to 40 or perhaps even 400 pages, you'll find that a little bit of planning in the beginning will make the site easier to use and maintain over time. If you have additional tips and suggestions regarding ways to organize files, please share them below. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.heidicool.com/blog/2006/06/20/web-file-organization-and-naming-conventions/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Building your site: Tertiary pages&#8212;When more is more</title>
		<link>http://www.heidicool.com/blog/2006/04/17/content/</link>
		<comments>http://www.heidicool.com/blog/2006/04/17/content/#comments</comments>
		<pubDate>Tue, 18 Apr 2006 02:00:31 +0000</pubDate>
		<dc:creator>Heidi Cool</dc:creator>
				<category><![CDATA[Heidi's Entries]]></category>
		<category><![CDATA[Planning Your Website]]></category>
		<category><![CDATA[Writing]]></category>

		<guid isPermaLink="false">http://www.heidicool.com/blog/?p=41</guid>
		<description><![CDATA[In the Planning your Web site articles I wrote on first and secondary pages, I recommended not overwhelming the user with too many choices or too much information. That less is more approach works very well to ensure that critical information is not lost in a crowd of words, and helps us set up an [...]]]></description>
			<content:encoded><![CDATA[<p class="photoright"><img alt="pencil2.jpg" src="http://blog.case.edu/webdev/2006/04/17/pencil2.jpg" width="200" height="188" />
</p>
<p>In the <em><a href="http://blog.case.edu/webdev/2005/07/01/so_you_want_to_build_a_website">Planning your Web site</a></em> articles I wrote on <a href="http://blog.case.edu/webdev/2006/01/25/building_your_site_the_front_page">first</a> and <a href="http://blog.case.edu/webdev/2006/02/08/building_your_site_secondary_pages">secondary</a> pages, I recommended not overwhelming the user with too many choices or too much information. That <em>less is more</em> approach works very well to ensure that critical information is not lost in a crowd of words, and helps us set up an easy to maneuver navigational system. But as we get deeper into specific areas of the site, our goals and strategies change.</p>

<p>Once we have carefully guided our visitors to our third, fourth and deeper level pages, it is time to reward them with in-depth content that </p>
<ul>
<li>answers their questions</li>
<li>helps them make decisions</li>
<li>shares your knowledge and expertise</li>
<li>or otherwise helps them achieve the goals they had in visiting the site.</li>
</ul>

<p>At this point we don't need to worry about short-attention spans anymore than would a novelist. Our visitors have come this far to find out X, and we should supply them with the necessary information to understand X, whether that can be done in 2 paragraphs or 20 pages. A user with a goal will read through 20 pages if that is what it takes to achieve the goal. </p>

<p>For example, let us return to the fictional Department of Cartooning site. On this site I've created a tertiary page on <a href="http://www.case.edu/webdev/hactest/cartoon/resources/pencils.html">mechanical pencils</a>. It includes a few paragraphs about pencils, a photo and a list of additional resources. When planning this site I had decided to include an area of resources that would include information on tools of the trade as well as other references. One such tool is the pencil. It was my thought that visitors to the cartooning site might include
<ul>
<li>Potential students wanting to learn and practice with the tools before beginning their coursework</li>
<li>Professional cartoonists wanting to learn more about the tools and history of the craft</li>
<li>Skeptical users of wooden pencils</li>
<li>Drawing teachers</li>
<li>Art supply salesman, etc.</li>
</ul>
<p>With that in mind, I must now ask myself if <a href="http://www.case.edu/webdev/hactest/cartoon/resources/pencils.html">my
site</a> provided sufficient information to help these visitors achieve their goals. <strong>In
this case, I do not think that it has.</strong> While I've been fond of mechanical pencils ever since I was a toddler dissecting the ones I found on my father's desk&mdash;much to his dismay&mdash;I don't actually know that much about them. I also have no idea whether cartoonists prefer them or not. I do know a bit about line art and printing, but I could have elaborated more. Additionally I could have shared some history, and given users tips on matching the right pencil and lead to their projects. I did include links to additional resources, but I would have a better chance at satisfying my visitors if I took the time to do additional pencil research.</p>
<p>I use this example because I think an imperfect page helps to illustrate that feeling that users get when there goal hasn't been met. After navigating through the site, and finding the right page, they then discover that it doesn't fill all of their needs and they have to continue their quest somewhere else.</p>
<p>This happens to me quite often. Whether I'm searching for autoparts or the best apple kuchen recipe, I will get frustrated if I jump through all the hoops only to discover that something is missing&mdash;the recipe lists all of the ingredients, but doesn't tell me what size pan to use or how long to cook the kuchen.</p>
<p>Yet when the reverse is true, I am quite pleased. Two years ago my dryer stopped working. I determined that the problem was in the on switch because it wasn't clicking into position properly. I took off the cover so I could look at the part, compared that button to the others, wrote down the part number, then hopped online to visit the GE website. Given that product code numbers had changed since I'd first bought the dryer, it took some hunting, but over time I was able to narrow down my search and track down the part I needed. I was also able to confirm that it was the correct part because they included an illustration and a list of models that used this part. With credit card in hand, I ordered my part and it arrived in just a few days. It took me less than five minutes to install and I was able to dry my clothes without the expense of either a repairman or a new dryer.</p>

<p>Although it took me more time to find the part on their website, than it did to install it, I was happy to have gone through the process, because when I did find the part, it was what I needed and it saved me both time and money. I was happy, G.E. was happy for the sale, and perhaps they are happy now that I am recounting how happy I was to find my part on their Web site. When considering future appliance purchases I will probably consider G.E. again, because I know I can count on them in regard to their parts and equipment. In other words everybody won.</p>

<p>As was the case with me and G.E., when we help our visitors to achieve their goals, we help them to achieve our own goals as well. If you keep this in mind when creating your pages, I expect you will have similar success.
</p>

<p>p.s. Whether writing for the Web or for something else you may be interested in reading Mano Singham's  <a href="http://blog.case.edu/mxs24/2006/04/17/on_writing5_the_three_stages_of_writing">latest blog entry</a>. He offers some great insight into the process of writing.
]]></content:encoded>
			<wfw:commentRss>http://www.heidicool.com/blog/2006/04/17/content/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building your site: Secondary pages</title>
		<link>http://www.heidicool.com/blog/2006/02/08/secondarypages/</link>
		<comments>http://www.heidicool.com/blog/2006/02/08/secondarypages/#comments</comments>
		<pubDate>Thu, 09 Feb 2006 01:57:17 +0000</pubDate>
		<dc:creator>Heidi Cool</dc:creator>
				<category><![CDATA[Heidi's Entries]]></category>
		<category><![CDATA[Planning Your Website]]></category>

		<guid isPermaLink="false">http://www.heidicool.com/blog/?p=30</guid>
		<description><![CDATA[Now that you've created a welcoming front door, it's time to create your secondary pages. These pages can fall into two categories. On a small site made up of just a few pages, your secondary pages will hold your primary content. On a larger site, such as our Department of Cartooning site, the secondary page [...]]]></description>
			<content:encoded><![CDATA[<p class="photoright"><img src="http://blog.case.edu/webdev/2006/02/08/aboutus.jpg" alt="About Us" /> </p>

<p>Now that you've created a welcoming front door, it's time to create your secondary pages. These pages can fall into two categories. On a small site made up of just a few pages, your secondary pages will hold your primary content. On a larger site, such as our <a href="http://www.case.edu/webdev/hactest/cartoon/">Department
of Cartooning</a> site, the secondary page must both include useful content and serve as a gateway to the other pages in that section of the site.
</p>
<h5>Gateway to enlightenment </h5>
<p>When I describe a page as a gateway, I mean it to be a page through which a user can find all other pages in this sectional area. On this page you will see a menu on the left that clearly illustrates what information is available. You will also find content on this page that is descriptive of the topic at hand. As is true of the main page, this content tells users they've arrived in the right place and gives them additional information. </p>
<p>As an example, let's consider the "<a href="http://www.case.edu/webdev/hactest/cartoon/about/">About
Us</a>" page on the cartooning site. "About Us" is often
considered a catch-all sort of phrase, but it's a section
that belongs on most web sites. It contains the most basic
information that may be of interest to users, it explains
your mission, and offers information on how to contact you
to learn more. With that in mind, I wrote a few paragraphs
for this page that I felt best described the department and
it's mission.</p>
<p>Given that this department doesn't exist, I based this on what I imagined such a department would be at a university like Case. It wouldn't offer mere vocational training for aspiring cartoonists, but would draw on the scholarship of many departments to create a program that would give students a broad-based liberal learning experience. To give an overview of this I included the following types of information:</p>
<ul>
<li>Who might be interested in this department?</li>
<li>Which fields of study are included in the program?</li>
<li>What are some unique aspects of cartooning?</li>
<li>How do we address the challenges posed by this field?</li>
<li>What do our students do after graduation</li>
</ul>
<p>If you <a href="http://www.case.edu/webdev/hactest/cartoon/about/">read the page</a>, you'll notice that I didn't need to go into a lot of detail to address these questions. I just wanted to include enough information to serve my potential audience so they could understand what we do and why. As we've discussed before, this audience could include potential students, parents, professors, researchers, media, etc.</p>
<p>When deciding what to include I tried to imagine who would go to this page and what they would expect and need to find. In the real world, we would also rely on marketing research. I find it can also be helpful to test my content with a few "what if" scenarios.</p>
<ul>
<li>If I were a student trying to choose a major would this information entice me? Would I want to learn more? Would I consider majoring in cartooning?</li>
<li>If I were a student who's father had just screamed, "What sort of major is cartooning? How are you going to pay rent when you graduate?" would I be able to send him to this page? Would it sooth his mind and inspire him to learn more?</li>
<li>If I were a newspaper editor looking to hire a new editorial cartoonist, would this let me know that my applicant received the right training? </li>
<li>If I were a professor from another university looking for partners for a research study, would this page inspire confidence?</li>
</ul>
<p>I'm sure you can come up with numerous such examples for your own sites.</p>

<h5>Design Elements</h5>
<p>Secondary pages using the Case templates use the same banner and footer as the main page, a left hand sectional menu, and an open area for your main content. You have enormous flexibility in this area so long as you don't change the fonts and colors or include sloppy looking graphics.</p>
<p>For <a href="http://www.case.edu/webdev/hactest/cartoon/about/">this
page</a> I chose a simple layout with a small photo floating to the right. I used an illustration of the design studio with some locational information as it seemed fitting for the page, but I could also have considered photos of students or faculty, images of people drawing, etc. If this were a real page, I might have had a student or faculty member create a series of one square cartoons about the department that I could scatter throughout the site. These would both offer some visual interest and create a unifying theme.</p>
<p>For your own pages you could consider using a right-hand side bar such as the <a href="http://www.case.edu/development/annual/index.html">Annual
Fund</a> page, paragraphs with thumbnail photos such as the <a href="http://www.case.edu/visit/tours/">Campus
Tours</a> page, a combination of photos, text and tables as found on our <a href="http://www.case.edu/visit/weather.html">weather</a> page, or any number of other layout options.</p>
<p>However you choose to arrange your content on the page, just keep in mind that the content is appropriate to the page and that the page is easy-to-read and uncluttered. If do that you'll be well on your way. </p>
<p>Next time: Digging deeper into the site with tertiary pages</p>

<p><a href="http://www.heidicool.com/blog/2006/04/17/content/">Next >></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.heidicool.com/blog/2006/02/08/secondarypages/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Building your site: The Front Page</title>
		<link>http://www.heidicool.com/blog/2006/01/25/frontpage/</link>
		<comments>http://www.heidicool.com/blog/2006/01/25/frontpage/#comments</comments>
		<pubDate>Wed, 25 Jan 2006 23:29:02 +0000</pubDate>
		<dc:creator>Heidi Cool</dc:creator>
				<category><![CDATA[Heidi's Entries]]></category>
		<category><![CDATA[Planning Your Website]]></category>

		<guid isPermaLink="false">http://www.heidicool.com/blog/?p=29</guid>
		<description><![CDATA[In the last chapter of the tutorial we discussed content acquisition. Now that some time has passed, and we've gathered our content it is time to start building the page. For the purposes of this entry my focus will be to explain what content goes where. This will not be a detailed explanation of HTML [...]]]></description>
			<content:encoded><![CDATA[<p class="photoright"><a href="http://www.case.edu/webdev/hactest/cartoon/"><img alt="Screen Capture of Cartooning Site" src="http://blog.case.edu/webdev/2006/01/25/cartoon.jpg" width="300" height="359" /></a></p>
<p>In the last chapter of the tutorial we discussed content acquisition. Now that some time has passed, and we've gathered our content it is time to start building the page. For the purposes of this entry my focus will be to explain what content goes where. This will not be a detailed explanation of HTML and CSS. </p>

<p>The image on the right is a screen capture of the first page of our fictional <a href="http://www.case.edu/webdev/hactest/cartoon/">Department of Cartooning website</a>. As was decided when building the site map, I'm using an "Advanced Template" with a horizontal menu for this site. (Template files are available in the <a href="http://www.cwru.edu/webdev/webtoolkit/index.html">Web Toolkit</a>.) I've assigned a number to each section of the site, and will now use that to explain the various elements of the page. </p>

<h5>1: <a href="http://www.cwru.edu/webdev/webtoolkit/pagedesign/header.html">Top Navigation</a></h5>
<p>This section is meant to offer consistent navigation from every website at Case. It should not be edited.</p>
<h5>2: <a href="http://www.cwru.edu/webdev/webtoolkit/pagedesign/masthead.html">Masthead/Banner</a></h5>
<p>This area contains 3 primary elements, the logo, a background image, and the name of your site. In an Advanced Template this area is usually gray. In this case I used Turquoise as I felt cartooning would benefit from something more whimsical. </p>

<p>Each template comes with a background image, but if you have an image in mind that more aptly fits your site, then we can change that. 99% of the time this image should be a  photograph, but for the department of cartooning I felt an illustration would be better. I used a drawing of bears I'd made for an earlier project. If this were a real site I would have used something from the department. </p>

<p>The image used in this area is 422 x 108 pixels wide. It is created from a Photoshop file that incorporates a particular mask that both fades out the left side and applies uniform color to the image. If you would like a diffent image, you can create one by following the <a href="http://blog.case.edu/webdev/2006/05/26/customize_your_masthead_image">customize your masthead image</a> instructions.</p>

<p>The third element in this area is the site name. This need not be the name of your department. Here I've used "Department of Cartooning", but I could just has easily have chosen "Cartooning at Case." Simply pick a name that reflects your content. The name should appear in UPPERCASE letters and should remain constant for every page on your site.   </p>
<h5>3: Primary Navigation Menu</h5>
<p>This menu will appear on every page in your site. It will allow users to easily switch between sectional areas no matter what page they are viewing at a given moment. The links used in this menu are simply the section names you came up with when <a href="http://blog.case.edu/webdev/2005/08/25/organizing_acquiring_and_creating_content_for_your_website_part_one">building your site map</a>. Additionally this menu includes a link to your home page. </p>

<h5>4: Headline &amp; Image</h5>
<p>This area is meant to announce "who you are" and "what your mission is" to your audience. You could choose something as simple as "Welcome to Department X" or something more descriptive. This space should tell your audience that they've landed at the right place, the information you provide is just what they are seeking, and that your site is worth exploring. The photo on the right should reinforce this message or reflect the nature of your site. </p>

<p>The templates were built with certain sized images in mind, and you should size your photo to match. Then choose your text to fit the space. While this may seem backwards, it helps to ensure that you don't overload this area with too many words. If you really need to change the size of the photo to reflect different dimensions, then you may need to adjust your stylesheets as well. You should also view the page in multiple browsers. A photo that looks fine in Internet Explorer may move things around in Firefox or Mozilla. If you need assistance with this feel free to contact <a href="mailto:cool@case.edu">me</a> or <a href="mailto:kla3@case.edu">Kevin</a>. </p>
<h5>5: The Search Box</h5>
<p>This box allows users to search your site via Google. You will need to edit the code to match the address of your site. Maintainers of older sites will also need to ensure that they use the current Case convention rather than the former CWRU convention. <a href="http://www.case.edu/webdev/webtoolkit/search.html">Learn more</a>. </p>
<h5>6:Related Sites</h5>
<p>Just as it sounds, this box gives you a place to link to related sites. These may be other Case sites, or external sites. Try to pick the places that would give people additional information that supports the content on your site. If you have 50 related sites you should just pick the top few and create a links page for the rest. The use of double angle brackets to indicate a site external to your own is optional.  </p>

<p>In some cases you may find that you need an additional box. Perhaps you have multiple types of related sites. Or you have special content that you wish to feature more prominently. Feel free to do this so long as you maintain the same look and feel. <a href="http://pharmacology.case.edu/">Pharmacology</a> did this both by including an extra gray box for "Our People" and a navy box for "Apply Here." You'll note that aside from the color change the navy box otherwise maintains the same look and feel of the gray boxes. Another example can be found at <a href="http://www.case.edu/its">ITS</a>. </p>
<h5>7, 8, 9: Primary Content, New, Events, Announcements, etc.</h5>
<p>These elements make up your main content area, but this is also the area where you have the most flexibility. You may wish to use multiple announcement boxes, bring in a feed of headlines from your blog, describe your department, etc. <a href="http://www.cwru.edu/events/amm/">American Music Masters</a>, <a href="http://www.case.edu/univrel/marcomm/">Marketing &amp; Communications</a>, and <a href="http://www.case.edu/athletics/varsity/">Varsity Athletics</a> all provide examples of this. </p>

<p>Choose your content carefully. People often try to throw everything "important" on the main page, but if include too much you will find that your "important" items become lost in the crowd, competing with one another for attention. If you have a great event coming up, give them a brief headline with a link to more info. You can do the same with news and other announcements. Give them just enough of a taste to whet their appetite to learn more.</p>
<p>While the main page should be inviting and informative, keep in mind that it is just the front door. What you put on this page is the sign that invites users to open that door and come inside. Your job, is to select content that makes them open that door.</p>

<p>Next chapter: Interior pages</p>

<p><a href="http://www.heidicool.com/blog/2006/02/08/secondarypages/">Next >></a></p>

]]></content:encoded>
			<wfw:commentRss>http://www.heidicool.com/blog/2006/01/25/frontpage/feed/</wfw:commentRss>
		<slash:comments>42</slash:comments>
		</item>
		<item>
		<title>Organizing, acquiring, and creating content for your Web site &#8211; Part Two</title>
		<link>http://www.heidicool.com/blog/2005/08/25/organizing-2/</link>
		<comments>http://www.heidicool.com/blog/2005/08/25/organizing-2/#comments</comments>
		<pubDate>Thu, 25 Aug 2005 19:10:58 +0000</pubDate>
		<dc:creator>Heidi Cool</dc:creator>
				<category><![CDATA[Heidi's Entries]]></category>
		<category><![CDATA[Planning Your Website]]></category>

		<guid isPermaLink="false">http://www.heidicool.com/blog/?p=19</guid>
		<description><![CDATA[Clark Hall Now that we've reviewed and finalized our site map, it is time to start collecting and writing the content we need to build the site. Acquiring existing written content Some of the content you need probably exists already. For example we've decided to include course descriptions on our fictional cartooning site. These probably [...]]]></description>
			<content:encoded><![CDATA[<p class="photoright"><img alt="clark.jpg" src="http://blog.case.edu/webdev/2005/08/25/clark.jpg" width="200" height="167" /><br />Clark Hall</p>

<p>Now that we've reviewed and finalized our <a href="http://blog.case.edu/webdev/2005/08/25/cartooningmap.pdf">site map</a>, it is time to start collecting and writing the content we need to build the site.</p>

<h5>Acquiring existing written content</h5>
<p>Some of the content you need probably exists already. For example we've decided to include course descriptions on our fictional cartooning site. These probably already exist in the <a href="http://www.case.edu/bulletin/casegenbulletin04-06.pdf">General Bulletin</a>, so you could just go there and copy and paste from that document. On the other hand you may find that you want to include more details than are available in the bulletin. In this case I would send the blurbs from the bulletin to the professors teaching the classes and ask them to write a more detailed description for the site. Some may also want to include a syllabus, a link to their class blog, or a link to Blackboard.</p>


<p>Your faculty can also provide you with articles that they've published or other information on their research. Perhaps Professor Brown has written the definitive book on Superman. He may have existing content that you can incorporate into the Superman section. He and the other members of the faculty may also have existing webpages that you can link to rather than create from scratch.</p>

<h5>Writing new content</h5>
<p>Some of the content you've chosen may exist clearly in the heads of your faculty, staff or students but doesn't really exist anywhere else. Professor Van Pelt may give a lecture on pens in her beginning illustration class but all that exists on paper is an outline. You could have her write a page about this topic (if she has time available) or you could request writing assistance from <a href="http://www.case.edu/univrel/marcomm/">Marketing and Communications</a>.</p>

<p>Your department members will be a great resource, but many will have time limitations. If they don't have time to write what you need they may be willing to spend an hour with a writer who can interview them about their expertise and then write what you need for the topic.</p>

<p>Even if you find that everyone is able to contribute to the project, you will find that they have very different writing styles. In this case it would also be helpful to have a marketing writer review your content and edit it for consistency in style, flair and punctuation.</p>

<p>A writer can also help translate pages covering very technical topics into language that can be more easily understood by a lay person. This is important because not every visitor to your site will share the same level of expertise. While a colleague in Berlin may very well want to know every technical detail of your fuel cell research, a twelve-year-old girl in Waterville, Maine just wants to know more generally what they do and how they work because she is thinking of studying to become an engineer someday (perhaps here at Case).</p>

<p>If you think you need assistance with this part of the process, please feel free to <a href="http://www.cwru.edu/univrel/marcomm/creative/contact.html">request a writer</a> from our department.</p>

<h5>Photographs and Illustrations</h5>
<p>Photographs and illustrations add color and diversion to your site to help break up long chunks of copy. More imporantly they can serve to illustrate the point you are trying to make. As with written content, some photographs, such as the photo of Clark Hall, may already be available. I have thousands of images you may pilfer (for use on Case sites) both <a href="http://www.case.edu/development/alum/photos/archive.html">online</a> and sitting on my Mac (because I've not had time to post them all). Case's creative team also has a large collection of images on CD in Bellflower Hall. Your department probably has a number of its own images available, and in the Case of the Cartooning site your faculty  should be able to share their own cartoons. <a href="http://www.case.edu/its/archives/">University Archives</a> is also a great resource for photos as well as historical information about the university.</p>


<p>You will also probably discover that there are images you need that do not exist. If you have a good eye you may be able to shoot your own pictures. Or you can request shots to be taken by our campus photographer. If you are looking for an existing image or the services of our photographer, you may <a href="http://www.cwru.edu/univrel/marcomm/creative/contact.html">request those online</a> as well.</p>

<p>Next time: <em>Building the site</em></p>

<h5>Postscript</h5>
<p>When using existing content please make sure you have the proper permission from the holder of the copyright.</p>

<p><a href="http://www.heidicool.com/blog/2006/01/25/frontpage/">Next >></a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.heidicool.com/blog/2005/08/25/organizing-2/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Organizing, acquiring, and creating content for your Web site &#8211; Part One</title>
		<link>http://www.heidicool.com/blog/2005/08/25/organizing/</link>
		<comments>http://www.heidicool.com/blog/2005/08/25/organizing/#comments</comments>
		<pubDate>Thu, 25 Aug 2005 18:50:50 +0000</pubDate>
		<dc:creator>Heidi Cool</dc:creator>
				<category><![CDATA[Heidi's Entries]]></category>
		<category><![CDATA[Planning Your Website]]></category>

		<guid isPermaLink="false">http://www.heidicool.com/blog/?p=18</guid>
		<description><![CDATA[Having reviewed our goals and those of our audience, we should now be at the stage where we have a list of content ideas. Some of these we've come up with on our own and some have been suggested by our prospective site visitors. If you are like me you may have these items scrawled [...]]]></description>
			<content:encoded><![CDATA[<p class="photoright"><a href="http://blog.case.edu/webdev/2005/08/25/cartoonmap.jpg"><img alt="Small Cartoon Map" src="http://blog.case.edu/webdev/2005/08/25/cartoonmapsm.jpg" width="300" height="225" /></a></p>

<p>Having reviewed our goals and those of our audience, we should now be at the stage where we have a list of content ideas. Some of these we've come up with on our own and some have been suggested by our prospective site visitors.</p>

<p>If you are like me you may have these items scrawled out in no particular order on a legal pad, note cards, or the back of an unused airsickness bag. Now is the time to make sense of them.</p>

<h5>Organizing your content</h5>
<p>The first thing I try to do is arrange my items into logical clusters, then give names to the clusters. These names will become the items in the menu on our site.</p>


<p class="photoleft"><a href="http://blog.case.edu/webdev/2005/08/25/alumnimap.jpg"><img alt="alumnimapsm.jpg" src="http://blog.case.edu/webdev/2005/08/25/alumnimapsm.jpg" width="180" height="106" /></a></p>

<p>One way to do this would be to write each topic on a post-it note and put it on the wall. This way you can move things around as you see natural clusters forming. You could also do this with notecards on a bulletin board, or you could move them around in the computer program of your choice. Any technique will do so long as it makes sense to you.</p>

<p>Our objective in clumping these topics together is to build a map of our website. This can be illustrated as a flowchart as shown above,  or done in a simple outline.</p>

<p>Here on the <a href="http://blog.case.edu/webdev/2005/08/25/cartooningmap.pdf">Department of Cartooning Sitemap</a> you will see one possible way to arrange the content. Some categories have only a few items while others have so many that they can be broken up into sub categories. I've arranged them so the category names are both descriptive and fairly general. I want terms that will be understandable to a wide audience so that users won't have to stumble  blindly through the site in the hopes of finding something specific such as the page on pens and pencils. I'm hoping that resources will appear to be an obvious category for this topic and that they won't look first in About Us or Academics. Given that people process information differently there is no guarantee that this will make sense to each and every user, but my hope is that by using broad categories I can funnel the users through the broad terms on down to more specific items.</p>

<h5>Reviewing the sitemap</h5>
<p>Now that I've built my sitemap I have a clear picture in my head of where everything will go and what pages I will need to create. I can see by the structure of my site that <a href="http://www.case.edu/webdev/show/advanced/">Case's advanced template</a> will work well for the site because it allows for a primary horizontal menu as well as vertical submenus that can be used within each section.</p>

<p>My sitemap may also indicate changes that should be made. While looking at this map I've realized that I've not created a portfolio category to showcase the work of our students. I may be missing other things as well so at this point it is probably a good idea to share the map with others in your department who can help you finalize the map.</p>

<p>Once you and your team have agreed on the site map you can start acquiring your content. We'll discuss that in detail in Part Two.</p>

<a href="http://www.heidicool.com/blog/2005/08/25/organizing-2/">Next >></a>
]]></content:encoded>
			<wfw:commentRss>http://www.heidicool.com/blog/2005/08/25/organizing/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>More about your target audiences</title>
		<link>http://www.heidicool.com/blog/2005/07/28/audience/</link>
		<comments>http://www.heidicool.com/blog/2005/07/28/audience/#comments</comments>
		<pubDate>Thu, 28 Jul 2005 19:07:57 +0000</pubDate>
		<dc:creator>Heidi Cool</dc:creator>
				<category><![CDATA[Heidi's Entries]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[Planning Your Website]]></category>

		<guid isPermaLink="false">http://www.heidicool.com/blog/?p=17</guid>
		<description><![CDATA[Last week the subject of our target audiences received short shrift as I waxed forth on the subject of goals. In revisiting this subject I want to emphasize just how critical it is to find the balance between our own goals and those of the people we wish to visit the site. Sticking with the [...]]]></description>
			<content:encoded><![CDATA[<p class="photoright"><img alt="Push Me Pull You Cartoon" src="http://blog.case.edu/webdev/2005/07/28/pushme.jpg" width="246" height="400" /></p>

<p>Last week the subject of our target audiences received short shrift as I waxed forth on the subject of goals. In revisiting this subject I want to emphasize just how critical it is to find the balance between our own goals and those of the people we wish to visit the site.</p>

<p>Sticking with the cartoon theme I've used the example of Dr. Doolittle's "Pushme-Pullyou." One head represents the person producing the web content while the other represents the site visitor. In the movie this creature provided a navigational advantage when they were on board ship as it could see both in front and behind. It had a clear vision.</p>

<p>Yet if these heads did not work together, if one wanted to wander south to drink water, while the other wanted to go north to eat plantains, then they would simply trip over their own feet and not accomplish either goal.</p>

<p>As web producers, how can we best mesh these goals? First we must understand them. As we've already analyzed our own, let's think about those of our audience.</p>

<h5>Who is your audience?</h5>
<p>Keeping in mind the goals we determined last week, the audience for our Department of Cartooning could potentially include:</p>

<ul>
<li>Current Students, Staff &#038; Faculty</li>
<li>Prospective Students, Staff &#038; Faculty</li>
<li>Alumni</li>
<li>Corporations, Foundations, Government Agencies and other potential donors</li>
<li>Working cartoonists</li>
<li>Newspaper syndicates and other media outlets</li>
<li>Cartooning researchers and scholars<li>
<li>Art directors from publishing houses and advertising agencies</li>
<li>School children and their teachers</li>
<li>Writers and other visual artists</li>
<li>etc.</li></ul>

<h5>What content do they expect or hope to find on your site?</h5>
<p>In some cases this may be obvious. Current students probably want a list of professors and course descriptions. Alumni may want networking resources. For each audience you can probably come up with a list of resources they might desire. But to really understand what they want, the most direct approach is to ask them.</p>


<p>If you were the Behemoth Corporation you might do this by having your market research department conduct surveys and focus groups. If you work on campus you might contact our marketing department to see if they have any pertinent data available. Perhaps you could contact a professor at Weatherhead to see if you could get some students to help do your research as a class project.</p>

<p>However, if you don't need something this elaborate, you can also take the simple route. Just ask the people you know who fall into these categories. While you may not be collecting data from a statistically significant sampling, you will probably get some great new ideas coupled with an understanding of why some things are more important to them than others.</p>

<p>I'm working with a department now that has included two students on the web project team. Thus far we've benefited not only from their own ideas, but also by their connection to the rest of the community.  Within the past few weeks they've been able to gather information from 50% of the students in their program. As you can imagine this has been invaluably helpful. I'm sure you will find it so as well.</p>

<p>Please tune in again next week as we discuss how to create the content that will serve our goals.</p>

<a href="http://www.heidicool.com/blog/2005/08/25/organizing/">Next >></a>
]]></content:encoded>
			<wfw:commentRss>http://www.heidicool.com/blog/2005/07/28/audience/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Understanding your goals and your target audience</title>
		<link>http://www.heidicool.com/blog/2005/07/21/goals/</link>
		<comments>http://www.heidicool.com/blog/2005/07/21/goals/#comments</comments>
		<pubDate>Fri, 22 Jul 2005 00:49:18 +0000</pubDate>
		<dc:creator>Heidi Cool</dc:creator>
				<category><![CDATA[Heidi's Entries]]></category>
		<category><![CDATA[Planning Your Website]]></category>

		<guid isPermaLink="false">http://www.heidicool.com/blog/?p=16</guid>
		<description><![CDATA[At this point you should have a fairly clear idea of the goals for your site. But have you considered this: are your goals related to the goals of your intended audience? To examine this issue let's pretend we are building a new website for the fictitious Department of Cartooning. As we see in my [...]]]></description>
			<content:encoded><![CDATA[<p class="photoright"><img alt="comicguy.jpg" src="http://blog.case.edu/webdev/2005/07/21/comicguy.jpg" width="250" height="352" /></p>
<p>At this point you should have a fairly clear idea of the goals for your site. But have you considered this: are your goals related to the goals of your intended audience? To examine this issue let's pretend we are building a new website for the fictitious Department of Cartooning.</p>
<p>  As we see in my own feeble attempt at cartooning, our webmaster is pondering
    his goals. The first one, to recruit faculty and students is a goal common
    to academic departments. (How we create content to support such goals will
    be discussed in a later post) Here our target audience is pretty obvious:
    prospective students and faculty.</p>
<p>The second goal, to show off his own skills seems to smack of self-interest,
  but may in fact support the first goal. Who do students wish to learn from?
  Someone who has only theoretical knowledge of cartooning? Or someone who also
  happens to be a succcessful cartoonist? If I'm a potential student I'd love
  to learn from someone who has experience in the field, someone who can mentor
  me, and give me real world guidance for my career. Thus this goal serves both
  the purpose of our webmaster and serves to let his targeted audience know more
  about the quality of the faculty in the department. He can publish his cartoons
  (perhaps on his blog so that he can self-syndicate for more media exposure).
  If the newspapers then pick him up for syndication, he will enhance the reputation
  of the department while at the same time increasing its visibility in national
  media. Additionally prospective students and faculty have easy access to his
  work so that they can decide if they like his style and would want to work
  with him.</p>
<p>Our third goal pertains to the wonders of mechanical pencils. If our webmaster
  merely has some random fondness for pencils then I'd say leave it off the site.
  But what if the mechanical pencil is the preferred tool of the trade? What
  if there are specific drawing techniques that utilize this implement? Perhaps
  a section on drawing resources that points out the specific benefits and uses
  of mechanical pencils would be useful. If the site provides a comprehensive
  overview on the subject, then it is supplying valuable reference material to
  cartooning students not only at Case, but in the world at large. If this site
  becomes the place to learn about mechanical pencils, then more traffic is driven
  to the site and more people learn not only about pencils, but also of our cartooning
  program, and the university itself. Thus we are enhancing Case's reputation
  and visibility by providing a valuable resource.</p>
<p>Our fourth goal is also fairly silly. If he needs help developing his surfing
  superhero then maybe he should write about it on his personal blog. Or make
  it a class project. But then again perhaps he could launch a nationwide writing
  contest. Contestants would submit their entries to the website, he'd find a
  writer, and he'd also expose hundreds of aspiring comic book writers to the
  cartooning program at Case. Hmmmm.</p>
<p>What other goals has he forgotten? Who does this website serve? Aside from
  prospects, it will also serve current students, staff and faculty. What information
  should be provided to them? Office hours? Course descriptions? Resources for
  buying art supplies? History of the department? Event listings? All this and
  more. When developing the site, our webmaster should think about everything
  these people could possibly wish to know and determine of that what is practical
  to publish on the site.</p>
<p>Regarding our external markets, professional cartoonists, cartooning scholars,
  school children working on class projects, media, corporations, foundations,
  etc. what other resources might we provide that would be of use to them and
  supportive of our department's goals? If we provide resources on pencils, then
  should we provide resources on other topics? History of cartooning? The differences
  between political cartoons and sunday funnies? What would be of interest to
  researchers (From 3rd grade through postdoc) on this topic? What would be of
  interest to professional cartoonists? These are all things to consider. And
  as I've already written a rather lengthy missive, I'll leave you to do just
  that. Ponder everything that anyone could want from your site, consider the
  whys and wherefores and then refine your list of goals and target audiences.</p>


<a href="http://www.heidicool.com/blog/2005/07/28/audience/">Next >></a>
]]></content:encoded>
			<wfw:commentRss>http://www.heidicool.com/blog/2005/07/21/goals/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>So you want to build a Web site</title>
		<link>http://www.heidicool.com/blog/2005/07/01/website/</link>
		<comments>http://www.heidicool.com/blog/2005/07/01/website/#comments</comments>
		<pubDate>Fri, 01 Jul 2005 22:20:31 +0000</pubDate>
		<dc:creator>Heidi Cool</dc:creator>
				<category><![CDATA[Planning Your Website]]></category>
		<category><![CDATA[How-to]]></category>

		<guid isPermaLink="false">http://www.heidicool.com/blog/?p=14</guid>
		<description><![CDATA[This is the first in a series of entries on how to plan your website. Whether you are starting from scratch or rebuilding an existing site, I hope this will help you understand how with careful planning you can build a site that serves the needs of your target audience. Now that you've decided to [...]]]></description>
			<content:encoded><![CDATA[<p><em>This is the first in a series of entries on how to plan your website. Whether you are starting from scratch or rebuilding an existing site, I hope this will help you understand how with careful planning you can build a site that serves the needs of your target audience.</em></p>

<p>Now that you've decided to make a site, you are probably thinking about colors, html and menus, etc. But just as one doesn't hit the ball in one's first tennis lesson, one doesn't start a website by jumping into the code. </p>

<p>Instead, the first question you should ask yourself is: WHY? </p>
<p class="photoright"><a href="http://blog.case.edu/webdev/2005/07/01/shiloh1.jpg"><img alt="Shiloh was a very cute Rottweiler" title="Shiloh was a very cute Rottweiler" src="http://blog.case.edu/webdev/2005/07/01/shiloh2.jpg"  /></a></p>
<h5>Why do you need the site?</h5>
<p>Initial responses to this question often include things like:</p>
<ul>
<li>My boss said we need a site and she put me in charge because I'm good with computers.</li>
<li>I want to learn HTML.</li>

<li>I have 50 cute pictures of Rottweilers that I want to share with the world.</li>
</ul>
<p>While those may be true, they're not the real reason you need to build the site. The real reason involves your goals. (If your goal is to learn HTML, then pick a topic with which you are familiar, and pick your goals accordingly. I'd recommend something with a narrow focus such as the wonderful things you can do with capers as opposed to the history of nanotechnology.)</p>

<h5>What are your real goals?</h5>
<p>Here at Case I find that goals tend to involve the distribution of basic information, dissemination of knowledge, and a marketing call to action. </p>

<p>
<strong>Basic information</strong> usually includes the location of your office, hours you are available, a directory of staff and faculty in the department, phone numbers, e-mail addresses, etc. </p>

<p><strong>Dissemination of knowledge</strong> involves the sharing of more in-depth information. Examples would include a biography of Bertolt Brecht, a tutorial on the double helix, your grandmother's compendium of apple pie recipes, information on configuring your e-mail program, or  reviews of B Movies featuring creatures from other planets complete with cast lists, photos and the names of the costumers. </p>

<p><strong>Marketing</strong> (for our purposes) means a call to action. What do you want people to do as a result of visiting your website? Examples might be: </p>
<ul>
<li>Apply for admission to your program.</li>
<li>Attend events such as your gaming/pizzafest marathon.</li>
<li>Donate money to a memorial scholarship fund.</li>
<li>Read Chapters 12-15 before Tuesday's class.</li>
<li>Participate in your research project.</li>
</ul>

<p>Almost all of you will have one or more marketing goals. </p>

<p>So let's say you're the one with the 50 pictures of cute Rotties. What are your real reasons for building the site? Do you just want to share your photos with other Rottweiler fans? Do you want people to hire you to take pictures of their dogs? Do you want to educate the public about Rottweilers and dispel myths about their viciousness? Do you want to provide information about the care and training of Rottweilers so that their owners will treat them with the respect and affection they may need? All of the above? Something else? </p>

<p>Think carefully about this. When you have a clear idea of your goals we can go onto the next steps: Understanding your target audience and choosing the content you need to support your goals. </p>

<p>Happy July 4th!</p>

<a href="http://www.heidicool.com/blog/2005/07/21/goals/">Next &gt;&gt;</a>
]]></content:encoded>
			<wfw:commentRss>http://www.heidicool.com/blog/2005/07/01/website/feed/</wfw:commentRss>
		<slash:comments>76</slash:comments>
		</item>
	</channel>
</rss>

