<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for The SharePoint Muse</title>
	<atom:link href="http://www.thesharepointmuse.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thesharepointmuse.com</link>
	<description>Marcy Kellar&#039;s Blog on SharePoint Branding, User Experience and Web Content Management</description>
	<lastBuildDate>Sun, 19 Feb 2012 07:37:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<meta xmlns="http://www.w3.org/1999/xhtml" name="robots" content="noindex,follow" />
	<item>
		<title>Comment on Lesson Learned: When To Use Publishing in SharePoint by Getting Started: SEO for SharePoint &#171; T3chnicalLead</title>
		<link>http://www.thesharepointmuse.com/2011/12/lesson-learned-when-you-need-to-use-publishing-in-sharepoint/comment-page-1/#comment-1577</link>
		<dc:creator>Getting Started: SEO for SharePoint &#171; T3chnicalLead</dc:creator>
		<pubDate>Sun, 19 Feb 2012 07:37:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesharepointmuse.com/?p=1236#comment-1577</guid>
		<description>[...] http://www.thesharepointmuse.com/2011/12/lesson-learned-when-you-need-to-use-publishing-in-sharepoin... – Marcy Keller [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.thesharepointmuse.com/2011/12/lesson-learned-when-you-need-to-use-publishing-in-sharepoin.." rel="nofollow">http://www.thesharepointmuse.com/2011/12/lesson-learned-when-you-need-to-use-publishing-in-sharepoin..</a>. – Marcy Keller [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lesson Learned: Using Fixed-Width Layouts in SharePoint by Tom Daly</title>
		<link>http://www.thesharepointmuse.com/2012/02/lesson-learned-using-fixed-width-layouts-in-sharepoint/comment-page-1/#comment-1532</link>
		<dc:creator>Tom Daly</dc:creator>
		<pubDate>Mon, 13 Feb 2012 18:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesharepointmuse.com/?p=916#comment-1532</guid>
		<description>Great post, I agree with maintaining liquid layouts on the more &#039;collaborative&#039; pages. I cringe internally when the clients ask otherwise.. because I know that once its all done they are going to complain once a user adds a list view webpart with 20+ columns and it doesn&#039;t fit.

Generally most of the publishing type sites I do are fixed width, but more consideration and guidlines go into populating those pages.</description>
		<content:encoded><![CDATA[<p>Great post, I agree with maintaining liquid layouts on the more &#8216;collaborative&#8217; pages. I cringe internally when the clients ask otherwise.. because I know that once its all done they are going to complain once a user adds a list view webpart with 20+ columns and it doesn&#8217;t fit.</p>
<p>Generally most of the publishing type sites I do are fixed width, but more consideration and guidlines go into populating those pages.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lesson Learned: Using Fixed-Width Layouts in SharePoint by Tom</title>
		<link>http://www.thesharepointmuse.com/2012/02/lesson-learned-using-fixed-width-layouts-in-sharepoint/comment-page-1/#comment-1531</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Mon, 13 Feb 2012 16:33:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesharepointmuse.com/?p=916#comment-1531</guid>
		<description>I like how you wrote this up and used lots of visuals. Generally, I agree with your recommendations, too.
The webstyleguide link is one of those cases of &quot;do what I say, not what I do&quot;, though. While the author suggests that most websites fall into the trap of presenting lines that are too long, the page the comment is made on is fluid. On my current browser width, the lines of text are much longer than the author&#039;s suggestion!</description>
		<content:encoded><![CDATA[<p>I like how you wrote this up and used lots of visuals. Generally, I agree with your recommendations, too.<br />
The webstyleguide link is one of those cases of &#8220;do what I say, not what I do&#8221;, though. While the author suggests that most websites fall into the trap of presenting lines that are too long, the page the comment is made on is fluid. On my current browser width, the lines of text are much longer than the author&#8217;s suggestion!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lesson Learned: Using Fixed-Width Layouts in SharePoint by Chris</title>
		<link>http://www.thesharepointmuse.com/2012/02/lesson-learned-using-fixed-width-layouts-in-sharepoint/comment-page-1/#comment-1530</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Mon, 13 Feb 2012 14:55:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesharepointmuse.com/?p=916#comment-1530</guid>
		<description>I agree that collaboration sites are not a good candidate for fixed width. Generally, the fluid layouts work better for primarily collaborative environments, which is why I think MSFT went that route.

For the vast majority of intranets I see, unless there&#039;s almost exclusively WCM happening, I suggest retaining the fluid layout.</description>
		<content:encoded><![CDATA[<p>I agree that collaboration sites are not a good candidate for fixed width. Generally, the fluid layouts work better for primarily collaborative environments, which is why I think MSFT went that route.</p>
<p>For the vast majority of intranets I see, unless there&#8217;s almost exclusively WCM happening, I suggest retaining the fluid layout.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lesson Learned: Using Fixed-Width Layouts in SharePoint by Nico de Jong</title>
		<link>http://www.thesharepointmuse.com/2012/02/lesson-learned-using-fixed-width-layouts-in-sharepoint/comment-page-1/#comment-1529</link>
		<dc:creator>Nico de Jong</dc:creator>
		<pubDate>Mon, 13 Feb 2012 14:22:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesharepointmuse.com/?p=916#comment-1529</guid>
		<description>Marcy,

I partly agree. Look and feel is also of great importance in team sites. Most of the users I work with spend about 30% on the content and 70% of their time on the look and feel - they want it too look like a website that their collaborators would like to use and thus they would do what is intended, collaboration - Often forgetting the real skills and agreements you need to get a group of people collaborating online.

I wanted to use fix width for my team sites. Especially because I believe your 85% resolution is also true for us ... To make it more future proof though I am thinking of using left and right padding instead .. a 15px padding - I think - would help for readability. I personally also dont like words touching the edge of the screen ..

What is your opinion?</description>
		<content:encoded><![CDATA[<p>Marcy,</p>
<p>I partly agree. Look and feel is also of great importance in team sites. Most of the users I work with spend about 30% on the content and 70% of their time on the look and feel &#8211; they want it too look like a website that their collaborators would like to use and thus they would do what is intended, collaboration &#8211; Often forgetting the real skills and agreements you need to get a group of people collaborating online.</p>
<p>I wanted to use fix width for my team sites. Especially because I believe your 85% resolution is also true for us &#8230; To make it more future proof though I am thinking of using left and right padding instead .. a 15px padding &#8211; I think &#8211; would help for readability. I personally also dont like words touching the edge of the screen ..</p>
<p>What is your opinion?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SharePoint Branding Tip: Dropdown Selector Arrow Not Inline with .ms-listviewtable Row by Emmanuel Baron</title>
		<link>http://www.thesharepointmuse.com/2012/01/sharepoint-branding-tip-dropdown-selector-arrow-not-inline-with-ms-listviewtable-row/comment-page-1/#comment-1523</link>
		<dc:creator>Emmanuel Baron</dc:creator>
		<pubDate>Wed, 08 Feb 2012 02:50:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesharepointmuse.com/?p=1542#comment-1523</guid>
		<description>Hi Marcy, and tks for your very useful blog !

Just one point: if your using IE7 and depending where is your welcome menu control (for me it was just above the top navigation bar - not in the ribbon), this can be a problem. 

Indeed the drop down menu of this control may be visible below the content (breadcrumb, title etc) if your adding a position:relative property to CSS selector .s4-ca</description>
		<content:encoded><![CDATA[<p>Hi Marcy, and tks for your very useful blog !</p>
<p>Just one point: if your using IE7 and depending where is your welcome menu control (for me it was just above the top navigation bar &#8211; not in the ribbon), this can be a problem. </p>
<p>Indeed the drop down menu of this control may be visible below the content (breadcrumb, title etc) if your adding a position:relative property to CSS selector .s4-ca</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SharePoint 2010 Branding and Customization Resources by Imran Aziz</title>
		<link>http://www.thesharepointmuse.com/2010/05/sharepoint-2010-customization-resources/comment-page-1/#comment-1522</link>
		<dc:creator>Imran Aziz</dc:creator>
		<pubDate>Thu, 02 Feb 2012 12:38:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesharepointmuse.com/?p=350#comment-1522</guid>
		<description>Wonderful, thank you very much for sharing such wealth of resources. It was very helpful to me to find some guidelines of SharePoint Navigation that I was looking for.</description>
		<content:encoded><![CDATA[<p>Wonderful, thank you very much for sharing such wealth of resources. It was very helpful to me to find some guidelines of SharePoint Navigation that I was looking for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Usability Issues in SharePoint 2010 My Sites: Social Design Patterns and Standards by Wes Hackett</title>
		<link>http://www.thesharepointmuse.com/2011/09/usability-issues-in-sharepoint-2010-my-sites-social-design-patterns-and-standards/comment-page-1/#comment-1521</link>
		<dc:creator>Wes Hackett</dc:creator>
		<pubDate>Wed, 01 Feb 2012 21:58:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesharepointmuse.com/?p=656#comment-1521</guid>
		<description>Really interesting article Marcy. An example of my MySite customisation can be seen on slides 12/13 of this SPSUK slide deck http://www.slideshare.net/weshackett/share-point-saturday-putting-you-at-the-centre-of-the-intranet I would be interested on your thoughts about it in relation to this research. The screen grab is missing the &#039;status update&#039; as this came recently into production.

Cheers,

Wes</description>
		<content:encoded><![CDATA[<p>Really interesting article Marcy. An example of my MySite customisation can be seen on slides 12/13 of this SPSUK slide deck <a href="http://www.slideshare.net/weshackett/share-point-saturday-putting-you-at-the-centre-of-the-intranet" rel="nofollow">http://www.slideshare.net/weshackett/share-point-saturday-putting-you-at-the-centre-of-the-intranet</a> I would be interested on your thoughts about it in relation to this research. The screen grab is missing the &#8216;status update&#8217; as this came recently into production.</p>
<p>Cheers,</p>
<p>Wes</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Overview of Usability Issues in SharePoint 2010 My Sites by John Liu</title>
		<link>http://www.thesharepointmuse.com/2011/08/overview-of-usability-issues-in-sharepoint-2010-my-sites/comment-page-1/#comment-1351</link>
		<dc:creator>John Liu</dc:creator>
		<pubDate>Tue, 10 Jan 2012 05:44:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesharepointmuse.com/?p=526#comment-1351</guid>
		<description>I love the usability tests and the score card for 2010 My Sites!  (And thanks for the link!)

Being mostly a developer, I&#039;m convinced that a _cheap_ way to go about fixing a lot of the UX problems with out of the box My Sites is to put the whole thing into a modalDialog.</description>
		<content:encoded><![CDATA[<p>I love the usability tests and the score card for 2010 My Sites!  (And thanks for the link!)</p>
<p>Being mostly a developer, I&#8217;m convinced that a _cheap_ way to go about fixing a lot of the UX problems with out of the box My Sites is to put the whole thing into a modalDialog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Lesson Learned: When To Use Publishing in SharePoint by Fpweb.net Hosted SharePoint</title>
		<link>http://www.thesharepointmuse.com/2011/12/lesson-learned-when-you-need-to-use-publishing-in-sharepoint/comment-page-1/#comment-1210</link>
		<dc:creator>Fpweb.net Hosted SharePoint</dc:creator>
		<pubDate>Wed, 21 Dec 2011 20:09:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.thesharepointmuse.com/?p=1236#comment-1210</guid>
		<description>Hi Marcy. Thanks for posting. You&#039;ve provided a very good, succinct explanation of SharePoint Publishing (like, couldn&#039;t Microsoft just have called it &quot;web content management&quot; to begin with?)

Your chart distinguishing which types of content should be implemented in Publishing mode is also very helpful. Perhaps one of the most important distinctions in your Cheat Sheet is the audience &#039;scope&#039; criteria: always use Publishing when the content will be public-facing. Also, thanks for annotating your table with the differences between SharePoint 2007 and SharePoint 2010 versions.</description>
		<content:encoded><![CDATA[<p>Hi Marcy. Thanks for posting. You&#8217;ve provided a very good, succinct explanation of SharePoint Publishing (like, couldn&#8217;t Microsoft just have called it &#8220;web content management&#8221; to begin with?)</p>
<p>Your chart distinguishing which types of content should be implemented in Publishing mode is also very helpful. Perhaps one of the most important distinctions in your Cheat Sheet is the audience &#8216;scope&#8217; criteria: always use Publishing when the content will be public-facing. Also, thanks for annotating your table with the differences between SharePoint 2007 and SharePoint 2010 versions.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

