As Drupal gains popularity, the need for developers is increasing and consequently so is the need for trainers. Let's make sure that the first point of contact for people to the community is a positive experience by open-sourcing our methods of teaching.
With entities Drupal took a huge step forward in providing conceptual clarity in how it deals with things like users, comments, taxonomy terms and nodes.
I believe there is one more step to take to bring even more clarity that will hopefully be possible in Drupal 8. This is the content of my Core Developer Summit lightning talk- hopefully it is not completely off the mark.
Where we recount the enjoyment that was had by mistakenly thinking that there was a simple solution to our search problem, then stumbling across one of the few cases that seem not to be handled "out of the box" by the Apache Solr module and learn how much fun it is to write your own faceted filters.
Ultima invenzione di casa Apple è l'iPad. Se ne è sentito parlare tanto alla tv, alla radio e sul web, ma una domanda vi sta sicuramente martellando in testa.. vale la pena comprare un iPad? Per rispondere, dobbiamo capire innanzitutto cos'è.
Supporting Activity Streams in Drupal is an interesting problem. On the one hand you have the endless possible actions afforded by Drupal and on the other hand you have the necessarily restrictive standard on which to map those actions. Add to that the need to make this as transparent to the user as possible and it becomes a really fun little exercise. In this post we take a brief look at Activity Streams and what some of implications of supporting them in Drupal are.
While centralised (or at least single-point of control) social networks are dominant right now, social networking is really something bigger that what any one company should handle. Work is underway to provide the necessary technology stack to achieve that and we would love to see Drupal lead the way the same way it has done with Semantic Web technologies. This is hopefully just our one of many contributions in that direction. We set the scene and figure out what would be a good, practical first goal.
Does Drupal really have a steep learning curve? If you read the usual CMS comparison posts around the web that seems to be the general consensus. But I don't believe that is entirely fair and, as most things, it is all about relativity - how steep the mountain is depends on what is at the top of the mountain once you get there.
How do you know you are "doing the right thing" while building a Drupal website? What does best practice really mean? I think best practice can be identified not on the merits of how many people do the same things but on the basis of whether it passes a set of sensible rules. In this post I try to outline some of the ones I apply to help me decide whether a solution is sensible, and I hope others will chime in with their own methods.
Can Drupal revolutionise its contribution process and tap into the long tail of developers that have little time to contribute but want to help in a meaningful way? A proposal for the Drupalcon San Francisco Developer Summit.