Hi Miva-Users,
I am doing a redesign on a site and was wondering if I could get some input
on design philosophies and prefered methods.
Currently, the site has many files that are accessed individually in
different directories with a combination of shtml and miva. What I mean is
if somebody wants the help page the go to
http://domain.com/subdirectory/help.shtml, if they want to access the
feedback page they go to http://domain.com/sudirectory/feedback.shtml, etc.
and some the shtml pages incorporat miva scripts.
Since I am currently using shtml and miva, I have two sets of template files
for headers, footers, site variables, etc. I would like to do away with the
shtml part and go strictly with miva for sake of simplicity with the
templates. However, I do realize that the miva processor is much more
complex and uses more of my server for processing than the SSI parser.
Another point, I was thinking of is only having one script to access all
other functions/scripts. In other words, when a person reaches my site they
go to the index.mv page and all other pages would be accessed through the
index.mv page. For example, if the person now wants the help page it will
be accessed by http://domain.com/index.mv?Link=help, and if the want the
feeback page it will be http://domain.com/index.mv?Link=feedback.
Can someone please enlighten me on some of the advantages and disadvantages
of the two methods described, ie. many scripts vs. one script with
functions?
Also, is it better to keep the shtml pages and not all miva to conserve the
miva engine?
All suggestions/feedback welcome.
Thanks,
Ed
__________________________________________________ ___________________________________
Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com
Comment