> Okay, I'll elaborate.
Thanks :)
> One nice benefit to having a fusebox architecture behind static content is
> that you've got an instant roadmap of where all links are going
> to, insofar
> that the links are within the app.
What can I see in the index.cfm that I can't see just by looking
at the directory structure?
> Because you can now one-stop-shop for all the in-app links in
> your app, it's
> pretty easy to see what is doing what.
Not really sure what you mean by that. Besides, if we're talking
about static content, we're not talking about an "app",
are we?
> And if you should ever choose to start introducing dynamic content, you
> already have the fusebox there, so it's a snap to integrate.
True. That's certainly something that needs to be taken into
consideration. Of course, it also depends on what you mean by
"dynamic." It's possible that the dynamic part could be acheived
by using an app to update the static pages.
> If you have anybody in your shop who knows Fusebox, they'll be
> able to pick
> up the app and run with it, even though it might be almost entirely static
> content.
But what if they don't know Fusebox? Or Cold Fusion for that
matter? Anyone who knows HTML can pick up a static site and
run with it.
I don't mean to sound anti-fusebox, and it's not that I don't
think we should use Fusebox for static sites. I don't think
we should use Cold Fusion for static sites.
Patrick
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
