One method we use is to create our pages as include files themselves. We
then build the main display page with simple code to set Page specific
information (like Title, template, etc.).
We have a template file for the application that includes the specified
files at the required point.
So I might have a template like this:
<cfparam name="PageTitle" default="">
<cfparam name="IncludeFile" default="no_includefile.cfm">
<html><head><title><cfoutput>#PageTitle#</cfoutput></title></head>
<body>
<table>
<tr><td colspan="2"><cfinclude template="myheader.cfm"></td></tr>
<tr>
<td><cfinclude template="menu.cfm"></td>
<td><cfinclude template="#IncludeFile#"></td>
<tr>
<tr><td colspan="2"><cfinclude template="myfooter.cfm"></td></tr>
</table>
and my main calling page would look like this:
<cfset PageTitle="Test Page">
<cfset IncludeFile="main.cfm">
<cfinclude template="mytemplate.cfm">
The main.cfm file would do anything required by that specific page.
We've moved to this because it allows us to change our templates across the
entire application with a change to a single file. It also for more modular
code, which leads to code reuse (in terms of the template at least).
This method also allows you to add javascript references or style references
on a per page basis, or on a system wide basis.
Hope this helps with your setup.
Shawn
----- Original Message -----
From: "Shannon Rhodes" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Friday, September 19, 2003 10:45 AM
Subject: Design Structure and cfinclude
> We all know that cfinclude is perfect for design headers and footers,
> but now that I'm actually redesigning my site to take advantage of
> this, I'm running into some perplexing problems. (Please don't
> suggest FuseBox, that's way overkill for this site and I don't have
> the time for it).
>
> My initial thought was: set up an Application.cfm and OnRequestEnd.cfm
> in each major section, which would call a header/footer for that
> section. I would be able to pass a url variable to request a
> print-friendly version instead, or to request no display at all (for
> action only templates). Global variables would be cfparam'ed, and one
> page title and set of meta tags would be defined per section. Voila,
> new pages can be content-only without even a cfinclude
> line---everything would be called by the
section's
> Application.cfm.
>
> As I'm getting into this, I'm finding that I don't like the loss of
> page-specific flexibility. I'm told that dynamically generated meta
> tags often are missed by search engines, for example, and I don't have
> a way to override the standard section page title for pages that
> really ought to
have
> their own title. I'm also stuck with defining all CSS and JS in one
> long file, even if some style definitions and JS functions are only
> needed on
one
> page, because I've made the header of my document standardized. Seems
> to
me
> I'm adding all kinds of unnecessary download time. Plus, my "section
> specific Application.cfm" idea kind of forces me to model my
> directories after my site navigation, when I'd actually prefer to
> avoid a lot of third level directories and keep pages logically
> grouped instead (after all, navigation sometimes changes over time
> anyway, but who wants to move directories around).
>
> I think I need a balance between letting CF templates "do it all" for
> me, and the tedious work of writing in each page information that is
> probably the same 80% of the time in a given section.
>
> Can anyone suggest a "best practices" approach to using cfinclude for
design
> elements? Should I hard code in most of the head area of documents,
> so I can put in page-level titles, meta tags, and page-specific styles
> & JavaScript, followed by a cfinclude containing the remainder of the
> head with links to the master style sheet, and any design code that
> will not change, followed by another include for section-specific
> design images?
Any
> suggestions are appreciated!
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm?link=i:4:137692
Archives: http://www.houseoffusion.com/lists.cfm?link=t:4
Subscription: http://www.houseoffusion.com/lists.cfm?link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community.
http://www.fusionauthority.com/ads.cfm
