[thelist] Fusebox framework and PHP

.jeff jeff at members.evolt.org
Thu Jul 25 19:34:01 CDT 2002


boris,

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> From: Boris Mann
>
> BUT, the learning curve is very steep, I find. You
> definitely have to buy in to the Fusebox concept, and
> I found it hard to get used to.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

as steve already said, it's important to understand that you don't have to do everything the way it's suggested in the fusebox concept.  what's more important is that whatever you do take from it and use you do so consistently.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> As a drawback, one big weakness is that the URLs aren't
> very search engine friendly, so it's something to watch
> out for if that's important for your web app.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

to be fair, the weakness you cite regarding urls isn't a symptom of using fusebox.  it's a symptom of dynamic, data-driven web development.  the fusebox concept even has things in place for building apps that are more search engine friendly, though not as much as they could be.  ie, querystings like /index.cfm?foo=bar&fooid=7 are converted to /index.cfm/foo/bar/fooid/7/.  however, to be truly search engine friendly, you have to get the extra data off the end of the url past the file name (and the filename outta the url as well, preferably), resulting in something more like /bar/7/.

evolt.org is a good example of this.  notice the urls don't have any querystrings except when you're logged in or if it's a page the search engine couldn't get to to begin with (like search results since they can't submit forms).  the site looks static to search engines but is actually fully dynamic.

.jeff

http://evolt.org/
jeff at members.evolt.org
http://members.evolt.org/jeff/






More information about the thelist mailing list