Last weekend three of us from Cocomore attended to DrupalCamp Spain 2014. This year it was held in the beautiful city of Valencia, at the East Coast of Spain, full of magnificent buildings and the land of Paella and Horchata. Because we know of the importance of these events, this Drupalcamp was sponsored by Cocomore.
Thousands of Drupalers will be covering in Austin with one goal in mind, to live and breathe Drupal. With the success of the DrupalCon Prague 2013 Community Summit, leaders are called to action again to discuss and sprint on important Drupal Community topics.
This week one our OSTraining members was working with the Views module.
They were able to create views, but weren't sure how to improve their design.
In this tutorial, we're going to show you how to apply CSS to your views so you can add both color and width.
Drupal 8's out-of-the-box mobile friendliness creates quite the buzz. "Mobile friendly," "responsive," "squishy" — all words to describe the behavior a site invokes on different devices or different screen sizes. Mobile friendly can also mean content first. From a big screen to a little screen, things look different. Images change sizes, menu items become drop-downs, columns are pushed around to locations that make sense with content being the supreme real-estate. So if Drupal is mobile friendly out of the box that must mean I am 100% good to go with all my websites using Drupal 8. We wish. Drupal 8 is coming along and looking pretty sweet, but it is still Drupal and not a magic unicorn. This blog post is not going to get into the nitty gritty of how responsive websites work, but we're going to take a closer look at how two new core modules can make it easier to build a responsive theme.
I got the chance a while back to speak with Amitai Burstein, CTO of Gizra - a boutique development shop in Tel Aviv creating advanced web applications using Drupal, along with Node.js, Jekyll and other technologies. Amitai is the maintainer of key Drupal modules such as Organic Groups, Message and Entity Reference, and contributes to Drupal core. He showed off Gizra's intriguing solution to content deployment in Drupal in this jam's Drupal Camp session: Zariz. I was impressed! You might be, too.
Per the 2014 Leadership plan, one of the imperatives for the Drupal Association is making Drupal.org a great tool for the Drupal community, building Drupal adoptions and developer satisfaction. One very important part of a great tool is great user support. The speed and ease with which users can get help when they have a problem greatly affects overall experience.
As with many other things on Drupal.org, historically support has been provided by an amazing group of community volunteers with a little help from the Drupal Association staff. Recently the Drupal Association staff had to step in heavily during a few intense times, such as after the security incident last May, when we reset all user passwords. Association staff answered hundreds of support requests, 24 hours a day, over the week following the incident.
What are all the channels where Drupal.org users can get support? There are some old and some new ones:Issue queues
Issue queues, of course, are the main and most important channel. The ones our team members monitor on a constant basis are:
The first step for most of the issue queues is cleaning up the backlog. Recently we had our first issue queue clean up sprint. There were 675 issues in the Webmasters, 200 in the Content and 336 in the Infrastructure queue before the sprint. A group of 11 people — community members and staff — cleaned up about 300 issues total.
We still have lots though (398 in the Webmasters, 179 in the Content, 311 in the Infrastructure) and are planning to organize more sprints like that. The next one will likely take place during DrupalCon Austin.
We want to stress that community involvement is at the heart of the Drupal Project. Although we have increased the staff commitment to support, we do not intend or desire to displace the enthusiastic and productive volunteers who have put so much time and energy into supporting the community. We will continue to work closely with volunteers to ensure that we find the right balance of actions for each of us so that we support and enhance each others efforts.ZenDesk
We first used ZenDesk last May, when lots of people were not able to log in and therefore were not able to open an issue about it. This continues to be a problem. Sometimes people lose access to their Drupal.org account, or they are not able to log in for other reasons. The only way for them to ask for help is create another account and open an issue.
To make this easier for people, we decided to keep the email@example.com email account and increase its use. Our plan is to use ZenDesk only for the cases when people cannot actually log in to the site. All the other requests will be forwarded to the issue queues.IRC
There are a few IRC channels where staff members already hang out and provide support alongside community volunteers: #drupalorg, #drupal-infrastructure, #drupal-association.Twitter
There are two Drupal.org related Twitter accounts @drupal_org and @drupal_infra, which are used to share various Drupal.org news and announcements. They are also used by the community to ask for tips and help related to Drupal.org.Site contact form
We are planning to forward requests from the form to firstname.lastname@example.org. All requests, which are not related to people unable to log in will be forwarded to the issue queues.
If there anything else we’ve missed in terms of support channels, let us know!Metrics
There are a few metrics we are tracking in the Drupal Association related to user support on Drupal.org. We are happy to report that last month average response time in Drupal.org-related issue queues went down from 56.65 hours to 16.82 hours! About 90% of issues received their first response within 48 hours after the issue was published. These are the results of a great work by the community volunteers (dddave, nevets, silverwing, WorldFallz, dman, and many more), Association staff and especially Lizz Trudeau (lizzjoy), who joined our team as a customer support coordinator exactly a month and a few weeks ago.
We already can see positive changes and are not going to stop. We’ll continue to streamline tools and processes, so that community volunteers together with the Drupal Association staff could provide better support for our users and improve these numbers even more.
I had a case recently, where I needed to add custom data to the node display and wanted this data to behave like a field, however the data itself didn't belong to a field. By "behaving like a field" I mean you can that field at node display settings and able to control it's visibility, label and weight by dragging and dropping that field.
So, as you may have undestood, hook_preprocess_node / node_view_alter approach alone wasn't enough.Drupal Tags drupal 7, drupal planet Read on about Adding a custom extra field to entity / node display
To develop the content for the Business Track at Drupalcon Europe this year we're conducting surveys to find the areas in which all Drupal businesses can improve.
I blogged recently about my initial thinking on the theme of the business track at DrupalCon Amsterdam this year.
Janne Kalliola, my co-chair and I decided to conduct a series of surveys to identify the strengths and weaknesses of businesses providing Drupal related services. From the findings we can then provide guidance to those proposing sessions for the conference in Amsterdam later this year.
We're launching 3 surveys — one for clients of Drupal businesses, one for the leaders of the businesses, and one for the staff of the businesses.
We'd really appreciate you filling in the survey that relates to you, and letting others know about this blog post so they can choose the survey that relates to them:
The results are anonymous, and aggregated data will be published. Act quickly, the surveys close on the 28th of May.
If you have any questions about the survey you can contact me at email@example.com.
The DrupalCon Amsterdam Drupal Business Track Team
Steve Parks, Wunderroot
Janne Kalliola, Exove
As a front-end developer for acquia.com, I've had lots of fun and challenging design requests come my way. Most recently I was tasked with swapping out the static homepage graphic with a full-width, responsive slideshow banner that can also be tested and personalized using Acquia Lift.
After a long 8 months break in the article series, we are back to talk about configuration translation basics. Why the long break? Well, both the configuration and content system was in heavy development with changes and I did not want to get you content that would be quickly outdated. Hopefully now it is safer to talk about what is going to end up in Drupal 8 for these systems. If not, well, then I’m sorry. We’ll cover configuration first because that is more baked.The Drupal 8 configuration system is a boon for language
As I wrote in the previous article in the series, configuration is now encompassing lots of settings that were variables or used custom settings storage in Drupal 7. The biggest value for non-English and multilingual sites in Drupal 8 of the configuration changes is that now a common system is used to manage your site name, email text settings through to views, field settings, entity form displays, etc. We can introduce language and translation support in a way that modules will need to plan with. It is not just an optional contributed add-on but a core feature.
In this post, I continue my series on how to override Open Framework's default styles to get a more custom look-and-feel on your site. Last time we looked at how to override our block styles, sidebar menus, and region styles. Today I'm going to share how to test for and override responsive styles on your site.
"It´s one of those modules that when you start off with Drupal and you discover a little bit down the road, it opens up a world to you."
- Stephen Cross | Talking Drupal #013
The quote pretty much explains the Rules module in one sentence. Are you familiar with Rules? Are you already using it?
You certainly heard about Wolfgang Ziegler aka fago - the Rules module creator. As he sums it up: "For the popular open source CMS Drupal, the Rules extension module makes it feasible for users to configure reactions on a high level without requiring any programming expertise."
This past weekend I got a chance to attend the first ever Drupal Camp in Moldova - Moldcamp. It was also the first Drupal event I attended. Propeople was one of the main sponsors and together with all my colleagues, both developers and PMs, we were happy to be a part of this big step for the local IT community. Our best developers from Moldova and Ukraine offices did their best in preparing keynotes and we were all excited to have useful fun together.
I dropped in to different sessions during the two days, but the two that appealed most to me both happened in the first day - these were Radu Trifan’s ThemeSnap case study and Viktor Levandovsky’s keynote on selling Drupal.ThemeSnap case study
Radu Trifan started with comparing two business models - Agency (custom development for every client) vs. Themes (develop once, iterate and sell to different clients). Obviously, he was insistent on convincing us that the second option is much better than the first, bringing more arguments in it’s favor and trying to distill all that could be against.
His case study compared side-by-side major theme marketplaces like ThemeForest, MojoThemes, CreativeMarket and ThemeSnap. He states that ThemeSnap has major advantages over the competitors in giving the developer more control over the pricing and packaging of the products he wants to sell. This includes features missing at the other marketplaces, one of them being the ability to buy a subscription to an author’s products.
Radu also talked about the life cycle of a theme. According to his data, the average time you can make money off a theme without updating/modifying it is one year, then it becomes outdated. He also provided a link to a landing page where Moldcamp attendees could go to sign up on better terms than the rest of authors.Selling Drupal
Viktor Levandovsky’s keynote was less formal, did not bring as many numbers, but was still interesting and engaging. His main focus was on how/why/when to sell Drupal and what obstacles he encountered in his practice with clients.
He started by making fun of open-source skeptics and continued by listing strong arguments in favor of Drupal: large community, quality code, lots of extensions, stable security solutions and popularity on the world market. The audience was mainly geeks (developers, architects), probably no designers, so as expected - topics like UX were not event mentioned, etc.
Viktor sees Drupal as a framework more than a CMS and claims that he has yet to meet a functionality that cannot be implemented with Drupal. He’s seen only one project for which Drupal was a poor match.
The second part of his presentation focused on relationships with clients - teaching them to trust professionals, declining projects with bad requirements from the start.Event as a whole
Overall, I think it was successful, especially comparing the stories I heard from Romanian and Ukrainian guests about the first Drupal camps in their countries.
There was a heavy focus on networking, both me and my Propeople colleagues got the chance to interact with representatives from different companies in the area, as well as from abroad. Most of the speakers were very sharp, there was no bubble talk - true leaders that all beginners in the Drupal community of Eastern Europe can look up to. The knowledge shared was presented as accessible as possible, without loss in quality. Many presenters showed code pieces, and real-life examples - not just the theory that anyone can find in a codex or wiki. Every session had Q&As during or after the keynote, keeping communication going two ways.
Among other perks of attending the event: coffee partnership with Marcu’s Coffee (great coffee shop, by the way, check them out when you’re downtown), a wine break and branded pens that write really well (I’d buy more and an extra notebook if they’d be sold).
Still, no event is perfect. I look forward to better WiFi coverage at future Drupal camps and hope that I will not have to bring along my own 3G connection.
I’m definitely planning to attend next year, even more so if there will be more sessions targeted on business people, managers and marketers. Translating geek Drupal talk to businessmen is one of the topics I hope to see addressed in the future.
The organizers efforts deserve applause and acknowledgement. I think all participants will agree that we had a great time both at the event and at the afterparty. A big thanks to them, to the speakers that worked hard and to everyone else who attended.
If anyone wants to get to know Drupal or learn to master it, Propeople Moldova will be organizing an internship this summer with a real job opportunity afterwards. If you’re interested, send your resume to firstname.lastname@example.org.
And if you’re already a Drupal Jedi interested in working with some of the brightest web development minds in the area, drop us a note at the address above.Tags: Drupal eventsCheck this option to include this post in Planet Drupal aggregator: planetTopics: Community & Events
Chances are when you launch your site you are not feature complete. Often times it is best to get a site launched as quickly as possible and then work on adding additional features down the line. However, this creates a problem: how do you engage your visitors and let them know about new features?
A while ago I shared that we are trying to better understand who plays what role in the Drupal Community. A small team of Association Board and staff have done some interviews with about 20 community members and now we want to get a broader understanding - what are the issues that concern you, and who should be doing the work to address them?
We're reaching out to our most active community members to ask you to complete a survey about who you think should be doing what in our community.Take the Survey
How the Drupal community and Association staff (as part of that community) work together to support the Drupal project is a question that we are excited to come to some agreement around. Your participation in this survey will help us answer some of the questions we have raised and create a more productive and meaningful path forward.
We would like you to share with us your answers to the following questions about the various aspects of the Drupal project and community:
- Who decides? Which person or entity gets to make the final call about what direction to take?
- Who does the work? For every decision that is made, who ensures that the work is complete?
- Who is consulted? Who needs to be heard before a decision is made and/or throughout implementation?
The work of the community is incredibly broad, so there are lots of places we need feedback. However, we didn't want this survey to be overly-long, so you can pick and choose which areas of work you would like to inform.
For each area of work, we want to you to tell us how various groups of people should be engaged. The audiences are:
- Community Volunteers
- Drupal Association
- Drupal.org Working Groups
- Drupal Association Marketing Committee
- Core Maintainers
- Project Maintainers
- Security Team
- Infrastructure Team
- Consultant (Someone the Association would hire)
Have questions? Let us know. You can reach me at email@example.com
Flickr photo: Stefan van Hooft
The monthly security release window for Drupal 6 and Drupal 7 core will take place on Wednesday, May 21.
This does not mean that a Drupal core security release will necessarily take place on that date for either the Drupal 6 or Drupal 7 branches, only that you should prepare to look out for one (and be ready to update your Drupal sites in the event that the Drupal security team decides to make a release).
There will be no bug fix release on this date; the next window for a Drupal core bug fix release is Wednesday, June 4.
Code below allows you to render the Drupal user edit form anywhere. Replace UID with the user account ID to edit.$account = user_load(UID);
module_load_include('inc', 'user', 'user.pages');
$form_state = array();
$form_state['build_info']['args'] = array($account);
form_load_include($form_state, 'inc', 'user', 'user.pages');
print render(drupal_build_form('user_profile_form', $form_state)); Tags: drupaldrupal 7formapiprofileaccount