<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Redesigning the frontpage step 2</title>
	<link>http://devblog.motigo.com/2007/06/04/redesigning-the-frontpage-step-2/</link>
	<description>motigo motigo motigo</description>
	<pubDate>Thu, 28 Aug 2008 19:27:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>By: Rocha</title>
		<link>http://devblog.motigo.com/2007/06/04/redesigning-the-frontpage-step-2/#comment-174</link>
		<author>Rocha</author>
		<pubDate>Fri, 29 Jun 2007 14:17:52 +0000</pubDate>
		<guid>http://devblog.motigo.com/2007/06/04/redesigning-the-frontpage-step-2/#comment-174</guid>
		<description>Overall, I like the new look of the page after logging in: it provides easy access to all services.

  There is one thing I don't like about it though: 
  I use many different counters.
  It is now necessary to click on each of them individually to track the number of visits to each of my websites.
  Could a summary of number of visits (say # visits in last 24h) be posted up-front?
  Being able to choose which summary is shown would be a plus.</description>
		<content:encoded><![CDATA[<p>Overall, I like the new look of the page after logging in: it provides easy access to all services.</p>
<p>  There is one thing I don&#8217;t like about it though:<br />
  I use many different counters.<br />
  It is now necessary to click on each of them individually to track the number of visits to each of my websites.<br />
  Could a summary of number of visits (say # visits in last 24h) be posted up-front?<br />
  Being able to choose which summary is shown would be a plus.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Motigo developer blog</title>
		<link>http://devblog.motigo.com/2007/06/04/redesigning-the-frontpage-step-2/#comment-124</link>
		<author>Motigo developer blog</author>
		<pubDate>Fri, 15 Jun 2007 09:11:59 +0000</pubDate>
		<guid>http://devblog.motigo.com/2007/06/04/redesigning-the-frontpage-step-2/#comment-124</guid>
		<description>[...]  Redesigning the frontpage step 2 [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;]  Redesigning the frontpage step 2 [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Corien</title>
		<link>http://devblog.motigo.com/2007/06/04/redesigning-the-frontpage-step-2/#comment-123</link>
		<author>Corien</author>
		<pubDate>Fri, 15 Jun 2007 09:05:55 +0000</pubDate>
		<guid>http://devblog.motigo.com/2007/06/04/redesigning-the-frontpage-step-2/#comment-123</guid>
		<description>Definitive improvement - the instant "list" of stats/forum/guestbook/shorturl" after logging in. 
New layout also got rid of the spelling mistakes on the front page (Dutch version) .</description>
		<content:encoded><![CDATA[<p>Definitive improvement - the instant &#8220;list&#8221; of stats/forum/guestbook/shorturl&#8221; after logging in.<br />
New layout also got rid of the spelling mistakes on the front page (Dutch version) .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ekendra Lamsal</title>
		<link>http://devblog.motigo.com/2007/06/04/redesigning-the-frontpage-step-2/#comment-104</link>
		<author>Ekendra Lamsal</author>
		<pubDate>Sat, 09 Jun 2007 07:12:06 +0000</pubDate>
		<guid>http://devblog.motigo.com/2007/06/04/redesigning-the-frontpage-step-2/#comment-104</guid>
		<description>I find the language chooser button uncomfort. The fronthead bar in the frontpage is not as attractive as the bottom header that contains link.
I have been using your services for a while, it has proven the best. Still you can make the best of the BEST. 
Regards.</description>
		<content:encoded><![CDATA[<p>I find the language chooser button uncomfort. The fronthead bar in the frontpage is not as attractive as the bottom header that contains link.<br />
I have been using your services for a while, it has proven the best. Still you can make the best of the BEST.<br />
Regards.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
