South Park Fan Site

[stradicaster]

I have a South Park Fan site for Turkish SP fans for 4 years now. I changed the design for many times and now I will convert my site from html plain site to a php+mysql based website to enchance my webprogramming skills. While this process is done underneath, do I have to do anything about the design?

I will be very glad if you make constructive critism. And thank you very much...

South Park - Turk
http://www.SPTurk.com

note: It's turkish but I think you will understand titles on the left hand. Flash menu leads you to the downloads...

[BerksWebGuy]

Your site looks like it would need some kind of help, if they are all static html pages. You could make it much easier with PHP.

You use PHP to make things dynamic, pulling things out of MySQL DBs, and a bunch of other stuff.

What will you be using php/mysql for??

[stradicaster]

Your site looks like it would need some kind of help, if they are all static html pages. You could make it much easier with PHP.

You use PHP to make things dynamic, pulling things out of MySQL DBs, and a bunch of other stuff.

What will you be using php/mysql for??

I will use php/mysql for updating site more easily, adding/managing new downloads/news to the site. It will be helpful for only administration, not user :). I want to create and use my own database for these.

It's much more about expanding my programming skills as a computer engineering student :). Only for hobby...

I'm working on php and mysql(I was familiar with C much and with tables a bit :)), I came much way but I'm a little bit confused about the database. I want to make a good database that don't waste much space and logically correct.

The problem is;
I have different download categories and all categories have different properties. For example one category has name, preview and size properties and another one has screen resolution and name only.

Solution;
I thought a design like creating tables to each property(name,preview) which have two different primary key; fileID and catID. And the table also has the value for size or preview files URL according to property.
There's also a main table with fileID, catID, URL, date and dlcount which is for finding other needed properties of downloads.

Question;
Is this a logical design? I have a OOP background also and I can't take myself from thinking about dividing the properties of an item is a bad way. fileID and catID is always will be repeated in every table, but also they will free more space because from eight different properties most of time four of them is used.

I will come up with another idea soon but how can it be solved in another way? With your experiences :)...