Page 1 of 1

Large site_best way to construct it with database, language

Posted: Thu Dec 25, 2003 7:49 pm
by zak
I need serious advice in deciding what to avoid and the best way of reconstructing a large content rich website.

I have a linux server on Apache with Mysql installed and believe it best to store data in the database. It is an extensive site with lengthy content.

I intend to implement:

a forum
user login
articles
ads
site search
how many are online

It is hoped that this site will grow larger and in the future possibly incorporate ecommerce, events search etc...

I was planning on using (X)html with tables and CSS formatting....

Some of my questions are:

Can I (or would it be advisable) to store all data in the database or only content modules which require frequent editing?. Of primary importance are search engine ratings…do spiders avoid dynamic content or is there a way around this?….perhaps if not everything is stored in the database this is not an issue.

Is html better to use than Xhtml?

As the pages are all lengthy it is probably necessary to compress the data… I am wondering if there is a preferred method of compressing the data?

If there is any advice you can give me on what things to avoid as well as what the best way to proceed I am open ears and would fully appreciate any advice or suggestions. I am about to begin reconstructing this monster and can not risk losing search engine position.

thanks,
zak

Posted: Thu Dec 25, 2003 8:15 pm
by McGruff
(1) My understanding is that most SEs do not have a problem with dynamic sites. If you are new to db design, check this out http://www.oreilly.de/catalog/javadtabp ... r/ch02.pdf.

(2) Xhtml.

(3) Make the pages shorter - eg paginate, re-organise, etc?

Can use ob_start("ob_gzhandler") to compress data sent to client:

Code: Select all

<?php
    function outputPage() 
    {
        ob_start("ob_gzhandler");
        
        $this->_openPage();
        echo "\n";
        $this->_printBlocks();
        echo "\n";
        $this->_closePage();
        echo "\n";        
    }
?>
You'll probably want to maintain page URLs (which may have been bookmarked). Page caching can sidestep problems with args from the query string. In fact, always use php to write html files where possible (less server load).