Developing modules for a photo agency
Hi! (Sorry if this is was already posted - but I don't think it was.) I am (slowly) developing a site for a small independent photo agency. I feel that a lot of the functionality that I need is already in Drupal core and contrib, but there are certain points that I need to address, probably through developing a few new modules. (Theming is obviously an important part of it too, but that's another story.) I have a few ideas on how to implement the functionality that I need and some choices to make, so I'm hoping for some comments and wisdom from the community. Also, if someone else is already doing or has done anything like this, that would be good to know. Hopefully this could turn into a solution that other picture agencies can use, or even better, a set of general modules that can be used in many different contexts. In short, I need too look at: 1) the handling of large image files and the quality of resized images, 2) a specific image search function, and 3) ecommerce integration. To keep this message short I'm saving the details, but I made a post in the forums describing my thoughts so far. If your'e interested or have experience in any of these areas - please take a look! http://drupal.org/node/75282 Thanks! /Hannes - zoo33
Op woensdag 26 juli 2006 20:24, schreef Hannes Lilljequist:
To keep this message short I'm saving the details, but I made a post in the forums describing my thoughts so far. If your'e interested or have experience in any of these areas - please take a look!
FWIW: I developed newsphoto approx half a year ago. http://newsphoto.nl/. We have discontinued the site (last content from months ago), because Drupal was not a good candidate to suit our needs. After investigation, we bought a commercial image shop tool, which is being developed now to replace the Drupal at newsphoto.nl. -- [ Bèr Kessels | Drupal services www.webschuur.com ]
On 27 Jul 2006, at 00:19, Bèr Kessels wrote:
To keep this message short I'm saving the details, but I made a post in the forums describing my thoughts so far. If your'e interested or have experience in any of these areas - please take a look!
FWIW: I developed newsphoto approx half a year ago. http:// newsphoto.nl/. We have discontinued the site (last content from months ago), because Drupal was not a good candidate to suit our needs. After investigation, we bought a commercial image shop tool, which is being developed now to replace the Drupal at newsphoto.nl.
It would help if you'd explain why you threw out Drupal. Without that information, your e-mail has _no_ added value. So care to elaborate? -- Dries Buytaert :: http://www.buytaert.net/
27 jul 2006 kl. 09.02 skrev Dries Buytaert:
FWIW: I developed newsphoto approx half a year ago. http:// newsphoto.nl/. We have discontinued the site (last content from months ago), because Drupal was not a good candidate to suit our needs. After investigation, we bought a commercial image shop tool, which is being developed now to replace the Drupal at newsphoto.nl.
It would help if you'd explain why you threw out Drupal. Without that information, your e-mail has _no_ added value. So care to elaborate?
I don't feel it would be that hard to extend or customize Drupal's image features into something that fits my needs (#1 & #2 in my original post). What I'm feeling a bit overwhelmed with right now is the whole ordering/ecommerce part. So obviously I too am interested in why Drupal didn't suit your needs. /Hannes
Op donderdag 27 juli 2006 09:02, schreef Dries Buytaert:
It would help if you'd explain why you threw out Drupal. Without that information, your e-mail has _no_ added value. So care to elaborate?
Off course. I posted the story on my blog, because it has become a rather lengthy story :) http://webschuur.com/node/641 Bèr
28 jul 2006 kl. 11.18 skrev Bèr Kessels:
Op donderdag 27 juli 2006 09:02, schreef Dries Buytaert:
It would help if you'd explain why you threw out Drupal. Without that information, your e-mail has _no_ added value. So care to elaborate?
Off course.
I posted the story on my blog, because it has become a rather lengthy story :)
Bèr
Those are good points. Thanks for sharing your experiences. There's bound to be some complexity from using a general tool for a specific task rather than a tool that is designed from the ground up for one (or a few) specific task(s). On the other hand, you could take the issues you mention and look at them as Drupal features that need to be more flexible. For example, a setting that controls who can search for users would easily solve one of your issues (is there a feature request for that?). Other issues are trickier, of course. My point is, it's still worthwhile trying to make Drupal an as flexible, modular and generalized CMS as possible. For me I hope using Drupal will be a decent middle course between building something from scratch and buying a readymade solution. /Hannes
Op vrijdag 28 juli 2006 14:15, schreef Hannes Lilljequist:
For example, a setting that controls who can search for users would easily solve one of your issues (is there a feature request for that?). Other issues are trickier, of course. My point is, it's still worthwhile trying to make Drupal an as flexible, modular and generalized CMS as possible.
Yup. Agreed. And I try to make at least a few of such patches per project. One of my latest ones was the -for me- annoying part that core contact module forced you to have user-contact forms if all you wanted was a general one. A patch for that cost me less then 30 mins and went into core within hours. Fact remains that during development of a more complex site, one that is meant to fit withing pre-set boundaries (Programs of Demands, strict time plannings etc etc) you cannot afford to do this for each and every thing you meet across your road. You will get to a point where "enough is enough" and you are forced to live with choices other (module) developers made for you. Again: not a Drupal issue, but a general one, that comes with any (semi) ready made solution.
For me I hope using Drupal will be a decent middle course between building something from scratch and buying a readymade solution.
Yes. But I would say that Drupal leans more towards the readymade one then towards the "build from scratch". It is, as I mention a couple of times, the most flexible of the readymade, but it certainly comes with a few of the unexpected "choises made for you". What?? We need 20 development hours only to allow a person to log in directly, without registering? That is unacceptible, we must release tomorrow! Okay, there are solutions for this rather silly example, and fact is that someone who needs to release tomorrow should have done his homework better. But we all know our examples of where we fought Drupal for days because our requirements (or a stubborn client) wanted something that Drupal refused to do. Bèr
participants (3)
-
Bèr Kessels -
Dries Buytaert -
Hannes Lilljequist