Should your web developer manage your image portfolio? Assumptions in this area cause frustration for both the developer and the website owner. In my opinion, for small sites, this is a good task to assign to an in-house Content Manager.
PROBLEM 1: WHAT ARE THESE PHOTOS OF?
If your web developer is an outside contractor or firm, the developer doesn’t know your products the way someone in-house would know them.
The developer doesn’t know when products come and go.
The developer doesn’t know when people who might be in the photos come and go.
The developer may not even know what’s in the photos, especially if there is a series of photos with minor differences.
PROBLEM 2: NAMING, TAGGING, CATEGORIZING
1. Every developer has a mirthless laugh with other developers about that time that a client gave you photos in a shoebox, or sent email after email of zipped files of photos with duplicates and no information, etc.
2. Images are a business asset. It took time to take them. But, like most other business assets, they need maintenance.
3. They need searchable file names.
4. They need keyword tags.
5. They need to be categorized major categories that will make them available to all departments
6. They may need model releases
7. This is content management, not development.
Hint: a content manager is not as expensive as a programmer.
PROBLEM 3: WHAT’S THE HOLD UP?
When the developer has to find, name, label, crop, etc. the images, the actual work that the developer is supposed to do is held up. This makes for a very difficult project for everyone.
There are a number of image management tools available. If you have the Adobe Suite, you probably already have Bridge. Or, you may have Lightroom. If you have hundreds or thousands of images and you don’t have a management tool, you might want to check out this resource.