<?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>Restaurant branding, marketing and other notes on various design topics &#187; web design</title>
	<atom:link href="http://blog.vigorbranding.com/tag/web-design/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.vigorbranding.com</link>
	<description>A restaurant branding blog done with Vigor™</description>
	<lastBuildDate>Wed, 08 Feb 2012 20:22:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Successful Restaurant Websites Pt 1 of 4: Visitor Wants, Visitor Gets</title>
		<link>http://blog.vigorbranding.com/2011/05/successful-restaurant-websites-pt-1-of-4-visitor-wants-visitor-gets/</link>
		<comments>http://blog.vigorbranding.com/2011/05/successful-restaurant-websites-pt-1-of-4-visitor-wants-visitor-gets/#comments</comments>
		<pubDate>Fri, 27 May 2011 09:20:59 +0000</pubDate>
		<dc:creator>Joseph Szala</dc:creator>
				<category><![CDATA[Unsolicited Thoughts]]></category>
		<category><![CDATA[restaurant user experience]]></category>
		<category><![CDATA[restaurant ux]]></category>
		<category><![CDATA[restaurant web design]]></category>
		<category><![CDATA[restaurant web development]]></category>
		<category><![CDATA[restaurant web ux]]></category>
		<category><![CDATA[restaurant website]]></category>
		<category><![CDATA[restaurant website design]]></category>
		<category><![CDATA[restaurant website development]]></category>
		<category><![CDATA[restaurant website user experience]]></category>
		<category><![CDATA[user experience]]></category>
		<category><![CDATA[ux]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[web development]]></category>
		<category><![CDATA[website design]]></category>
		<category><![CDATA[website development]]></category>

		<guid isPermaLink="false">http://blog.vigorbranding.com/?p=1855</guid>
		<description><![CDATA[A restaurant&#8217;s website isn&#8217;t unlike other websites in that it needs to serve a number of functions at the same time. There&#8217;s a collision of the User&#8217;s Wants, Brand Wants, and Functionality/Accessibility. Flash brings motion to pages and that motion/animation gets people pumped up. Sure, at first brush it&#8217;s great, but then you run into [...]]]></description>
			<content:encoded><![CDATA[<p>A restaurant&#8217;s website isn&#8217;t unlike other websites in that it needs to serve a number of functions at the same time. There&#8217;s a collision of the User&#8217;s Wants, Brand Wants, and Functionality/Accessibility.</p>
<p>Flash brings motion to pages and that motion/animation gets people pumped up. Sure, at first brush it&#8217;s great, but then you run into the problems of functionality and user wants. I&#8217;ll go into detail in another post, but for now, lets list what a user wants from your restaurant website.</p>
<p><a rel="attachment wp-att-1856" href="http://blog.vigorbranding.com/2011/05/successful-restaurant-websites-pt-1-of-4-visitor-wants-visitor-gets/restaurant-website-user-wants/"><img class="aligncenter size-full wp-image-1856" title="restaurant-website-user-wants" src="http://blog.vigorbranding.com/wp-content/uploads/2011/05/restaurant-website-user-wants.png" alt="" width="428" height="145" /></a></p>
<p><span id="more-1855"></span></p>
<p>1. What&#8217;s Cooking? Obviously, a first timer wants to know what&#8217;s on the menu. But that doesn&#8217;t mean you should have it plopped on a page as a PDF download. You need the menu on the actual page AND a PDF download. The menu on the page gets them the info right away. The PDF gives them a way to download it and print it for later. You need both.</p>
<p>2. What&#8217;s the Vibe? A first timer wants to know what the place looks like and what its vibe is like. Is it formal? Casual? Fun? Light? Manage expectations with photography of the locations and food, and also the design. A template website is going to look generic. A custom design will be tailored to deliver an expected vibe. That&#8217;s invaluable. This also plays into brand messaging.</p>
<p>3. Where are you? People want addresses and phone numbers. They want links to a map. Put these somewhere VERY obvious so people can find you quickly and easily.</p>
<p>4. What&#8217;s New? Is it fresh? Is the restaurant happening or did they put up a site and leave it at that. The site needs a news area. The site needs a way to feature new dishes and specials. Most importantly, the site needs updated frequently. This is prime reason for using a <a title="Restaurant Website CMS" href="http://www.vimcms.com" target="_blank">content management system tailored to restaurants like VIM.</a></p>
<p>4. Opportunities to Save. Now they want to see if they can save a little bit on their visit. They&#8217;ll look for ways on your site, on Twitter, Groupon, FourSquare and various other places. But why not just list them in one area? Put this info in one location for them to find and choose. Your goal with any discount program is to get them to visit then worry about increasing the ticket while they&#8217;re there.</p>
<p>5. Connect &amp; Contact. Finally, then want to connect to you. They want you to talk to them. Do this through Facebook, Twitter and email. Give them the means to ask you to reach out then make sure you actually reach out!</p>
<p>Your visitors/users come first. You have to deliver what they want and get it to them quickly or you&#8217;ll lose them every time. Make sure these 5 elements are present on your restaurant&#8217;s website and win.</p>
<p>What are features you like seeing on a restaurant&#8217;s site? What features do you hate?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.vigorbranding.com/2011/05/successful-restaurant-websites-pt-1-of-4-visitor-wants-visitor-gets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Vigor Launches Aroogas.com</title>
		<link>http://blog.vigorbranding.com/2009/08/vigor-launches-arooga-com/</link>
		<comments>http://blog.vigorbranding.com/2009/08/vigor-launches-arooga-com/#comments</comments>
		<pubDate>Mon, 31 Aug 2009 19:28:18 +0000</pubDate>
		<dc:creator>Joseph Szala</dc:creator>
				<category><![CDATA[Unsolicited Thoughts]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[new site]]></category>
		<category><![CDATA[restaurant website]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[website design]]></category>
		<category><![CDATA[websites]]></category>

		<guid isPermaLink="false">http://blog.vigorbranding.com/?p=204</guid>
		<description><![CDATA[After months of design and development we finally launched the website for central, PA&#8217;s sport bar gods, Aroogas! The site features a robust content management system, VIM, with modules spanning ecommerce, blog, events listings and so much more. Check out the site at www.aroogas.com]]></description>
			<content:encoded><![CDATA[<p>After months of design and development we finally launched the website for central, PA&#8217;s sport bar gods, Aroogas! The site features a robust content management system, <a href="http://www.vimcms.com" target="_blank">VIM</a>, with modules spanning ecommerce, blog, events listings and so much more.</p>
<p>Check out the site at <a href="http://www.aroogas.com" target="_blank">www.aroogas.com</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.vigorbranding.com/2009/08/vigor-launches-arooga-com/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Considerations for Content Management</title>
		<link>http://blog.vigorbranding.com/2009/06/considerations-for-content-management/</link>
		<comments>http://blog.vigorbranding.com/2009/06/considerations-for-content-management/#comments</comments>
		<pubDate>Mon, 01 Jun 2009 19:16:21 +0000</pubDate>
		<dc:creator>Joseph Szala</dc:creator>
				<category><![CDATA[Unsolicited Thoughts]]></category>
		<category><![CDATA[CMS]]></category>
		<category><![CDATA[content management system]]></category>
		<category><![CDATA[usability]]></category>
		<category><![CDATA[web design]]></category>
		<category><![CDATA[websites]]></category>

		<guid isPermaLink="false">http://blog.vigorbranding.com/?p=156</guid>
		<description><![CDATA[Website content management systems have grown from a luxury often used by only large corporations into a necessity that is borderling irresponsible NOT to have on a company&#8217;s website. Being able to manage one&#8217;s own content reduces the amount of money needed to keep information fresh and up-to-date. Fresh information spawns continued readership, repeat visitors, [...]]]></description>
			<content:encoded><![CDATA[<p>Website content management systems have grown from a luxury often used by only large corporations into a necessity that is borderling irresponsible NOT to have on a company&#8217;s website. Being able to manage one&#8217;s own content reduces the amount of money needed to keep information fresh and up-to-date. Fresh information spawns continued readership, repeat visitors, new vistors, higher search results and inevitably&#8230;new business.</p>
<p>Despite the need for content management, a lot of misconceptions have arisen over the years with regard to what can and cannot be done (not to mention how much it should cost.) So, we&#8217;ve decided to shed some light on the facts surrounding content management systems. Whether you are using an opensource God like WordPress, or using a proprietary system like Vigor&#8217;s VIM, the following hold true.<span id="more-156"></span></p>
<p><strong>1. The more you want to do, the more it will cost</strong></p>
<p>Things cost money and just because you want something doesn&#8217;t mean you get to have it for cheap. The more complex you imagine the capabilies of a CMS, the more it is going to cost to purchase, setup, integrate, support and use. There are no work arounds and no exceptions. Think of it as a car. Older cars were easier to work on because the system was pretty basic. Now there are electronics in the engine throughout the vehicle, A/C systems with coolant and a million other elements that make the car cost more to purchase and maintain.</p>
<p><strong>2. Flash is restricting</strong></p>
<p>Flash animations, blinking lights and moving pictures restricts your ability to update. Those animations are what they are so you won&#8217;t be able to edit that particular content without investing significant money to make it editable. Even then, it&#8217;s going to be tricky. Use Flash to add a little flair, but use it wisely. We&#8217;ve never heard of any brand making money because they animated their entire site. On the other side, companies have paid out more money because they had to hire outside consultants to update their site over and over again.</p>
<p><strong>3. You aren&#8217;t going to automatically understand the system</strong></p>
<p>No matter how hard engineers try to make things intuitive a content management system is a new piece of software, and it will take some learning time to use. You aren&#8217;t going to open it and automatically understand how everything works. Training is key and training does usually cost money. It&#8217;s worth it to take the time to understand how all the caveats of a CMS works.</p>
<p>A content management system is a MUST for every website out there. That is, of course, if that website is supposed to be successful.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.vigorbranding.com/2009/06/considerations-for-content-management/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>

