Application design opinions... What is the best way?

Hi,

I am making a small application for a friend, to help her update her website. The website is a very simple one, using a menu (table of links) in one frame, and the content in the other frame. The content consists merely of pictures, with some information (text) below each picture.

Because my friend has no clue how to change her website (let alone upload it and the images to the right FTP folders), I decided to make an application that does that for her.

I had decided on the following design, but now I'm having second thoughts whether or not it's a good idea:
1. I use a Database to store the information and path to each picture.
2. I generate the content HTML files completely from scratch every time an update is required, retrieving the image path + info from the database and generating the correct HTML code from it.
3. I save the HTML files and upload them + all the images they use to the FTP.

She can now add, remove and/or edit any items in her website, in each category, and it works fine at the moment. But there are a few problems:

1. When she decides to remove a picture (from the database), the actual image will stay on the FTP server. She only has a maximum of 100 MB capacity, so having 50 unused images on there is not very efficient.
To remedy this, I simply remove all the images before uploading the new website, so there will only ever exist the current images.

2. When her site gets larger, the amount of images will increase, possibly to about 80 MB. I don't think she'll want to wait for 80 MB in pictures to upload when she only changed a typo in one of the picture's descriptions...
In the past, the whole site is uploaded at once without considering which changes were made, so that wasn't very good. I decided to keep track of which categories were changed, and only upload the categories that have been changed. This reduces the amount of images to upload, but there still could be around 10 MB in a single category, which is acceptable but still not ideal.

3. The images she has chosen have to remain on her computer, because they are uploaded again every time she updates here site. If she removes them, they will not be found and cannot be uploaded. Now, the images would still be on the server, so there really isn't any need for her to keep the images. But, due to point 1, they get deleted, so I don't have them anymore.


I can think of a few more things that aren't very good, but I'll stop now (the post is long enough as it is).

Can anyone recommend a better way to go about this?

Thanks!

It would be far easier to teach your friend how to use an ftp program and a little html.

One way to do this might be to build the structure of the website (i.e. the file layout) in a temp folder on her machine. Then connect to the site and compare the structure, any files on the site that are not in the directory are cleaned up from the server. Any files that are different on her machine are uploaded to the site either overwriting or creating a new file.