As has been mentioned many times, you're trying to find a solution for a problem you can't identify. What you need to do is think about you would feel is missing and how much you will miss it in the future.
My professional experiences have all been with companies where the end goal would require massive growth at some point. A twelve person company doesn't need a whole lot. The people working together are usually pretty intimately familiar with each other and data organization isn't very critical. If the long term plan isn't to stay small, but to eventually grow to hundreds or thousands or employees, keep that in mind when examining your needs. When everyone isn't on a first name basis and/or working in the same office, sharing data becomes a chore is not properly done. A wiki (or CMS) is a good thing for a dozen people but of absolute importance to a larger organization. Why not start one now?
Sticking with my theme of eventually having a large organization, the ability to find people is an often overlooked need until it's too late. Consider having a user directory with pictures, contact information and work group data. When doing this, make sure it allows for editing by the user as people are likely to link out to their projects and documents when given the chance. Also, having a single point of management for vital information (like when phone numbers change) means it can be an administrative nightmare.
Forums and blogs! Email is great but it's not always the best way to propose ideas and have random discussions. Forums allow for much better data persistence (usually only an admin can remove a thread) and give people a place to have more "off topic" banter. While I don't personally have much of a use for a blog, many people find them to be useful scratch pads. At the last place I worked, I occasionally updated a blog with tips and tricks, software patches for third party tools and random tech bugs I'd dealt with.
Whatever you do, make sure you have a central point of access. A unified search component (like a search appliance) is key to making sure that, when you have the date, you can find it. People are good at remembering a single point of entry but less so at remembering an ever growing list. All of these resources are useful but, unless you have a simple way to get to them/find data, they won't get nearly the utilization they could.
Lastly, if you do this all on a single host, you're destined for pain. I don't know anything about the Drobo (and I don't feel like looking it up), so I have no idea if it's running in a redundant state. Regardless, the fact that you have a single machine attached means that, if that box has a problem, all of this is for nothing. At the very least, you should get a second machine with a mirror of any resources/sites you create, so you're not left dead in the water if it fails. I'd actually recommend three, so you can have two in a production swappable state and one where you can test new software and upgrades before making them live.
Good luck.