How was the main site's Documentation section built?

If you have questions about using mojoPortal, you can post them here.

You may want to first review our site administration documentation to see if your question is answered there.

This thread is closed to new posts. You must sign in to post in the forums.
1/31/2012 10:21:27 AM
Gravatar
Total Posts 10

How was the main site's Documentation section built?

Joe,

Did you use built in features to create the documentation section? I need a similar documentation section with an expandable index. The closest thing I see is the links feature. The blog feature might work if it was easy to find and go straight to a specific entry, but I'm not familiar with it yet.

BTW, thanks for the cms!

1/31/2012 12:39:21 PM
Gravatar
Total Posts 18439

Re: How was the main site's Documentation section built?

Our documentation is made simply from pages with Html Content feature on them arranged in a hierarchy. Some of the pages that are just top level parent of other pages don't have any content of their own but have the "Show Child Pages Site Map?" checked in Page Settings and that makes an index in the middle of the page linking to the child pages, the one on the left is just the PageMenu. The article Menu Structure and Properties may help you.

Hope that helps,

Joe

1/31/2012 2:29:00 PM
Gravatar
Total Posts 10

Re: How was the main site's Documentation section built?

Nice,Cool  that one little checkbox makes all the difference. Now I don't have to do anything else.

1/31/2012 3:37:38 PM
Gravatar
Total Posts 10

Re: How was the main site's Documentation section built?

In the center section, the child pages show up, but I'm not getting the hierarchy, expandable/collapsible structure. Everything is left justified. Am I missing setting or is it the skin I'm using (artisteer31-green).

2/2/2012 9:34:44 AM
Gravatar
Total Posts 18439

Re: How was the main site's Documentation section built?

Hi,

In your theme.skin file update this entry like this:

<portal:mojoTreeView runat="server" SkinID="ChildSiteMap"
ContainerCssClass="sitemap"
RootUlCssClass="childpagesitemap"
RenderLiCssClasses="false"
RenderAnchorCss="true"
LiCssClass=""
LiRootExpandableCssClass=""
LiRootNonExpandableCssClass=""
LiNonRootExpnadableCssClass=""
LiSelectedCssClass=""
LiChildSelectedCssClass=""
LiParentSelectedCssClass=""
AnchorCssClass=""
AnchorSelectedCssClass=""
ExpandDepth="-1"
ShowExpandCollapse="true"
PopulateNodesFromClient="false"

/>

then add this in your style-artisteer-overrides.css:

div.sitemap ul { list-style:none; }
div.sitemap ul li { margin-top: 7px;}
div.sitemap ul li li {margin-left:10px; }
ul.childpagesitemap { margin: 0px 0px 0px 0px; }

div.sitemap .AspNet-TreeView-Collapse
{background: url('collapse.gif') 0 0 no-repeat; width: 15px; margin-right: 5px;
float:left; cursor: pointer; font-family: Courier; font-size: large;
line-height: 15px; text-decoration:none;}
div.sitemap .AspNet-TreeView-Expand
{background: url('expand.gif') 0 0 no-repeat; width: 15px; margin-right: 5px;
float:left; cursor: pointer; font-family: Courier; font-size: large;
line-height: 15px; text-decoration:none;}

.AspNet-TreeView-Hide { display:none; }

You may need to tweak this css to your tastes as far as margins or padding

Hope that helps,

Joe

2/2/2012 9:38:17 AM
Gravatar
Total Posts 10

Re: How was the main site's Documentation section built?

Thanks, u da man! Hopefully that will make it more readable than all left justified.

You must sign in to post in the forums. This thread is closed to new posts.