Building a website w/ php-mysql...

madcat

Hi-

Can someone please help me hash this out...

At the moment, when I build a website...I will have a separate .html file for each page of the site. All of the information goes directly on the page. Of course, sometimes I use php includes to include common sections like the navigation and/or footer.

I'm really interested in using MySQL tables in conjunction with creating websites. I don't quite understand how this is accomplished however. A few questions I have (when coding I'll use php within .html files)...

If you're building a website using MySQL db tables...Is it still necessary to have separate .html files for every 'page' of information. Or could you just use an index page (a template) that imports/exports (so to speak) information for new sections via php variables? So instead of having index.html, services.html, contact.html > You have just index.html and the index, services and contact info get pulled out of your db tables and inserted into the variable within index.html?
Do you put everything in your MySQL table? Such as page headers, paragraphs of information, paragraph headers...meta tags...

If so, do you have a separate MySQL table for each .html page in your site?

How is it that you use php and MySQL to create websites...maybe just some ideas and examples as to what uses the db tables have with your site.

I've read some articles on building your site w/ php and mysql- these are just some specific questions I still have. I appreciate any help!

Matt

ClevaTreva

I've been working on a GPL app called phpSiteContent for months, which does what you want. It isn't finished, as I am just halfway through the admin pages.

Release 1 will allow the management of the pages and color schemes (these can be set per subdirectory or subdomain).

Release 2 will add news management (and articles, diary, etc).

Release 3 will be a skinable version (I have over 50 skins already in progress).

If this page is up (I haven't paid for the server for a while, but it was there when I last checked, you can see what release 2 will look like):

www.chippingcampdenbaptistchurch.org.uk

A new site/server with release 1 is:

www.cornerstonechurches.org.uk

Both are beta test sites, where some links work, others don't!

The important thing is, this is what the php for EVERY page looks like:

<?php
include("/home/***/public_html//config.inc.php");
include("$docRoot/phpsc/**barepage.inc.php");
?>

Only the search page is different, in that a few extra variables were needed (the search engine works!).

All the elements for the page are stored as modules and called according to the page setup defined by the admin user. Browsing around you will see different layouts. ALL the content is in the database.

I anticipate 1.0.0 being released in a month.

I'm hoping users will ask for mods and a community to use it and support it will evolve.

Trevor
PS, I hope this isn't considered an advert, coz it isn't intended as such. I'm donating this app to the community coz it was developed with much help from this forum and its members.

groovything

Originally posted by madcat
Hi-

Can someone please help me hash this out...

At the moment, when I build a website...I will have a separate .html file for each page of the site. All of the information goes directly on the page. Of course, sometimes I use php includes to include common sections like the navigation and/or footer.

Heres what I do:

I process all content (most of it anyways) through default.php

I create the layout using a table.
top row:
banner

second row:
1st <td> = menu include( <? include ("inc/menu.inc"); ?> )
menu items link to:
"default.asp?page=content_here"

2nd <td> = content include ( <? include ("page/$page.htm"); ?> )
3rd <td> = advertizements, right column content

third row:
footer (copyright, legal, etc...)

you can use the querystring to tell the content td which page to display.

this way, you never have to duplicate any code. - it's much easier to edit too if you organise your directories well.

1. If you're building a website using MySQL db tables...Is it still necessary to have separate .html files for every 'page' of information. Or could you just use an index page (a template) that imports/exports (so to speak) information for new sections via php variables? So instead of having index.html, services.html, contact.html > You have just index.html and the index, services and contact info get pulled out of your db tables and inserted into the variable within index.html?

It depends on the content. You will figure that out as you build the site. I use a different htm file for most of my content, but i build those files with very little formatting so I can feed them into the main section and the css detemines how they display. that way you can revamp the entire site by editing one css, or in my case dynamically select from a bunch of different stylsheets.

The actual content of the pages is mostly pulled from a database, but the htm files provide the specific 'shell' for the content to be delivered to. (they call specific sql queries to get the desired content)

2. Do you put everything in your MySQL table? Such as page headers, paragraphs of information, paragraph headers...meta tags...
If so, do you have a separate MySQL table for each .html page in your site?

page headers are all in the default.php file

introductory paragraphs (explaining the function and content of the specific section) are in the .htm files and all content that is dynamic is databased. usually in a separate table for each category of content.

3. How is it that you use php and MySQL to create websites...maybe just some ideas and examples as to what uses the db tables have with your site.

Matt

examples of db tables:

registered user information table

images table & image comment table

writing contest table

etc...

if you want to see it in action see my website groovything.com(button below)

look at the address bar to see the querystring values