Reply To: How to structure database for portfolio pieces on profile pages

[__]

Both user types will be able to upload up to 6 portfolio images, up to 10 skills, and a testimonial.

for images, you’d need to store (at least) the URL and the id of the user the image belongs to. Optionally, you could also store info about height/width/alt attribute/etc.

For skills: do you choose the skills, or do they?

If you do, then you’ll need a table to list the available skills, and an intersection table to associate user ids with their selected skills and “skill rating” (for designers, you could simply leave this field NULL).

If users are allowed to choose their own skills, you could probably drop the first table and use the intersection table only.

For testimonials, you’ll need to store the text of the testimonial itself, and the id of the user it belongs to. Optional stuff might include publishing date, who authored the testimonial, and so forth.