Currently i am wondering whether or not to use a MySQL DB to provide content on my website.
An example of what i mean is based loosely here: http://www.asual.com/jquery/address/samples/
find the sample called SEO. Alternatively Click Here
Anyone with HTML5 able browsers will notice the URL is ‘pretty’ and is what you’d expect to find on any standard website.
Anyone with IE8 or a browser which isnt ‘Webkit’ enabled, will see the use of the Hashbang (#!) in order for SEO.
The problem is this: the content is pulled from a MySQL DB..
I have approx 30 pages (some are PACKED with content) And im wondering if all this tedious modification of my website is necessary?
I use jQuery MySQL and PHP through a single page interface so my content is not indexable at all. What are your views?
Help me!!
PS. would it be easier to provide PHP Includes in my DB content to fetch pages without having to upload all my pages into my DB?
your question is made up of a lot of questions. 🙂
to mysql or not to mysql: most of the PHP-usng web world is using mysql as a database to store content. i don’t see much of a problem there. 30 pages is peanuts.
jquery and php for a single page interface indexable: depends on the search engine. i’ve read somewhere (too lazy to look things up) that google uses a javascript enabled crawler. not sure if they use it in production already.
PHP includes in DB content: textpattern uses this approach. your worry is a problem of scale.
if your PHP code can serve pages properly, it wouldn’t matter where it pulls content from. DB or filesystem wouldn’t matter at this point.
just do it.