Multi-templates - some questions

Question

Hi...
Setting up a site and need multiple templates for the
following reason:
They may require / ask for colour coding in the main
navigation and masthead
areas and subsequent pages.
What i want to do is use SSIs to simplify later modifications
of the
navigation. Main navigation will be common across the site.
Using PMM for
the menu (horizontal).
What i propose is this:
Master file uses SSI for Navigation menu and footer. Use a
copy / paste of
the master to create sub templates for the various, proposed
sections.
Set up variations of the PMM css. Eg. PMMblue.css,
PMMgreen.css, etc. (Only
colours are changing here.) In each of the sub templates link
to that
particular PMM css. Set the editable regions in the sub
templates - will
actually be identical across the board.
Common navigation SSI for updating links - which will be
identical. Common
footer will be identical.
Anyone see any problems?
Grateful for feedback...
Thanks and Cheers,
JJ

Answer 1

> If i have one master template for all pages, effecting
these kinds of
> changes will be more of a hassle no?
No. It would be pretty simple, and the method would depend on
your skill
and ability with things like javascript or server-side
scripting. Here are
several methods you could consider (all shown with XHTML tag
syntax) -
1. The simplest would be to make the link to your *base*
stylesheet
(containing color scheme #1) link
<link href="base.css" rel="stylesheet" type="text/css"
/>
ABOVE the editable region called "head" in the head of the
template. This
would let you add a 'modifier' stylesheet link within that
editable region
that would change the color scheme as needed. Since this
modifier link is
BELOW the base link, conflicting rules will fall with the
modifier rather
than the base.
2. A more complex method would be to have dynamically written
stylesheet
links below the base link (both of which are BELOW the
editable region in
the head region called "head" -
<script type="text/javascript">if (styles == 2) {
document.write('<link
href="scheme2.css" rel="stylesheet" type="text/css" /' +
'>') }</script>
<script type="text/javascript">if (styles == 3) {
document.write('<link
href="scheme3.css" rel="stylesheet" type="text/css" /' +
'>') }</script>
and then in the editable region called "head" which is ABOVE
this scripting,
put this (on each child page - adjust the value of 'styles'
as needed) -
<script type="text/javascript">var styles =
2;</script>
3. Use a Template Conditional expression to determine which
stylesheet to
link based on the value of a Template parameter (use DW's F1
Help to work
through this).
4. Use server scripting to dynamically write the appropriate
stylesheet
link based on a lookup, or some other conditional logic.
Take your pick.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"Jay Jhabrix" <[email protected]> wrote in message
news:[email protected]...
>
> "Murray *ACE*" wrote:
>
>> DO NOT USE "sub templates". They'll drive you nuts.
I don't see any
>> need for them in the scheme that you have presented.
>
> Murray,
>
> Sorry, again, lack of lucidity in my description. Let's
drop the 'sub' for
> the templates.
>
> What i meant was, i have the master layout file (not a
template, just the
> design master) from which i create individual templates
for each section
> and its child pages.
>
> The way i figure it is:
>
> They may want colour coding according to section. So,
certain elements -
> say menu bar, item in header, may need to change at a
later date according
> to section. Therefore, creating the sectional pages
would be easier with
> individual section templates as a change here would
apply to all child
> pages in the section. Also, maintaining the SSIs would
be easier and could
> be locked in the non-editable region:
>
> Section 1 template:
> <!--#include file="fooblue.ssi" -->
>
> Section 2 template:
> <!--#include file="fooblack.ssi" -->
>
> If i have one master template for all pages, effecting
these kinds of
> changes will be more of a hassle no?
>
> Cheers,
>
> JJ
>
>
>> --
>> Murray --- ICQ 71997575
>> Adobe Community Expert
>> (If you *MUST* email me, don't LAUGH when you do
so!)
>> ==================
>>
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
>>
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
>> ==================
>>
>>
>> "Jay Jhabrix" <[email protected]> wrote in
message
>> news:[email protected]...
>>> Hi...
>>>
>>> Setting up a site and need multiple templates
for the following reason:
>>>
>>> They may require / ask for colour coding in the
main navigation and
>>> masthead areas and subsequent pages.
>>>
>>> What i want to do is use SSIs to simplify later
modifications of the
>>> navigation. Main navigation will be common
across the site. Using PMM
>>> for the menu (horizontal).
>>>
>>> What i propose is this:
>>>
>>> Master file uses SSI for Navigation menu and
footer. Use a copy / paste
>>> of the master to create sub templates for the
various, proposed
>>> sections.
>>>
>>> Set up variations of the PMM css. Eg.
PMMblue.css, PMMgreen.css, etc.
>>> (Only colours are changing here.) In each of the
sub templates link to
>>> that particular PMM css. Set the editable
regions in the sub templates -
>>> will actually be identical across the board.
>>>
>>> Common navigation SSI for updating links - which
will be identical.
>>> Common footer will be identical.
>>>
>>> Anyone see any problems?
>>>
>>> Grateful for feedback...
>>>
>>> Thanks and Cheers,
>>>
>>> JJ
>>>
>>>
>>>
>>
>
>