[Web4lib] Drupal 7

Mon Apr 18 08:52:30 EDT 2011

Jorge,

>From a post I wrote back in January (
http://beanworks.clbean.com/2011/01/drupal-and-other-distractions/):

> The terms usually associated with Drupal are “steep learning curve.”  I was
> the only one in my organization who even knew what Drupal is, although some
> seemed to have a vague concept of “content management system.” But I
> recommended we go with Drupal over other options because of (1) it’s
> potential, (2) the growing and active group of libraries with Drupal, and
> (3) because it’s the CMS I was most familiar with.  Looking back, I’d have
> done some things differently (isn’t that always the case?), but I would
> still choose Drupal. We haven’t fully taken advantage of all Drupal’s
> potential, but that’s only because I decided to hold off development of more
> advanced features until after we completed the initial project.
>

To elaborate:
(1) it's potential:  while CMS's like Wordpress and Joomla are easier, the
tradeoff is the limitations on extending them and implementing
library-specific things.  Drupal's community involvement and willingness to
share is impressive (see a previous post:
http://beanworks.clbean.com/2008/10/drupal-google-calendars-and-cool-people/
)
(2) the growing and active group of libraries with Drupal: See #1 above, but
also, I like to keep in mind the future, as in, what would happen if I
weren't here tomorrow to manage the CMS for my organization?  Would there be
people who could continue what we've done?  How hard would it be to get
someone who knows enough of the CMS to continue to manage and develop it?
Drupal isn't easy, but there are a lot more people in the library field who
know Drupal than any other single CMS, so the likelihood of finding someone
who knows something about Drupal is greater.  There is also a lot more
training available in any given location to learn about Drupal.
(3) it’s the CMS I was most familiar with.  I have worked with Wordpress and
Joomla, but I wasn't as familiar with either of those as I was with Drupal,
and we needed to get something up fairly quickly.  But this wasn't the
primary reason; #1 and #2 were.

Hope this helps,
Carol

On Sun, Apr 17, 2011 at 4:28 PM, Jorge Biquez <jbiquez at icsmx.com> wrote:

> Hello.
>
> I have been working with D6 and studying the differences on D7. One
> question came to my mind and I hope it does not sound too stupid....
>
> What are the reasons , with all other options around, that you decide to
> continue working with Drupal?
>
> Yes, I know we all know could have other solutions working from previous
> versions. NO, the question is more profound. What do you see or found in
> Drupal that make you decide continue working with it?
>
> The question is jut in the effort of learning.
>
> For example. A friend told me. Why are you still with Drupal if there are
> other solutions like concrete5 for example? ( <http://www.concrete5.org/>
> http://www.concrete5.org  )
>
> What are your reasons?
>
> I'd love to hear your comments.
>
> Take care all.
>
> Jorge Biquez
>
>
>
> At 11:28 a.m. 08/03/2011, you wrote:
>
>> I did a basic analysis of a couple of D6 sites I work on to get a sense of
>> the status of modules we're currently using on the two sites and the
>> availability of those modules (or functional replacements) in D7.  While a
>> good portion of the D6 modules have D7 versions that are GA release, alpha,
>> beta, or dev releases and in some cases there is either equivalent
>> functionality in another D7 module or in the D7 core, there are still quite
>> a few modules for which there is not an existing migration path.  One of the
>> major roadblocks (for us) is the lack of a D7 version of the back_reference
>> and conditional_fields modules.
>>
>> -----Original Message-----
>> From: web4lib-bounces at webjunction.org [mailto:
>> web4lib-bounces at webjunction.org] On Behalf Of Cary Gordon
>> Sent: Tuesday, March 08, 2011 12:26 AM
>> To: Maida Scott
>> Cc: Web4lib at webjunction.org
>> Subject: Re: [Web4lib] Drupal 7
>>
>> We have started to build sites in Drupal 7. Our test is whether we
>> believe that the modules required by the site will be available by the
>> time the site is scheduled to go live. On sites with a six month to
>> launch horizon, we feel that most of the "big" pieces will be in place
>> and we can begin development with dev modules. With a 60 day timeline,
>> we will stick to D6 unless every module we need is ready for
>> production now, or we can launch without full functionality.
>>
>> Exceptions include, on the go side, clients with the resources to take
>> a module over the hump, if needed, and on the no-go side, sites that
>> require i18n.
>>
>> Cary
>>
>> On Fri, Mar 4, 2011 at 4:59 PM, Maida Scott
>> <Maida.Scott at pueblolibrary.org> wrote:
>> > Since our redesign efforts fell in line with the lastest release of
>> > Drupal, I made the decision to go ahead with Drupal 7, to avoid the
>> > headache of upgrading later.
>> >
>> > Is anyone else out there using/upgrading to Drupal 7?
>> >
>> > Maida
>> > ________________________________
>> > Maida Carpio Scott
>> > Web Administrator
>> > Pueblo City-County Library District
>> >
>> >
>> > _______________________________________________
>> > Web4lib mailing list
>> > Web4lib at webjunction.org
>> > http://lists.webjunction.org/web4lib/
>> >
>> >
>>
>>
>>
>> --
>> Cary Gordon
>> The Cherry Hill Company
>> http://chillco.com
>>
>>
>> _______________________________________________
>> Web4lib mailing list
>> Web4lib at webjunction.org
>> http://lists.webjunction.org/web4lib/
>>
>>
>>
>> _______________________________________________
>> Web4lib mailing list
>> Web4lib at webjunction.org
>> http://lists.webjunction.org/web4lib/
>>
>
> _______________________________________________
> Web4lib mailing list
> Web4lib at webjunction.org
> http://lists.webjunction.org/web4lib/
>
>

-- 
Carol Bean
beanworks at gmail.com