-
Blog
- Query from items where category is blog
- Display data by latest date first
options
- Display a particular news item (link in title) and show comments in that view (limit)
Articles
- Query from items where category is articles
- Display data by latest date first
- Display title and first paragraph
- Link title to full article
options
Projects
Same as articles, just different category.
Contact and about section
- Query from items where category is either contact or about
- Display title and content
Photoblog
All PHP driven
That's everything i've got for the display. The database connection happens quite a lot so would it be wise to include the db connection in a seperate PHP file and then require it in all the db queries? Doing a detailed design on the admin section now
-
Why would you want to store the content for an about and contact page in the database, they willl just be static HTML so you'd be making an unnecessary demand on the database. Plus, it's easier to modify a static HTML page in your code editor than via phpmyadmin or the equivalent
-
Are you going to require users to register if they want to add comments or view comments?
Also I wouldn't see about and contact being modified a great amount - about and contact you could barely consider content. I would leave them as static personally.
-
Yeh i'm going to leave those pages as static. No they won't have to register in order to post a comment.
I'm just writing the admin section now, i'll paste code later on. Still need to do the SQL code as well