To speed development and ensure consistency of design, template authors are encouraged to assemble pages from distinct component templates that may be recycled in different contexts. One typical -practice is to build a "master" template for an entire section of a -site, with a common header, footer and sidebar layout. For each -page request, the "content" template is incorporated dynamically -into a specified area of the master template, usually a table -cell.
+practice is to build a "master" template for an entire +section of a site, with a common header, footer and sidebar layout. +For each page request, the "content" template is +incorporated dynamically into a specified area of the master +template, usually a table cell.(graphic)
Another common practice is to build small reusable templates that may be included in other templates as logical components. This -may be useful for common "widgets" such as search boxes or lists of -related links, as well as for building configurable portal pages -where users may assemble different types of content to their -liking.
+may be useful for common "widgets" such as search boxes +or lists of related links, as well as for building configurable +portal pages where users may assemble different types of content to +their liking.(graphic)
See include and -master. See also Building reusable layout components and -Using master templates.
+master. See also +Building reusable layout +components and Using master +templates.Template authors need a simple mechanism for declaring
properties within the templates. The most common use of such
@@ -115,7 +117,7 @@
Caution: Do not write to the connection.
Specifically, if you must use the <% %> tag, do
not call ns_puts, because it will not work the same
-way as in AOLserver's ADP pages.