Posted by bhosmer on January 13, 2012 at 10:47am
Start:
2012-01-24 18:30 - 20:30 America/New_York Organizers:
Event type:
User group meeting
Join us for a second meetup of the month at Radiant Blue Technologies
This is a secure facility, so you will need to sign in when you arrive and when you leave.
We will discuss "Your goto modules" as well as other topics.
Use the signup feature so that I know how many people to expect please.
Comments
Maggie: Here are some ideas
Maggie: Here are some ideas to get started with your question about which modules do you use everyday: http://imagexmedia.com/blog/2012/1/imagex-media-top-ten-modules-and-them...
https://github.com/benhosmer/Ben-s-Drush-Make
I'll talk about using Drush Make to build a new Drupal site with one command.
new day and location
During our Cocoa meetup last night, we decided to continue having twice-monthly meetups in Brevard: one in Cocoa Village (2nd Thursday of the month), and one in Melbourne (4th Tuesday of the month). Hopefully this will allow us to maximize participation.
-mike
Here is another list that I
Here is another list that I think Mike talked about yesterday: http://www.digett.com/blog/01/04/2012/digetts-favorite-drupal-7-contrib-...
Thanks for module list
Thanks Ben, for this additional list of recommended module. We are just finalizing our starting list now so it's very timely. Also I see this site recommends Adaptive Theme which is the one we have been using. Does anyone have comparison data between Adaptive and Omega... it seems both are "responsive" (mobile-friendly).
If you're looking for
If you're looking for responsiveness, look no further than Omega. I have it in my make file.
and another...
And here's a brand new list as well...
http://imagexmedia.com/blog/2012/1/imagex-media-top-ten-modules-and-them...
-mike
Our tentative Module ist
We didn't get to the recommended module discussion last night and we are trying to build our site today. So I built a spreadsheet based on inputs from a few places including Mike's and Ben's suggestions and this is what we came up with as a tentative starter list. Does anyone have any other recommendations or caveats about any of these?
Admin Menu
Backup & Migrate
Captcha
CKEditor
Colorbox
Context
Ctools
Date
Delta (this assumes we switch from Adaptive to Omega)
Devel (do we need this if we aren't writing code?)
Display Suite
Entity Reference
Features
Field Group
Field Permissions
File Field Sources
Global Redirect
Google +1
IMCE
Insert
Link
Metatag
NodeQueue
Omega (this assumes we switch from Adaptive to Omega)
Omega Tools (this assumes we switch from Adaptive to Omega)
PathAuto
Relations
SMTP
Taxonomy Manager
Token
Views
Webform
I wanted to add dragndrop but it looks like it's not D7 yet?
Also I have questions about CCL Custom Contextual Links. I'm not sure but it seems like this is one that can help simplify things for content providers which is a big issue for us??? Is Workbench also useful for this - maybe both these are future needs.
Admin Menu Backup &
You may want to be careful about adding too may modules. Make sure you have requirements for them before you add them. Workbench can be useful for a content creator to not have to wade through all of the extra administrative things in the menu.
Sign Up
IMO, any discussion of Date + Calendar should include SignUp module http://drupal.org/project/signup. A great module -- if only for the automated event reminder emails, to anon or auth users. Quite a few extension contrib modules too. All looking good for D7.
I'd call that a Calendar package....triumverate. (But, can be used without calendar.)
Tyme
Thanks for the tip - it's on the phase 2 list. I enjoyed looking at your site! still puzzling out all the semantics.
good point
Ben makes a good point, so I'll ride his coattails a bit.
Don't think about adding modules, think about adding "use cases", and your module list will fall out of that. As Admiral Akbar says, "It's a trap!" ...to start enabling modules on your site without a clear use case for each one. Enable them as you need them as you're building out use cases, not the other way around.
-mike
P.S. I've been wanting to use that quote on drupal.org for quite some time now. Thank you.
System concept and Requirements
well, I think we have a pretty good concept of our requirements but definitely need to formalize them. Hopefully my systems engineering skills are still at least semi-functional. And I'd really welcome an opportunity to review our requirements with you gurus once I do get them formalized. But I think everything in our list is important to our IOC (Initial Operating Capability or our first use case) and would be needed to get any traction. (maybe it's odd that it's an enterprise that will grow from the website as opposed to a website about an existing enterprise so there is more than the usual chicken/egg scramble) Maybe it is too much to start with - but in previous versions I found myself struggling and jury-rigging things where I later found out "there's a module for that". So it's hard to find the balance - but there are over a hundred modules on the list that we pared down to just these few dozen. But you can see from our initial list that SEO is a big priority, as is the ability for people to contribute (crowd sourcing, forum, wiki-like behavior, multiple blogs) as well as ease of entry and ease of finding and connecting data.
@marguerite A few years ago
@marguerite
A few years ago Mediacurrent released a white paper that tries to help organizations "Drupalize" their requirements. There are some questionnaires and planning documents that might be helpful. Also, I wrote an accompanying blog post that provides a little more context around why its difficult to scope and estimate the level of effort around Drupal projects (link to white paper is included):
http://www.mediacurrent.com/blog/mediacurrent-releases-free-best-practic...
Overall, its great to see that you understand the value of solid planning and well-defined specs - this will save your organization a lot of time and money in the end.
Cheers,
Dave
Mediacurrent
Enterprise-Class Drupal
thanks! That looks like a terrific document and right up my alley (in real - or maybe I should say previous - life my specialty is Enterprise Information Architect/Systems Engineer). As we know all the leverage happens up front and rework cost increases exponentially as things get more complex. No matter how agile you are, water still flows downhill. I'll comment more after I've read it and might even be able to contribute something after I get more proficient with Drupal.
BTW my starting point for the list was Jay's Top 50. So kudos to Mediacurrent for that too.
ATMono vs Omega theme
OK - has anyone used both ATMono and Omega and/or have opinion? We have already purchased and used ATMono and like it. Omega sounds more complicated/flexible to set up. Maybe this is not the best place to ask this question.
The important thing to
The important thing to remember with Omega, is that it is not a drop-in theme. It is a theme framework. If you are looking to create your own custom theme, go with Omega because of the built-in responsiveness and mobile-first design.
I am a huge Omega fan.
If you are just looking for a drop-in theme with responsiveness built in, I am not sure where to direct you.
Generally going with a paid theme you definitely know what you are getting and get some support included with the price of the theme.
Don't worry about asking questions here, this is what this group is for!
meetup reminder
Don't forget that the Melbourne Drupal Meetup is tomorrow night, Tuesday, January 24 at 6:30pm at Radiant Blue in downtown Melbourne!
-mike