Forum Moderators: buckworks
There are advantages & disadvantages to both, but here are a couple things to keep in mind before going with one or the other.
1) Static pages require more maintenance but allow more flexibility in page control & layout.
2) Static pages may be better indexed by certain search engines. Google will pick up dynamic pages, but it is the safest route.
3) Static pages don't require a link to the database everytime a product is viewed, resulting in faster page loads and overall site speed.
4) If you ever need to change the site to another shopping platform will your URL change as a result? With static you can keep the url as long as you are moving to another system that allows you to pass the product parameters into the cart.
Ultimately a dynamic system can be created that reads from a product database table and writes the static .html files. This way, you can incorporate inventory control and reduce page maintenance.
My only regret for my own pages is that I used .html and not .php for my static files. If I had used .php then I could add some dynamic features into the page later.
But just keep these thoughts aware before choosing a system that ties you into using their own frontend for product pages.
those most affected are those which are combined catalogue / shopping carts. the session ID is really only required to "maintain state" in the shopping cart part of it, so look for a "bolt on" shopping cart instead.
>>My only regret for my own pages is that I used .html and
>>not .php for my static files. If I had used .php then I
>>could add some dynamic features into the page later.
if you're on *nix with php, i believe you can parse .html files just the same as you parse .php files. ask in the *nix / php forum for more info. i do almost everything in php or asp these days so can't tell you any more about it myself.