<?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"
	>

<channel>
	<title>Website Design and Development</title>
	<atom:link href="http://ak.kemplergroup.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://ak.kemplergroup.com</link>
	<description>Adam Kempler</description>
	<pubDate>Tue, 16 Dec 2008 18:54:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
	<language>en</language>
			<item>
		<title>Moving my blog</title>
		<link>http://ak.kemplergroup.com/2008/11/14/moving-my-blog/</link>
		<comments>http://ak.kemplergroup.com/2008/11/14/moving-my-blog/#comments</comments>
		<pubDate>Sat, 15 Nov 2008 02:24:12 +0000</pubDate>
		<dc:creator>Adam Kempler</dc:creator>
		
		<category><![CDATA[@play]]></category>

		<category><![CDATA[@work]]></category>

		<guid isPermaLink="false">http://ak.kemplergroup.com/?p=88</guid>
		<description><![CDATA[I&#8217;m moving my blog to http://adamkempler.com
Update your feeds. Sorry for the trouble.
]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m moving my blog to http://adamkempler.com<br />
Update your feeds. Sorry for the trouble.</p>
]]></content:encoded>
			<wfw:commentRss>http://ak.kemplergroup.com/2008/11/14/moving-my-blog/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Public versus private content - a recurring pattern</title>
		<link>http://ak.kemplergroup.com/2006/02/19/public-versus-private-content-a-recurring-pattern/</link>
		<comments>http://ak.kemplergroup.com/2006/02/19/public-versus-private-content-a-recurring-pattern/#comments</comments>
		<pubDate>Mon, 20 Feb 2006 02:08:19 +0000</pubDate>
		<dc:creator>Adam Kempler</dc:creator>
		
		<category><![CDATA[@work]]></category>

		<guid isPermaLink="false">http://ak.kemplergroup.com/2006/02/19/public-versus-private-content-a-recurring-pattern/</guid>
		<description><![CDATA[A recurring pattern I encounter frequently when developing community oriented sites is whether to make certain user-contributed content public or private. Often the end-user has the option of making their content public or private and the system defaults to one or other.
The client almost always votes for private as the default, but Ari Paparo tells [...]]]></description>
			<content:encoded><![CDATA[<p>A recurring pattern I encounter frequently when developing community oriented sites is whether to make certain user-contributed content public or private. Often the end-user has the option of making their content public or private and the system defaults to one or other.</p>
<p>The client almost always votes for private as the default, but Ari Paparo tells a cautionary tale in his post about <a href="http://www.aripaparo.com/archive/001456.html">why his bookmarking company Blink.com failed</a> and del.icio.us succeeded.</p>
<p>Ari lists multiple reasons, but the one I identify with as a web developer is the issue of public versus private content. This comes up time and again, and as Ari states, it&#8217;s not just the ability to make something private or public, but which should be the default. In his case, making &#8216;private&#8217; the default was a deciding factor in the failure of his site, whereas del.icio.us defaulted to &#8216;public&#8217; for the very same content (bookmarks).<br />
So the next time I&#8217;m <strike>wrestling</strike> discussing with a client whether or not user-generated content should be public or private I will refer them to Ari&#8217;s post.</p>
<p>[tags]Marketing, Patterns, Content, Content Management[/tags]<a rel="tag" href="http://technorati.com/tag/marketing%20patterns%20content%20contentmanagement%20content-management" /></p>
]]></content:encoded>
			<wfw:commentRss>http://ak.kemplergroup.com/2006/02/19/public-versus-private-content-a-recurring-pattern/feed/</wfw:commentRss>
		</item>
		<item>
		<title>A Subversion Repository for my wife</title>
		<link>http://ak.kemplergroup.com/2006/02/14/a-subversion-repository-for-my-wife/</link>
		<comments>http://ak.kemplergroup.com/2006/02/14/a-subversion-repository-for-my-wife/#comments</comments>
		<pubDate>Wed, 15 Feb 2006 00:13:33 +0000</pubDate>
		<dc:creator>Adam Kempler</dc:creator>
		
		<category><![CDATA[@play]]></category>

		<guid isPermaLink="false">http://ak.kemplergroup.com/2006/02/14/a-subversion-repository-for-my-wife/</guid>
		<description><![CDATA[My wife&#8217;s Valentine&#8217;s day gift is a subversion repository. She&#8217;s a writer and like many of the writers I know, rarely backs anything up, preferring to believe that the Great God of Writers will protect her and her work from harm. While I live in fear that the next time she has an &#8220;oops&#8221; with [...]]]></description>
			<content:encoded><![CDATA[<p>My wife&#8217;s Valentine&#8217;s day gift is a subversion repository. She&#8217;s a writer and like many of the writers I know, rarely backs anything up, preferring to believe that the Great God of Writers will protect her and her work from harm. While I live in fear that the next time she has an &#8220;oops&#8221; with her laptop, I won&#8217;t be able to rescue the files from her hard drive. (It&#8217;s been four times already).</p>
<p>So today I setup a subversion repository for her to store her manuscripts. I installed TortoiseSVN on her laptop so all she has to do is right-click on her Word file and select &#8220;commit&#8221;. She can even add comments about the her status if she wants.<br />
I also setup WebSVN so she has the added bonus of being able to access her manuscript from any computer via the browser.</p>
<p>Happy Valentine&#8217;s Day honey&#8230;</p>
<p><code>  [tags]subversion, svn, scm[/tags]</code></p>
]]></content:encoded>
			<wfw:commentRss>http://ak.kemplergroup.com/2006/02/14/a-subversion-repository-for-my-wife/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Website urls</title>
		<link>http://ak.kemplergroup.com/2006/01/31/website-urls/</link>
		<comments>http://ak.kemplergroup.com/2006/01/31/website-urls/#comments</comments>
		<pubDate>Tue, 31 Jan 2006 21:57:56 +0000</pubDate>
		<dc:creator>Adam Kempler</dc:creator>
		
		<category><![CDATA[@work]]></category>

		<guid isPermaLink="false">http://ak.kemplergroup.com/archives/53</guid>
		<description><![CDATA[I was setting up a new Wordpress blog and was trying to decide what format to use for my urls (permalinks). I opted for a format like:http://www.mysite.com/blog/archives/123I thought that this would be easier on the eyes than having the post title in the url:http://www.mysite.com/blog/archives/some-post-by-me
However, I was just found a post on the importance of a [...]]]></description>
			<content:encoded><![CDATA[<p>I was setting up a new Wordpress blog and was trying to decide what format to use for my urls (permalinks). I opted for a format like:<br /><span><code>http://www.mysite.com/blog/archives/123</code></span><br />I thought that this would be easier on the eyes than having the post title in the url:<br /><span><code>http://www.mysite.com/blog/archives/some-post-by-me</code></span></p>
<p>However, I was just found a post on <a href="http://ipears.com/2006/01/06/britney-spears/">the importance of a good post slug</a>. I really hadn&#8217;t thought about the importance of relevant content in the url for search engines and ad serving via Adsense.</p>
]]></content:encoded>
			<wfw:commentRss>http://ak.kemplergroup.com/2006/01/31/website-urls/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Project management best practices</title>
		<link>http://ak.kemplergroup.com/2006/01/22/project-management-best-practices/</link>
		<comments>http://ak.kemplergroup.com/2006/01/22/project-management-best-practices/#comments</comments>
		<pubDate>Sun, 22 Jan 2006 19:05:31 +0000</pubDate>
		<dc:creator>Adam Kempler</dc:creator>
		
		<category><![CDATA[@work]]></category>

		<guid isPermaLink="false">http://ak.kemplergroup.com/archives/52</guid>
		<description><![CDATA[I&#8217;ve usesd a lot of project management software and the key ingredient missing from all of them is a way to document and identify best practices for each of the projects. Clay Shirky says: The best way to learn something is when someone else figures it out and
tells you: &#8220;Don&#8217;t go in that swamp. There [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve usesd a lot of project management software and the key ingredient missing from all of them is a way to document and identify best practices for each of the projects. <a href="http://shirky.com/writings/group_enemy.html">Clay Shirky says</a>: The best way to learn something is when someone else figures it out and<br />
tells you: &#8220;Don&#8217;t go in that swamp. There are alligators in there.&#8221; </p>
<p>When starting a new project there are always lessons that were learned in previous projects that could be applied. However, these are usually relearned each time. Especially if there are different teams working on each of the projects. </p>
<p>I&#8217;ve always found doing a &#8220;Lessons Learned&#8221; after each project to be helpful in capturing some of the best practices. This can be a simple process involving just typing up some basic questions and answers such as:
<ul>
<li>Description of the project</li>
<li>What were three things that went wrong during the project and why did they go wrong?</li>
<li>How could they be prevented in the future?</li>
<li>What were three things that went right during the project and why?</li>
<li>How can they be replicated on future projects?</li>
</ul>
<p>It&#8217;s important to ask these questions both internally and with the client. Often what went wrong and what went right are very different based on who you ask.</p>
]]></content:encoded>
			<wfw:commentRss>http://ak.kemplergroup.com/2006/01/22/project-management-best-practices/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Idea Generation Methods</title>
		<link>http://ak.kemplergroup.com/2005/08/31/idea-generation-methods/</link>
		<comments>http://ak.kemplergroup.com/2005/08/31/idea-generation-methods/#comments</comments>
		<pubDate>Wed, 31 Aug 2005 20:36:29 +0000</pubDate>
		<dc:creator>Adam Kempler</dc:creator>
		
		<category><![CDATA[@work]]></category>

		<guid isPermaLink="false">http://ak.kemplergroup.com/archives/50</guid>
		<description><![CDATA[Martin Leith has an extensive list of idea generation methods at www.ideagenerationmethods.com. Each method links to a page with additional information. Looks pretty interesting. 
I think this site would benefit tremendously if it were in a Wiki format. Users could provide additional information on each of the methods such as examples of usage, case histories, [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.martinleith.com/">Martin Leith</a> has an extensive list of idea generation methods at <a href="http://www.ideagenerationmethods.com/">www.ideagenerationmethods.com</a>. Each method links to a page with additional information. Looks pretty interesting. </p>
<p>I think this site would benefit tremendously if it were in a Wiki format. Users could provide additional information on each of the methods such as examples of usage, case histories, and positive and negative feedback about each method. Additionally users would be able to add additional methods to the list.</p>
]]></content:encoded>
			<wfw:commentRss>http://ak.kemplergroup.com/2005/08/31/idea-generation-methods/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Sticky sites are now dirty</title>
		<link>http://ak.kemplergroup.com/2005/08/28/sticky-sites-are-now-dirty/</link>
		<comments>http://ak.kemplergroup.com/2005/08/28/sticky-sites-are-now-dirty/#comments</comments>
		<pubDate>Mon, 29 Aug 2005 00:51:34 +0000</pubDate>
		<dc:creator>Adam Kempler</dc:creator>
		
		<category><![CDATA[@work]]></category>

		<guid isPermaLink="false">http://ak.kemplergroup.com/?p=47</guid>
		<description><![CDATA[I caught this snippet on Robert Scoble&#8217;s blog and it made me stop and think. Scoble: I&#8217;ve seen this behavior before&#8230;
As a web developer and marketer building web sites for clients one of the golden rules had always been  &#8220;Make it sticky&#8221;. Content, functionality, and navigation were always designed to keep the user on [...]]]></description>
			<content:encoded><![CDATA[<p>I caught this snippet on Robert Scoble&#8217;s blog and it made me stop and think. <a href="http://radio.weblogs.com/0001011/2005/08/27.html#a10975">Scoble: I&#8217;ve seen this behavior before&#8230;</a></p>
<p>As a web developer and marketer building web sites for clients one of the golden rules had always been  &#8220;Make it sticky&#8221;. Content, functionality, and navigation were always designed to keep the user on the site for as long as possible.</p>
<p>This brings up a good point which is another golden rule that I&#8217;d forgotten - Sometimes the rules change! New technologies lead to new user mindsets which ultimately change the way users expect to interact with an online presence.</p>
<p>I think all of us web developers should put our &#8220;golden&#8221; rules up on the wall each time we develop a web site and ask ourselves if any of those rules have changed. I know I will for now on.</p>
]]></content:encoded>
			<wfw:commentRss>http://ak.kemplergroup.com/2005/08/28/sticky-sites-are-now-dirty/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Don&#8217;t forget these steps:</title>
		<link>http://ak.kemplergroup.com/2005/08/27/this-is-going-to-be-big-10-steps-to-a-hugely-successful-web-20-company/</link>
		<comments>http://ak.kemplergroup.com/2005/08/27/this-is-going-to-be-big-10-steps-to-a-hugely-successful-web-20-company/#comments</comments>
		<pubDate>Sat, 27 Aug 2005 21:36:46 +0000</pubDate>
		<dc:creator>Adam Kempler</dc:creator>
		
		<category><![CDATA[@work]]></category>

		<guid isPermaLink="false">http://ak.kemplergroup.com/archives/46</guid>
		<description><![CDATA[10 Steps to a Hugely Successful Web 2.0 Company is a nice reminder of some important points to keep in mind when developing and running a Web company.
#10 made me go back and revisit all the competition for my own soon to be released product. I fell prey to too easily dismissing many of the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.thisisgoingtobebig.com/2005/08/10_steps_to_a_h.html">10 Steps to a Hugely Successful Web 2.0 Company</a> is a nice reminder of some important points to keep in mind when developing and running a Web company.</p>
<p>#10 made me go back and revisit all the competition for my own soon to be released product. I fell prey to too easily dismissing many of the competitive sites as &#8220;no competition.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://ak.kemplergroup.com/2005/08/27/this-is-going-to-be-big-10-steps-to-a-hugely-successful-web-20-company/feed/</wfw:commentRss>
		</item>
		<item>
		<title>SightSpeed Gets It</title>
		<link>http://ak.kemplergroup.com/2005/08/25/sightspeed-gets-it/</link>
		<comments>http://ak.kemplergroup.com/2005/08/25/sightspeed-gets-it/#comments</comments>
		<pubDate>Thu, 25 Aug 2005 15:59:01 +0000</pubDate>
		<dc:creator>Adam Kempler</dc:creator>
		
		<category><![CDATA[@work]]></category>

		<guid isPermaLink="false">http://ak.kemplergroup.com/?p=44</guid>
		<description><![CDATA[I&#8217;ve been seeing a lot of posts lately about how some big name companies just don&#8217;t get blogging and bloggers. Companies such as Dell and Apple have had their share of grief at the hands of bloggers. 
Yesterday I came across a company that does get it. I blogged about Google Talk and mentioned that [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been seeing a lot of posts lately about how some big name companies just don&#8217;t get blogging and bloggers. Companies such as Dell and Apple have had their share of grief at the hands of bloggers. </p>
<p>Yesterday I came across a company that does get it. I blogged about Google Talk and mentioned that I also was trying other messaging and communication software including SightSpeed. Within an hour, someone from SightSpeed had commented on my post and offered to set me up with an account to give it a try. </p>
<p>This is amazing. I was truly floored. This shows the power, immediacy, and viral capabilities of blogging from a marketing standpoint that most companies are missing out on. </p>
<p>If SightSpeed had just sent me an email saying, hey try out our new software, I would have instantly deleted it. I wouldn&#8217;t have seen it, and neither would anyone else. </p>
<p>But when someone blogs about a product, service or company, they are in some ways, extending an invitation to that company to respond. Now the company has been invited to talk to the user, and their discussion (and marketing message) takes place in front of everyone that reads that post.</p>
<p>I&#8217;ve been working with the marketing departments of companies for a long time and this is something that I will be using as an example of &#8220;what to do&#8221; with all my clients. So many companies don&#8217;t even monitor what is being said about them in the blogosphere. Here it is proactively being taken a step further. </p>
<p>I&#8217;m going to install the new version of SightSpeed today and I&#8217;ll post about my experiences with it here.</p>
]]></content:encoded>
			<wfw:commentRss>http://ak.kemplergroup.com/2005/08/25/sightspeed-gets-it/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The problem with wikis</title>
		<link>http://ak.kemplergroup.com/2004/08/15/the-problem-with-wikis/</link>
		<comments>http://ak.kemplergroup.com/2004/08/15/the-problem-with-wikis/#comments</comments>
		<pubDate>Sun, 15 Aug 2004 10:00:00 +0000</pubDate>
		<dc:creator>Adam Kempler</dc:creator>
		
		<category><![CDATA[@work]]></category>

		<guid isPermaLink="false">/?p=34</guid>
		<description><![CDATA[Getting ready for my move, I decided to setup a web-based tool to document information and links. The tool will be maintained by my wife and myself. I went through my usual brain spasms - what technology should I use - Wiki, Blog, or some other CMS tool. If it was just me using the [...]]]></description>
			<content:encoded><![CDATA[<p>Getting ready for my move, I decided to setup a web-based tool to document information and links. The tool will be maintained by my wife and myself. I went through my usual brain spasms - what technology should I use - Wiki, Blog, or some other CMS tool. If it was just me using the system I would have immediately chosen a Wiki, however, since Mel would be updating it too, it needed to be simple, and here I believe is where Wikis fail at being a mainstream application. <strong>One</strong> - They require the learning of an awkward sytax which may be fairly simple for a technically minded person to use but even I find it annoying. Two - It requires everything you do to be in the mindset of EDITING rather than ADDING. This is key. What I like about blogs is that when I add a post I am really adding it, not editing existing content to add it as is done with a wiki.</p>
]]></content:encoded>
			<wfw:commentRss>http://ak.kemplergroup.com/2004/08/15/the-problem-with-wikis/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
