T
tcarp
I've developed a reasonable working knowledge of html, CSS, DWTs, and
includes over the last few months; probably just enough to be dangerous.
I've been re-working my sites to aline to and take advantage of these
capabilities but would like to get some comments from the more experienced in
these areas on the strategies I've been working through on their use.
To start, there are some basic assumptions I have on DWTs and Includes I
want to validate.
"DWTs will always create the entire <head> section." If this is true then
the style sheet links, the meta data (names, etc.), and the scripts will be
the same for any page that use the same DWT. The strategic implication is,
that if I want to use a different style sheet, for example, I will need to
create a separate DWT even if the structure defined in the two DWTs is
exactly the same. This is sort of the inverse of the approach used at
cssZenGarden.com for example.
The approach that would maximize creating modular, reusable components of a
site while eliminating having to put redundant copies of the <body> in each
DWT would be to perhaps use an Include for the entire <body> section while
only varying the <head> stuff. Is that a sound approach or are there other
ways to work with the DWT rules but allowing <head> sections to vary for
different major subsections of the site.
"Includes only bring in <body> sections". For navigation I use a pull-down
menu technique. For related pages in a subsection of a site, the menus, and
their pull-downs, are exactly the same, however, they change between the 1st
and 2nd levels of the site structure (i.e. the top level pages all use the
same menus, but each major 2nd level have their own which is consistent
through all pages at that level within a subsection.)
My thought was to use Includes that change from DWT to DWT to pull in the
html that defines the menu being used. This means that, rather than having
to copy/paste all the menu code every time I change the content of the menus,
I could create a new DWT with a different Include for each menu structure and
make any menu changes in the separatly included <body> code with the changes
being replicated automatically into the pages.
Before I jump into changing the basics of the site I wanted to make sure I
had a solid strategy based on a good understanding of the character and
functioning of DWTs and Includes.
Thanks for any advice.
Tom
includes over the last few months; probably just enough to be dangerous.
I've been re-working my sites to aline to and take advantage of these
capabilities but would like to get some comments from the more experienced in
these areas on the strategies I've been working through on their use.
To start, there are some basic assumptions I have on DWTs and Includes I
want to validate.
"DWTs will always create the entire <head> section." If this is true then
the style sheet links, the meta data (names, etc.), and the scripts will be
the same for any page that use the same DWT. The strategic implication is,
that if I want to use a different style sheet, for example, I will need to
create a separate DWT even if the structure defined in the two DWTs is
exactly the same. This is sort of the inverse of the approach used at
cssZenGarden.com for example.
The approach that would maximize creating modular, reusable components of a
site while eliminating having to put redundant copies of the <body> in each
DWT would be to perhaps use an Include for the entire <body> section while
only varying the <head> stuff. Is that a sound approach or are there other
ways to work with the DWT rules but allowing <head> sections to vary for
different major subsections of the site.
"Includes only bring in <body> sections". For navigation I use a pull-down
menu technique. For related pages in a subsection of a site, the menus, and
their pull-downs, are exactly the same, however, they change between the 1st
and 2nd levels of the site structure (i.e. the top level pages all use the
same menus, but each major 2nd level have their own which is consistent
through all pages at that level within a subsection.)
My thought was to use Includes that change from DWT to DWT to pull in the
html that defines the menu being used. This means that, rather than having
to copy/paste all the menu code every time I change the content of the menus,
I could create a new DWT with a different Include for each menu structure and
make any menu changes in the separatly included <body> code with the changes
being replicated automatically into the pages.
Before I jump into changing the basics of the site I wanted to make sure I
had a solid strategy based on a good understanding of the character and
functioning of DWTs and Includes.
Thanks for any advice.
Tom