Well you have the create statement pretty much OK, as far as it goes.
have you thought about the structure of your web pages? as it stands, each of your page 'contents' will have the same tags throughout, which means you have some content stored in many records for no real reason. And then if you decide in the future to adjust an individual page, might that break the others because they would all have the same tags?
How I have done it is this.. (not that I am correct but it works for me and the pharmacist. lol)
I store my images in a set of three tables - images, gallery_titles and gallery_images. So I have a bucket of images and then I decide which gallery they are to be in.
I store my text for each page in a set of tables. file_sequencing, file_data and file_images. Which means I can have several paragraphs stored individually where each may or may not have an image(s). Sequencing is used to sequence them in the nav menu.
So if I change the html tags on any one page it won't affect any other but, at the same time, I haven't stored certain html tags throughout the db which would have to be altered if I redesign the website. (I leaned that the hard way) - pretty much like always.
food for thought. It may not work for you but it might get you rolling a bit further.