http://code.google.com/p/google-highly-open-participation-drupal/issues/...
The imagecache module is a very cool module that manipulates images
uploaded in various ways. It is widely used and very powerful but is not
very intuitive to configure and use. The existing documentation is very
sparse and needs to be expanded and improved.
This task will require installing and learning to use the imagecache module
and reading the existing documentation. Then write step-by-step
instructions, including screenshots, for three imagecache tasks:
1. how to configure presets
2. how to set a CCK image field to display different size images and
3. how to manually call the theme_imagecache function in a theme
The task will be complete upon adding the new documentation to the handbook
page as well as creating a documentation patch to include with the module.
Resources:
* Project page: drupal.org/project/imagecache
* Handbook page: http://drupal.org/node/163561
Estimated time:
3-4 days
Comments
Comment #1
webchickComment #2
add1sun commentedClaimed by alexandrebfarias. Don't know drupal.org username.
Comment #3
Etinin commentedThis is my Drupal username BTW.
Comment #5
Etinin commentedComment #6
dopry commented@etinin, feel free to ask me anything you need to know. You can catch me via my contact form or irc.
I would personally like to see this module better documented. I've failed in most cases to explain how it works, to the point that I've given up trying.
Comment #7
Etinin commentedI've attached my work, is there anything else I should add?
The file only contains
<img>tags, I didn't break lines withas I think that's not necessary for Drupal.
Comment #8
Etinin commentedComment #9
add1sun commentedRock! This is great stuff Etinin. I've got a few tweakish things:
1. I would mention up in the first paragraph that you can use imagecache with any images uploaded to Drupal, so you can use it with Image module as well as normally uploaded images using the Upload module but the most common way to use it is with CCK and Imagefield.
2. I would move the sentence about needing CCK and Imagefield down to when you start the demonstration itself. You should mention all of the prerequisites, so it assumes you have already installed and enabled imagecache, CCK and imagefield, as well as also having already added an imagefield to a content type.
3. You should probably tell them to click the Update preset button after each step (select action and fill in dimensions) just to be sure they don't get lost.
4. With the content type section at "To accomplish that, first go to Administer>Content Management." I would then add, "click the configure link for the content type with you imagefield" or something like that to get them from the content type listing to the screen with Display fields on it.
5. On the final results screenshots I would add a little title to each pic so they know which one is the teaser view and which is the full.
6. The last thing I'd do, is for the theme function bit at least have a bullet list explaining what each of the parameters is. e.g.
print theme('imagecache', $ruleset_namespace, $image['filepath'], $alt, $title, $attributes);$ruleset_namespaceis the imagecache preset name$image['filepath']... (this one you probably need to help folks out with maybe how that can find out what the filepath is)All in all this is already going to be a great help to a LOT of people.
Comment #10
quicksketchThis looks great! Technically a-okay, no problems that I noticed on a read-through.
add1sun most of the issues I found also. In addition:
In addition to telling users when to click "Update preset", also be sure to mention clicking "Create preset" after filling in a label. Which buttons to push seem to throw a lot of people off (part of the UI's fault admittedly). Be sure to include the "Update preset" button in your screenshot also.
A small nit-pick that the path definition should be consistent,
Administer>Content Managementshould beAdminister -> Content Managementlike the example earlier in the file.Thank you Etinin!
Comment #11
Etinin commentedHi, thanks for the feedback. I've done the changes as requested.
Comment #12
quicksketchAbsolutely fantastic! One last tiny detail: let's use
$presetin the example rather than$ruleset_namespace"ruleset" isn't part of the imagecache vocabulary and we'll probably phase out "Namespace" from the interface anyway. Preset is the word we'll be using in the future. Thanks!Add1sun, can we get this added as a handbook page? (I'm intentionally not on the docs team).
Comment #13
quicksketchWell webchick quickly solved my lack of documentation-team membership. ;)
I updated the existing imagecache docs page at http://drupal.org/node/163561, this is 20x better than what we had. I also update the project page with the documentation link, as it's definitely going to help a lot. Thanks again!
Comment #14
webchick@Etinin: Great job! Could you please upload your final work to http://code.google.com/p/google-highly-open-participation-drupal/issues/... and we'll mark this sucker "Closed" so you can do an awesome job on a new task. :D
Comment #15
dopry commentedGarsh... and now I'm getting close to releasing 2.x, with a brand new UI :), and additional installation requirements... Caffiene and I are a bad combination.
Comment #16
dopry commentedYou work is awesome I really appreciate it... I'll use it as a model for building the docs for the 2.x release...
Comment #17
quicksketchWe can make another task for making a new 2.x documentation page then :D
Comment #18
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.