> I think putting a SSI in a template sort of defeats the
purpose. I suppose
> it has its uses.
Think again.
I use the following scheme....
First, I mentally separate the page layout into three
sections:
1. Stuff that will probably not change for the life of the
site (i.e., the
basic
structural elements)
2. Stuff that *could* change from time to time (e.g.,
navigation elements,
burst advertisements, section-specific navigation, etc.)
3. Stuff that *will* change from one page to the next
Then I create a template containing all class1 elements. Next
I create
server-side include files containing all class 2 elements and
place them on
the template as needed. Note - some of the class 2 elements
may be
"section-specific elements", and their placement on the
template will be
subject to the next item. Finally, I insert editable regions
to cover the
class 3 items, INCLUDING the section-specific navigation.
This allows me to just cookie-cut the rest of the site. I
estimate that
even for fairly large sites, about 80% of my work goes into
planning and
creating this template file.
--
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
==================
"Art" <lee_*nospamification@artjunky.com> wrote in
message
news:g4vvlq$bl4$1@forums.macromedia.com...
>
>> Can you not include server side includes in
templates?
>
> I think putting a SSI in a template sort of defeats the
purpose. I suppose
> it has its uses.
>
> Of course you should make sure the SSI is posted and all
pages that have
> the SSI in them should also be posted. I don't think
putting a SSI in a
> template is any different than any other bit you might
put in a template.
> The only other problem I can think of is perhaps you
have the path to the
> SSI wrong?
5
Replies
AdChoices