Something I definitely miss which is not difficult to implement at all is a site logo. I want to have a logo displayed to the left (or maybe right justified) of the Site Name/Heading. Currently it only supports text by means of some kind of custom control named SiteTitle.

If I edit the layout.Master page to add a logo to the left then it gets displayed outside the heading area, ideally it would be a property of SiteTitle to also set an optional logo image.

That would really be fantastic because just adding it to the left of <portal:SiteTitle ...> does not work around the lack of logo support.

Hey thanks half a million Kevin, that is indeed good information. I was trying with simple HTML but it was not showing the image for reasons unknown to me. I also have caching problems, even when I clear the cache and restart the app I don't see my changes until some strange condition ocurrs and then suddently they are there.

Anyway, I followed the instructions (pity about all this secret settings) but the logo does not properly integrate into the site heading (see http://www.coralys.com/). I placed it just before the <portal:SiteTitle> control but that does not render well. I may need to hack it with a custom style for margins but that is not what I would like to do. That is why I think the image should be a property of SiteTitle.

thanks 4 the cache info, will look into that...

As for the site logo I really don't see what is so difficult about it as I have done that in the past. Obviously we cannot expect any arbitrary image to fit there but that is exactly why one imposes constraints such as:

• If SiteTitle.Image property is not set no logo is displayed, otherwise it is
• Image is restricted to a size of (X,Y) pixels which is a constraint of the site heading.

The site title is just an enlarged text string and something like this could be done:

    <div class="xxx"><img src="~/.../logos/sitelogo.gif" align="left" /><span class="...">SITE TITLE</span></div>

Anyway something along those lines, it is very common to display images inline with text. Obviously some cssClass attributes would be applied to these items. It is very flexible and provided the user follows the restrictions of image size everything would be OK. Otherwise users have to hack up the layout.Master (which is not really an optimal way) and on every upgrade then the user has to hack away the same thing. Likewise, if the user changes themes another layout.Master has to be changed. Whereas if this is solved in the <portal:SiteTitle> web control then it would work the say way for all themes.