Hi Vipul,

It is possible to use up to 5 content panels and you can position the extra 2 anywhere you want in layout.master. But that won't really give a rows and columns kind of layout. For that I recommend to just use one content instance in the center panel and then do layout inside that content using content templates. Keep in mind that each content instance you add to a page is requiring additional hits to the database to get the page content so it isn't really optimal to put lots of instances on a page, it can be more efficiaent to use a single content instance and do layout inside that instance.

You can find some non-Artisteer skins in the extra-skins.zip download on our codeplex download page.

Hope that helps,

Joe

Hi,

If you are using the latest version of mojoPortal, then MenuAdapterSuperfish is deprecated and no longer used. If you look at the latest version of jQueryUI skin which uses superfish you will see the menu is configured like this in layout.master:

<portal:SiteMenu id="SiteMenu1" runat="server"
MenuSkinID="Superfish"
UseTreeView="true"
TreeViewShowExpandCollapse="false"
TreeViewExpandDepth="-1"
HideMenuOnSiteMap="false" ></portal:SiteMenu>

and the menu classes are controlled in theme.skin like this:

<portal:mojoTreeView runat="server" SkinID="Superfish"
ContainerCssClass="AspNet-Menu-Horizontal"
RootUlCssClass="sf-menu sf-navbar"
RenderLiCssClasses="true"
RenderAnchorCss="true"
LiCssClass=""
LiRootExpandableCssClass="sf-with-ul"
LiRootNonExpandableCssClass=""
LiNonRootExpnadableCssClass=""
LiSelectedCssClass="current"
LiChildSelectedCssClass="current"
LiParentSelectedCssClass=""
AnchorCssClass="inactive"
AnchorSelectedCssClass="current"

/>

This configuration is using mojoTreeView.cs and TreeViewAdapter.cs

So it is possible to control css classes easily from theme.skin

Hope that helps,

Joe