Best database structure

[siobhan]

I am constructing a database for the front page of a website. The front page has several sections: 1) a photo story section with a head line, photo, tagline, and link to the complete story. There are three photos stories in total on the front page. 2) a welcome section with a bit of text about the site, 3) a training section with a bit of text about training and 4) a today section with a bit of text.

Sections 2, 3, 4 will have the same headline always

I need a bit of advice on how to structure the database (an admin user will use a web front end to update the database).

Is it okay to put all of this in the same table or should i have three separate tables?

What table fields would you suggest? Right now I have

FrontPageID
UserID
DatetoUpload
DatetoRemove
welcome training
today
story1tab
story1head
story1tag
story1photo
story1link
story2tab
story2head
story2tag
story2photo
story2link
story3tab
story3head
story3tag
story3photo
story3link

[laserlight]

It seems like you need a table to record the user that posted the content, along with information of when the content was posted and when it should be removed from display, so:

Table: PageItem
id
userId
uploadDate
removeDate

I would likely create a table for the photo stories, e.g.,

Table: PhotoStory
id
pageItemId
headline
photo
tag
link

I might hard code the other sections into the page, or maybe create another table:

Table: PageSection
id
pageItemId
title
content

[siobhan]

Thank you! This is very helpful.