Question

I have this page table structure to store all the website page information,

page_id
page_url
page_title
page_subtitle
page_description
page_introduction
page_content_1
page_content_2
page_content_3
page_content_4
...

You can see that I have page_content_1 to page_content_4, instead of just page_content. The reason why I do this because I might want to store different types of page content for each page.

But I doubt whether this is a good practice or not? What if other developer comes to further develop on this page table, would you find this structure redundant?

I am thinking maybe I should create another table to store additional page content like this below?

table page_additional_content,

content_id
content_additional_1
content_additional_2
content_additional_3
content_additional_4
page_id

Is this better?

Or there is better standard idea that I should look into?

Answer 1

Building on Quentin’s answer, if you want to be able to reuse content across pages (such as headers or footers), you could create a table structure like:

page_content: 
     content_id (primary key)
     actual_content (actual content of the page)
page_structure: 
     page_id (foreign key of the page)
     content_id (foreign key of the content)
     order_in_page (order of the content in the page)

You content can grow to as many sections as you want without adding additional tables (just add a new row in page_structure and increment the order_in_page counter).