greedy for modules
I've just been through some of the modules, earmarking
ones that would probably be useful on a school website.
Does this list look over the top?
3rd party
charts
flash gallery
flash video
video filter
foto notes
gallery
JsMath
moodle course list
page ear
Community
advanced forum
multisite manager
kudos
privatemsg
subscriptions
imagefield
imagecache
inagefield crop
imagefieldgallery
Administration
automated logout
AES encryption
apply for a role
backup and migrate
comment closer
custom (form) destination
download count
email change confirmation
flag content
membership (temporary timed)
site documentation
string over-rides
taxonomy delegate
taxonomy manager
translation overview
transliteration
userplus
Content
Audio
Bibliography Module
Checkbox Validate
Contact Link
Content Profile
Content Taxonomy CCK
Content Templates
date
Document Import API
Email field CCK
Embedded Media Field
faq
faq ask
FeedAPI
forum access
G2 Glossary
htmLawed
Internationalization
job posting
link CCK
modr8
Meta tags
Node Relativity
Outline
Scheduler
STORM
Content Display
Clickpath
E-Publish
External Links
Flashnode
Flexifilter
Form Defaults
Front Page
GeSHi Filter
Header image
Hovertips and Clicktips
Image Assist
Indexpage
Menu Breadcrumb
Multipage form controller
Quick Tabs
Remove Upload Enclosures
Recent Changes
Simplelist
Slideshow Creator
smileys
User Stats
I've still got to weed out a few which overlap function, but even still, the list
looks very long to me, considering I've not finished going through the modules
yet?
Should I be restricting myself to 'must have' modules only, or is anyone else's
module list like this on a production site?
Cheers.
That's a LOT of modules!
There's no single correct answer to your question. How many modules you can handle will depend on how well they happen to work with each other, and your server's capability. But I think most any experienced Drupaler will see the length of that list as worrisome.
Fortunately, the solution is easy too: just pick the small handful of most vital modules; install, configure, and learn those. If things are still working well, move on to the next few important ones, and make sure things still work well. And so on. You'll probably find that you've implemented plenty of good features, before you get to the point where additional, less-important modules start causing trouble.
A little at a time should do it!
--------
Easy Drupal Admin Manual, Drupal questions, other stuff for the newbie: http://www.drupalace.com
Depends ......
It is easy to to go over the top when planning a Drupal site especially with no experience of building one. Each module takes time to add, get working and then theme, each module takes up memory on your server, some don't play nicely with others - so do you have the time, patience, ability, server capabilities to build such a massive site? Are you being paid or is this for love? How long do you have to build this siite?
I find the best way to go is to build the basics first then add the fancy bits as you go as you have time etc. Have a test site that you can experiment with.
As you build it you will find what you need and what you can live without and what you can be bothered adding.
gpdinoz
"Everything should be made as simple as possible, but not simpler." - Albert Einstein
OK, thanks for the
OK, thanks for the replies.
I thought I was being a bit to greedy!
Cheers.
Tail wagging the dog
The point of the other posters is that you need to find a need first, then a solution. It's never a good idea to find a solution and then try to create a need.
NancyDru (formerly Nancy W. until I got married to Drupal)