1) The Senate, to the best of my knowledge, is still using Drupal 6 of the main website and used Drupal 7 for a microsite this summer, although at the time of my leaving they were looking to upgrade to Drupal 7. All projects I have worked on since leaving the Senate have been Drupal 7 projects.
2) I personally have been using Drupal for almost two years.
3) As with Sheldon, I was not part of the team that chose to go with Drupal initially.
4) To the best of my knowledge, the Senate uses Drupal to run their main web property and some micro sites. Personally, all web properties I own or work on are run off of Drupal.
5) As was previously mentioned, I was not part of the initial team, but if we had to choose a new platform going forward, I would.
6) To me, Drupal's great strengths are its community, breadth and quality of free contributed modules, and ease of extensibility. Weaknesses include a medium to high learning curve for developers and content editors, at least out of the box. The learning curve for content editors can be partially alleviated thanks to contributed modules, themes, and development work.
7) I personally have used Wordpress and, while the administrative interface is very nice, it is very hard to build advanced functionality for and most of the community seemed to revolve around paid extensions or themes instead of the open source mindset that Drupal revolves around.
8) I never had any direct interaction with content contributors at the Senate, but the microsite that was created using Drupal 7 allowed people with no training to add content to the site and that project through a, for lack of a better term, sculpted content editing interface. That was fairly successful. The key for ease of acceptance is a good content creation UI and powerful tools. With work, both are achievable within Drupal, but do not come as out-of-the-box functionality.
~ Sam Richard
On Tuesday, November 15, 2011 at 1:47 PM, Sweeney Bill C wrote:
> My name is Bill Sweeney and I'm a Digital Developer for State of Oregon, Legislative Administration Information Services. We're in the process of transitioning Oregon's Legislative Website from a mostly static site to a site utilizing a Web Content Management System. We're considering using the open source Drupal solution for this purpose. I understand that you are currently using Drupal as your WCMS, and I’m hoping you would be willing to share some information regarding your experience with this system. Among our requirements is need to allow content contributors, legislators mainly, the ability to maintain their respective content. Any information you could offer would be helpful!
> Thank you very much for your time and consideration. Please feel free to contact me with any questions you may have.
> Best Regards, -Bill Sweeney
> 1. What version of Drupal are you currently using?
> 2. How long have you used Drupal?
> 3. What other software did you explore and what made you choose Drupal over the others?
> 4. How do you currently use Drupal?
> 5. In retrospect, would you choose Drupal for this purpose again?
> 6. What features stand out as Drupal's strengths and weakness?
> 7. Have you ever used other Web Content Management Systems (WCMS)? If so, why did you change to Drupal?
> 8. What is the level of acceptance from your content contributors regarding Drupal's ease of use?
> Bill Sweeney, Digital Communications Developer
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.