Hi,
I'm looking for feedback on a set of recommendations I'm putting together for a Boston-area non-profit.
The non-profit takes volunteers from local corporations and matches them with local non-profits on short-term projects--for example, past projects have created or upgraded static websites. The non-profit would like to move towards a cms and after doing some of their own initial research, asked me to look into Drupal.
I've spent quite a bit of time looking at FAQs, blogs, and docs as well as installing a local dev site. As I'm compiling and finalizing the recommendations/guidelines and developing a base/starter profile (db backup and files); it would be great to get some community feedback and advice.
If anyone is interested, I can post my outline or email/attach a document.
Thanks,
Tim
Comments
Please do post
I know Grassroots.org is interested in doing the same thing with the volunteers it matches up to do web development, but making so volunteers can set something up with Drupal, and the arrangement will be sustainable for all concerned, still needed some work.
benjamin, Agaric Design Collective
benjamin, agaric
cool, do you have any contacts?
Thanks for the thoughts. I checked out their website, it seems like a neat organization--ambitious :). If you have any contacts there I would be interested in sharing what I have and/or borrowing from them.
Loudon & Company Consulting
draft recommendations
Assumptions: 4-5 project members working ~5 hrs/wk for ~6 months. Project scope/outline, discovery, etc to be previously completed by the non-profit--project team's focus to be on execution. Project team members to be skilled technically--not necessarily with php, javascript, css, etc; although a working knowledge of html can be expected (part of the project appeal is to allow volunteers to branch out in new areas).
Main Objective: a website that a part-time, unskilled non-profit staff member could easily maintain and support.
Current Strategy:
develop a set of roles for the project team and non-profit staffers that minimize the options/complexity of Drupal.
extend the Drupal core with a standard set of modules
create a base theme--basically complete but with placeholders/notes for masthead, background color, etc
install 5 other themes for less css-savvy teams to chose from
leaning away from coding: leaning towards config + more pr/marketing (i.e., focus on content)
Interested In:
suggestions for modules
feasibility of custom theming for the project team
feasibility of custom module development for the project team
thoughts on custom coding for the project team
thoughts on dropdown menus--seem to be a standard request
5.x vs. 6.x
words of wisdom and sage advice :)
thanks
-tim
Loudon & Company Consulting