I think that's just a bit of an odd thing to say. It all depends on how
you have your app set up. I've never heard any convincing reason to keep
display code out of application.cfm files. Application.cfm is a great
place to handle things that need to be handled across and app (hence the
filename). I keep hearing people say that this is "bad practice", but
seldom do they ever offer any explanation as to why they think this. If
you have an application.cfm file that cfincludes a header.cfm file,
you've essentially done the same thing as putting header.cfm's code in
your application.cfm file. There isn't any real difference, unless
there's a lot of information that makes sense to separate so that it can
be more easily maintained. Often, application.cfm is a very logical
place to put the meta tags as you're likely to be setting the product
line or whatever for a given page in this file as well.

Now the real thing here is this. If you really want to kick SEO in the
pants, you can write your application so that it writes your entire site
out as static html. Most big search engines don't have any "problem"
getting through dynamic sites, but why limit it or take the chance. It's
much better to have your app generate itself as static html and then
watch it just get crawled like CRAZY! I have several sites that work
this way right now and I'm rewriting fitzandfloyd to do so as well.

  _____  

  They do (well, they -can-).

  Application.cfm is really just like any other CF template that
runs...it's
  just implictly pre-pended to all applicable files.  The question is,
do
you
  put any HTML in there?  I've heard where it's considered bad practice
to
put
  display code into the Application.cfm.  I interpret this as any HTML
(even
  meta tags).  I could be off base here, or it could just be that there
really
  is no definitive 'rule'.

  I've just been in the habit of keeping all HTML out of there.  It's
sole
  purpose is to control the template files that reside beneath it.  Not
to
  display anything to the screen (or the source code).
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to