Hi,
what would be the best way to set up the system (page assets + css) to do tabbed pages (similar to how the wiki looks) so the end user thinks that they're looking at varying aspects of a single process/level.
Thanks
Hmm… interesting. The thought off the top of my head, is that you'd need to use asset listings set to display the contents of each asset, and then use CSS to style the listing to create the tabs.
Haven't actually tried to do this in practice though. 
Nah, that's a little overkill. 
Build your docs like this…
…and just use a menu_normal MySource_AREA. Set level to 1 and build the menu as a plain old boring list.
Then apply some suitable suitable to get the tabs.
Neither of those two links work for me?
Hi,
here's the structure so far but I can't stop 'Sub Level 1' from appearing like a 'Tab Page'.
Site:
Level 1:
…Tab Page 1
…Tab Page 2
…Tab Page 3
…Sub Level 1:
…Tab Page 1
…Tab Page 2
…Tab Page 3
Level 2:
I've got the basics the using this (from the tutorial) for the level;
--------------------------------------------------------
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title><mysource_print id_name="global" var="site_name" /> : <mysource_print id_name="global" var="asset_name" /></title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<style type="text/css" media="all">
body {
background-color: #fff;
color: #000;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: small;
}
</style>
</head>
<body>
<div id="breadcrumbs>
<MySource_AREA id_name="breadcrumb_trail" design_area="asset_lineage">
<MySource_SET name="levels_to_print" value="0" />
<MySource_SET name="prefix_with_home_link" value="true" />
<MySource_SET name="show_hidden_links" value="false" />
<MySource_SET name="suffix_with_current_link" value="true" />
<MySource_SET name="prefix_with_divider" value="true" />
<MySource_SET name="suffix_with_divider" value="false" />
<MySource_DIVIDER>
>
</MySource_DIVIDER>
<MySource_ASSET>
<a href="<MySource_PRINT var="asset_link" />"><MySource_PRINT var="asset_short_name" /></a>
</MySource_ASSET>
</MySource_AREA>
</div>
<div id="mainbody"><mysource_area id_name="body" design_area="body" />
</div>
<div id="menu">
<MySource_AREA id_name="right_menu" design_area="menu_normal">
<MySource_SET name="level" value="children"/>
<ul>
<MySource_ASSET>
<li><a href="<MySource_PRINT var="asset_link" />"><MySource_PRINT var="asset_name"/></a></li>
</MySource_ASSET>
</ul>
</MySource_AREA>
</div>
</body>
</html>
-----------------------------------------
and this for the tabbed pages;
-----------------------------------------
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title><mysource_print id_name="global" var="site_name" /> : <mysource_print id_name="global" var="asset_name" /></title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<style type="text/css" media="all">
body {
background-color: #fff;
color: #000;
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: small;
}
</style>
</head>
<body>
<div id="breadcrumbs>
<MySource_AREA id_name="breadcrumb_trail" design_area="asset_lineage">
<MySource_SET name="levels_to_print" value="0" />
<MySource_SET name="prefix_with_home_link%
Make "Sub Level 1" a TYPE_2 link – on the Linking page. That should make it disappear.
Hi,
that worked but I'm trying to have appear as a child link of Level one but not of 'Tab 1, 2 and 3' of which it is a sibling. The problem is, I do want 'Tab1, 2 and 3' to appear as siblings of each other.
Ian
Sorry,
I should have been clearer. I don't just have one level with a subset of tabbed pages. Each level down has a set of tabbed pages. I need to separate the tabbed list of links from the links to children (levels) as they are both necessary. I was wondering if there's something in the design options to identify the assets as different 'types'. Then I could apply one design for tabs and another for levels.
You can't do that at the moment. The menu system grabs everything that has a TYPE_1 link and doesn't really distinguish between siblings.
Thanks,
is it possible to use div's within a page asset plus a css to generate the tabs or would this involve developing a customer page asset? I know how to do this (css + html) manually but I'm keen to know if the page asset can be easily set up with pre-named div's.
Ian
Each Bodycopy in a standard page can have an ID (and gets one by default). You can also use the Div Properties dialog box to change the ID of each bodycopy.
If you want to create a page that automatically has multiple DIVs, each named specifically, you'd have to create a custom asset.
To clarify, the ID being changed is for the DIV - not the bodycopy asset. The bodycopy asset holds the content containers (either DIVs or TABLEs) that can each have an ID.
Whoops, sorry. I meant to say bodycopy DIVs, but obviously lost my mind… la, la, la. If you see it, please tell it to come home.
Hi,
I set up a working model by synchronising the div id's with my CSS and some javascript in a parse file. Unfortunately the model ignored any tables inserted between the div's within a single page asset. So, it sort of works. I think that this is probably the way to go for managability, as you don't want to be workflowing closely align subsets of pages separately.
Ian
[quote]Nah, that's a little overkill.
Build your docs like this…
…and just use a menu_normal MySource_AREA. Set level to 1 and build the menu as a plain old boring list.
Then apply some suitable suitable to get the tabs.[/quote]
Hi,
my tabs are generic so I replaced;
<li><a href="#">Item two</a></li>
with
<li><a href="/tab1">Tab 1</a></li>
Unfortunately this doesn't produce a relative URL and jumps me back to suitable, which doesn't exist as the site is several levels deep. Is this correct or are you making some special use of the list generated by matrix via the 'Mysource_Area' command?
regards,
Ian
Ian – can you email me the parsefile and CSS you're using (it got cut off above). avi dot miller at squiz dot net.
Thanks!