Ah, good point. We manually include the header and footer into each layout and that's nice for changing it on a per-page basis.
-Kevin ----- Original Message ----- From: "Craig Dudley" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Friday, September 19, 2003 11:10 AM Subject: RE: Design Structure and cfinclude > Remove the include from your application.cfm and put it at the top of > each template, that way you can pass in all your meta tags/titles with > simply variables.title etc, I know that means it's not quite so clean, > but it is only a few lines of code for each template and the footer can > still be called from OnRequestEnd.cfm. > > Your other option is cfhtmlhead. > > And as Kevin says, I would deffinatley use .css files and .js files > where possible. You could even use a sperate .css file for each section > if needed. > > -----Original Message----- > From: Kevin Graeme [mailto:[EMAIL PROTECTED] > Sent: 19 September 2003 17:09 > To: CF-Talk > Subject: Re: Design Structure and cfinclude > > > One quick suggestion: put your CSS and javascript into separate .css and > .js files that get called into the header. That way the browser should > cache. If you just put code in the page header itself, yeah it has to > download it fresh each time. > > I'm interested to see what other responses you get though because we're > in the same boat looking for a better method that doesn't make it too > complicated. > > -Kevin > > ----- 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:137705 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 Get the mailserver that powers this list at http://www.coolfusion.com
