Upgrade Your Drupal Skills

We trained 1,000+ Drupal Developers over the last decade.

See Advanced Courses NAH, I know Enough
Sep 07 2012
Sep 07

Listen online: 

Welcome to the first Drupalize.Me podcast! We've renamed the Lullabot podcast to Drupalize.Me and we're re-invigorating it with a new schedule. We will be posting a new podcast every other Friday, starting today! In this episode the Lullabot team gives a recap of the highlights from DrupalCon Munich. Join Addi, Karen, Joe, Sally, Kyle, and Brock as they chat about big announcements and their favorite sessions and moments from DrupalCon.

Podcast notes

Release Date: September 7, 2012 - 10:25am


Length: 40:12 minutes (16.1 MB)

Format: mono 44kHz 56Kbps (cbr)

Sep 07 2012
Sep 07

Drupal 8 Multilingual Initiative Code Sprint weekend

I took a train from Frankfurt (Germany) down to Munich the Saturday before the DrupalCon. When I joined the Multilingual Sprint on Sunday morning, many of them had already been sprinting for a full day and a number of issues were ready for review, so I dived in, observing the behavior of Drupal 8 before and after applying patches, proof-reading the patches for anything odd (e.g. typos in the documentation), discussing the issues in comments and in IRC with people who were sitting just across the room (other times actually speaking in person). By the end of the day, instead of the dozen or so people that Gábor Hojtsy, the Multilingual Initiative team lead, had expected, there were close to 50 people at the location, some joining us in the work on Multilingual issues, some working on other Drupal 8 tasks, and some who were just arriving in Munich and followed the Tweets to where we were. Luckily, the location rented for the Saturdays and Sundays before and after the DrupalCon week was big enough to accommodate all the extra arrivals.

While on the topic of the venue we used for those weekends, I’d like to personally thank Stephan Luckow and Florian (“Floh”) Klare of the Drupal-Initiative e.V. for all that they did to find a nice place that would still leave us with a budget for food and for their valiant work on stretching the food budget while still serving up excellent fare, in keeping with the fantastic meals we enjoyed the rest of the week. Instead of ordering delivery, they prepared almost everything themselves, including beautiful open-face sandwiches, fruit platters, and lovely grilled specialties at a club we went to where you can barbecue in the Biergarten.

…thanks for the huge help to the local organizers, especially Florian Klare and Stephan Luckow. They helped us manage collecting and spending sponsor money wisely with the Drupal Initiative e.V, prepared great sandwiches and fruit plates for us and even organized a sprinter party night with grill food. It was amazing to work with such helpful and flexible local organizers.
Gábor Hojtsy, September 5, 2012

Luckow and SirFiChi of the Drupal Initiative, organized the location and made us great food!

Since people were “fresh”, I think a lot of work got done on the first weekend and the Monday before the conference (more than 50 people joined us and worked on various core initiatives on Monday in the room we later used for core most conversations at the Sheraton), which also meant that issues were still fresh in our minds while we had days of sessions and conversations, so when we started sprinting again on Friday we had lots of new ideas for the tasks we were still working on. Friday’s sprints were at the Westin Grand, where there was great attendance both upstairs in the main room as well as a large room downstairs from it, where Drupalize.me hosted a core contribution workshop to ease people into the process of contributing to core. I decided to go to that workshop since I’m still pretty new to it all and found a few people sitting nearby who were I was also able to interest in some Multilingual tasks, so while the main group sprinted upstairs, we also worked downstairs. Later on, I came upstairs, and since there were not a lot of simpler tasks for “core newbies”, like myself, I took some time to sprint on a module I contributed some time back, before there was much of anything for Drupal 7 in the area of “multilingual”… and tried to make my module more multilingual-friendly. I got a few good commits and a new release out for Internal Links and also recruited a colleague to look at the code with me, provide some ideas, and become another maintainer. So I personally found Friday quite productive.

*/ First off, a sprint on this scale would not be possible without sponsors and significant on-site help. DrupalCon provided us with space on Monday and Friday, and some great food on Friday. The rest of the days would not have been doable without comm-press, dotProjects.be, Open8.se, OSINet and Acquia. The [ … ] financial sponsorships they provided paid for our weekend venue [ … ].

I continued sprinting with the Multilingual initiative at the Film Coop Saturday and Sunday, leaving mid-afternoon on Sunday to get back to the train station. When I left the other sprinters, Webchick was only finally getting some rest after her trip home and we had about 20 issues that were marked “RTBC”. In all, there were dozens of issues tackled over the weekend. For a complete overview of all the issues we made progress on, see Gábor’s post about the sprints, where you can also check out his excellent DrupalCon core conversation presentation, “Drupal 8’s Multilingual Wonderland”. There is still a lot to do in the time between now and the “feature freeze” deadline, but we made good progress in the DrupalCon sprints, so hopefully we can push on and get the rest of the critical tasks done in the time remaining.

One of the less trivial tasks I took on during the final sprint weekend was documenting the new language_select field type, which involved checking out the Drupal API (documentation) project, updating the Form API table to include a new Element column (language_select) and Property row (#languages), as well as information about these (below the table) and linking them in all the appropriate places. Currently, updating this page is a bit of a pain, but hopefully we will move to a better system for maintaining this information, perhaps even automated generation. While I’d worked on other Drupal documentation pages before, this was the first time I’d actually contributed patches to update the API, so it was a good learning experience.

If you’d like to help out with the Multilingual initiative or other core contribution, you might first want to take a look at the Drupal 8 Initiatives page, where announcements about coming IRC meeting can be seen. This page also has links to the news, roadmaps, filtered issues, and other pertinent information. Drupalladder.org is also a great place to go for lessons to help you work through the steps of being ready to contribute to Drupal core.

I look forward to seeing you all in IRC and in coming code sprints.

Sep 07 2012
Sep 07

I started writing this post at the DrupalCon and then continued work on it on the train back home after a long week, last Sunday after the code sprints—even now, more than a week later (after being ill for a week—I think I was burning the candle at both ends for a bit too long), it’s hard to believe that it’s finally over. I arrived the weekend before to participate in the pre-con code sprints and stayed for the Friday–Sunday after the conference to continue that effort. I’ll write about the sprints in another post. This one will cover the highlights of the actual DrupalCon, what I think worked well, and recommendations for those attending their first DrupalCon; with two new continents getting a ’con this year, I think there will be more than a few at their first.

The food at DrupalCon Munich was great

For me, one of the major highlights of this conference was the outstanding food quality. It was so good I was distracted enough I never pulled out my camera to take photos of i, but it was attractive, gourmet, and delicious and there was something for everyone, even a fantastic salad buffet as well as more desserts than anyone could try… and hot dishes with plenty of options for both vegetarians and omnivores, alike. In the closing plenary, it was revealed that the catering costs for the event were about €352,000 for the 1800+ of us in attendance; not surprising for the quality and abundant variety of fare they served us. Food service tables were put in place in all areas of the conference so that there was no crowding into one area and the same dishes were provided at both the Sheraton and the Westin Grand, which were a few minutes’ walk away from each other. The conference occupied the three conference center floors of the Westin Grand and a few smaller rooms in the Sheraton, which were primarily “core conversations”. One might think I would gorge myself, but most days I had simple salad items, walnuts, and seeds… and gave myself a break before finishing with some fresh fruit and a light mousse from the dessert buffet. Despite the fact that the days were hot and many of the rooms weren’t well conditioned, people were alert and in good spirits and I think the food had more than a bit to do with that.

To continue a moment in the vein of “food”, since I really do think it was notable at this DrupalCon, I hope this reflects some new recognition of the importance of good sustenance when organizing a successful event like this. And I hope that future Drupal events will also place emphasis on food quality. That said, I also think that the community would pull together if we had commercial kitchen space and quality ingredients—we could prepare similar gourmet meals without quite the budget we used for catering at this conference; on the other hand, such a model might work better at one of the large DrupalCamps (a few hundred attendees) than at a huge (North American or European) DrupalCon. Of course preparing our own food would provide another place for people to connect (food preparation and more volunteer service), which I think would offset the downsides (not being able to be someplace else whenever you have “kitchen duty”).

The Venue


Munich is a beautiful city I’d never really visited before the DrupalCon. Public transportation was not too expensive, but I got to see a bit more of Munich by walking almost everywhere, so my walks back from the pre-conference sprints and out to dinner (beer) in the evening were mostly through parks where I got to see the huge Olympics installation and unusual sights like Munich’s famous river surfing.

Surfers have a man-made wave on the Eichbach

Sessions and participation

Choosing sessions

This was my second time attending a DrupalCon and I decided I wanted to primarily attend the “core conversations” track (with a few exceptions). For those who don’t know, the “core conversations” sessions are where plans for the future of Drupal are presented, discussed, and refined. It’s truly an amazing experience to sit in a room with dozens of top-notch developers as they hash out the architecture for new Drupal features or present the innovations they have already completed. Of course participating in the Drupal 8 (Multilingual initiative) sprints in Barcelona (a couple months ago) and before and after the DrupalCon session days probably also spurred my interest in the areas being covered by other initiatives, but it is definitely an interesting track if you are not sure what to attend. In the past, core conversations were often not fully recorded, another reason I chose to attend this track, but it looks like you can view most core conversations pretty well now, online. If you missed them and are interested in the future of Drupal (i.e. Drupal 8), there are many that you might want to watch.


Another first for me was helping the DrupalCon staff as a volunteer, mostly monitoring the rooms I was in and taking a head-count in mid-session. Other activities of a room monitor included being a bit early and making sure the speakers had everything they needed; I got to loan out a display adapter for one session and was prepared with multiple power adapters if anyone happened to be missing a way to plug in—we also tried to make sure that questions were recorded in session audio (either by having those with questions come to a microphone or the speaker repeating the question). I found volunteering rewarding and I thank Adam Hill, the DrupalCon Munich volunteer coordinator, for being a great guy to work with.

DrupalCon Munich Volunteers

Drupal 8 will be great!

Angie Byron’s current overview of Drupal 8 (aka “”) had not changed a lot since I last saw her similar presentation at the “Developer Days” in Barcelona a couple of months earlier, but it filled the largest session room, so there may have been close to 1,000 in attendance. Some features are more polished, some of the features are not yet written, but are better conceptualized than they were a couple of months ago, but the general ideas are mostly the same so in a presentation providing an overview of Drupal 8, while much has changed, it wasn’t much that affected the presentation. I’ve take the liberty to add a few specifics which were actually covered in separate sessions (sessions which covered each core initiative, for example), just for the sake of brevity and consolidation of information.

Webchick presents an overview of Drupal 8 features and initiatives

One key point that was made by all Drupal 8 core initiative leads is that we are only 3 months away from “Feature freeze” for Drupal 8 (December 1st, 2012), so it’s time to pitch in and try to help get all the great planned features into Drupal 8. All of the major initiatives need help and have areas where they are behind schedule as far as being ready for the freeze deadline with all the features the community would like to have in core.

Key Drupal 8 initiatives and components

- This finally ends the problem of having an evolving set of configuration on the development/staging sites which needs to be moved to production… but can’t be since the configuration (in Drupal 6 and 7) tends to be all over the place. Having a set of YAML documents stored in your sites “files” directory is a good way to manage and deploy common patterns to multiple sites, update configuration on production sites, etc. And it gets around the issue that pushing a database update from a development/staging server to production might overwrite actual content. So we now have a working configuration management system based on YAML files and a developers’ API, but no user interface for adjusting configurations; the UI still needs to be written. We also need ways to determine if configuration has been changed on the production server, have a range of multilingual configuration issues to still resolve, and performance issues, among other outstanding tasks. Join the #drupal-cmi IRC channel during the CMI meeting times and work on the issue queue if you want to help get the CMI full-featured for Drupal 8. Most active work is in the CMI sandbox repository.

deals with helping sort out inconsistencies and inflexibility in the core blocks functionality. It’s been described as, “Like panels in core, only better”… well at least that’s the goal. Everything on a page has context and is a block or layout/nested layout. Since blocks are rendered independently, caching is well-supported. A responsive layout designer from Spark can allow you to figure out your layouts for different screen sizes without a ton of divs complicating their HTML. If you would like to help with improving Drupal 8 layouts, there are office hours every Friday in Drupal IRC in the #drupal-scotch channel and you can read more about their current issues by looking at the “sandbox” project for the Drupal 8 Blocks and Layouts Everywhere initiative (it is not yet in the 8.x master branch of Drupal).

features will be in core and better than ever before. Interface translation, content translation, base language functionality and language configuration are all being greatly simplified so that it can all be in core with a nice, normal workflow. A lot of the real “pain points” with multilingual sites (or even simply non-English ones) have already been addressed and there is a ton that’s been done, but there is still a lot more to complete in the next three months if we want to really consider this a success. A lot of great progress was made during the code sprints before and after the conference. If you would like to help improve the Multilingual workflow in Drupal 8, there are lots of ways for anyone new to Drupal core development to still pitch in. There many open issues and many ways to move them forward without even writing a single patch. The best place to find active issues is probably to look at Gábor Hojtsy’s “focus issues” list. You can join the Drupal Multilingual initiative meetings in IRC (#drupal-i18n). See the meeting schedule on the main Drupal 8 initiatives’ help page.

is one of the biggest initiatives in terms of importance to Drupal 8’s success… ensuring that a site is responsive to the display size and has toolbars which nicely resize for device type is one of the major aspects of this work. We need good front-end performance for running on smaller, lower-powered devices; we need good, solid, clean, uncomplicated HTML5 code, and we need to be able to support easily using Drupal as a back-end for native mobile apps, purely responsive web design, web apps, or anything in between. There are some big parts of this which are not far along yet, so this is a great place for front-end developers and others interested in Drupal 8 mobile experience to get involved. One current obstacle to the Mobile initiative achieving its goals is greater completion of the Web Services initiative (WSCCI) also achieving its goals. Otherwise, John Albin Wilkins, the Mobile initiative project lead indicated two other areas which need a lot of work: front-end performance and the Drupal 8 mobile admin interface, likely designed with Spark’s Responsive Layout Builder. There are regular meetings on IRC (see meeting schedule on the mobile initiative’s official Drupal Groups page) and the Drupal 8 issue queue has a tag for "mobile" so it’s easy to jump in and help make mobile support rock in Drupal 8. You don’t need to be a rocket scientist to help move the issue queue along. As Dries and others have indicated, this might be the primary initiative for determining Drupal’s future success, given current trends.

: One of the highlights of DrupalCon Munich sessions certainly had to be Angie Byron and the Spark team’s presentation of all the awesomeness that comes from the Spark-distribution modules. Spark is only still in “alpha”, but you can already tell how amazing the features are. The idea is that while they design the perfect authoring experience for Drupal 8, the community can use, test, and help to refine the new functionality (in Drupal 7 via the Spark distribution) so that the feature-set will be well-tested and as awesome as possible when Drupal 8 is launched. Spark allows you to simply edit content, in-place (via the Aloha editor used by the Edit module) and also has a number of nice tools for designing responsive layouts, and has a tool palette which pulls out from the side and responsively adapts to the device. The goal is for the editor system to output only clean code without a mess of ugly divs and inline styling… and the editor is already living up to most of that promise. Words don’t really do Spark justice, so rather than take my word, you can try the demo. Note: Since anyone can make changes to the demo site that might be a bit weird, if things are really messed up, you can check back later. And of course reviewing patches in the Spark issue queue and creating new issues, where applicable, can help smooth the way to getting the envisioned “perfect” content authoring experience into Drupal 8.x core.

The Aquia Spark team prepare their presentation at DrupalCon Munich.

: Theming/Templating improvements in Drupal 8 include the use of Twig, a templating system also designed by Fabien Potencier of Symfony. It eliminates PHP from the theming layer for simpler code and removal of many security threats. The work on Twig does figure heavily into some of the initiatives, but is not an official core initiative on its own. Work is being done in a Twig sandbox led by Andreas Sahle of Wunderkraut. If you are interested in helping build this up, you can check out this sandbox and assist with the issues.

: Drupal 7 was released in January 2011, but it took over a year before there were enough of the important contrib modules ready enough for it that Drupal 6 was finally surpassed (in terms of numbers of Drupal 7 installations). Getting Views into core will hopefully help boost the uptake of Drupal 8 use as soon as it’s released. This will be a lot of work and there is a fund to help pay for development time. A lot of Drupal 8 Views features actually already work. Major parts of cTools are now in core. There is a funding request for getting Views into core (I threw 10 € into the donation box at the DrupalCamp in Barcelona), and the more we can donate, the more the Views team can allocate paid developer time to ensure that Drupal has a nice version of Views available when it ships. Of course you can also help with the Views for Drupal 8.x issues.

in core (only better). There is still a lot to do, but the idea is that the site can take any kind of request and send appropriate responses without a lot of headache. A lot of Symfony components being brought into Drupal are especially important here. Symfony integration helps bridge a gap between ours and the also-dynamic PHP-based developer community around Symfony, so should help provide a lot more experienced developers for Drupal. There is still a lot to do here; you can check out the current status via the WSCCI sandbox and help with the issue queue. See the core initiatives overview page for IRC meeting times and details. If you weren’t there for Larry Garfield’s Munich presentation, Web Services and Symfony Core Initiative, you can still watch it to get a good overview.

Automated testing in Drupal 8 is much faster and the Symfony components also help allow us to have more modular modules… ones which can more easily be unit-tested. In Drupal 8, PHPUnit will replace Simpletest although the latter may remain in core for a transition period.

The social side of the DrupalCon

What happens between sessions is the real reason that most of us go to DrupalCons. There is nothing quite like participating in code sprints with Webchick sitting across the room, committing the patches you’ve just been helping with. And of course you can take your favorite Drupal developer out for a beer or something. It’s great to be in an atmosphere where there are thousands of people who actually have an idea what you are talking about when you tell them your occupation—and of course it’s nice, for a change, to be able to leave out any explanation of Drupal. If you go to a DrupalCon, it’s a given that you will leave having made new friends—new friends who will feel a bit more like “old friends” the next time you see them.

More DrupalCons in the coming year than ever before

If you have never been to a DrupalCon, there are more DrupalCons coming in the next year than we’ve ever had in a year period, before. Granted, the two new (Australia / South America) cons are planned as smaller events that would actually be dwarfed by some of the larger DrupalCamps, but this is all a sign that Drupal is growing, world-wide. Note that the U.S. and European DrupalCons are both being held a bit later than in previous years. I look forward to seeing you all at a coming DrupalCon.

Aug 22 2012
Aug 22

Posted Aug 22, 2012 // 0 comments

When Moshe Weitzman posted his idea for a Drupal community initiative called DrupalGive on Drupal.org, we knew we wanted to get on board. As Moshe simply explains, Drupalgive is a page that organizations publish on their website to highlight the ways they have contributed to Drupal with the intent to educate clients and partners about the Drupal community and also "nudge" other organizations to contribute.

By nature, open source software is dependent on contribution. As Drupal matures, organizations are using it to build bigger, more complex websites. It is therefore more important than ever to contribute and share within our community in order encourage further innovation.

We are proud to announce the launch of our own DrupalGive page, designed by Dave Ruse and developed by Tirdad Chaharlengi and Josh Cooper.

Our page highlights 4 different ways we contribute to Drupal:


We recently posted a blog about our contributions to the Large Scale Drupal Initiative (LSD)  Specifically Site Preview System, read more about the project and this module here.


We are a proud silver sponsor of DrupalCon Munich. We've been busy in Munich with some great collaborative sessions:


We maintain 4 distributions: OpenPublic, OpenPublish, Open Atrium and Managing News.  We are excited about the most recent OpenPublish release including a new demo theme: Gazette.  Stay tuned for the impending OpenPublic release!


We make sure we post as many of our session slides as we can, to promote Drupal Learning. Look out for our DrupalCon Munich session slides posted soon to our slideshare.

We had a lot of fun putting our Drupalgive page together, we look forward to our contribution lists growing, and using other organization's Drupalgive pages to stay informed and up to date on the latest Drupal contributions. 

As marketing coordinator at Phase2, Annie is involved in the open source events in the New York metro area. She really enjoys engaging the lovely Drupal Community and promoting Phase2 to prospects, clients, staff members, and the greater ...

Aug 17 2012
Aug 17

Posted Aug 17, 2012 // 4 comments

The Site Preview System Drupal module is a framework for previewing a site with a set of conditions active. Here is a video to introduce you to what the module does. SPS was developed out of the LSD CSI project as part of a suite of modules.

The Site Preview System works by accepting conditions, generating a list of override revisions and altering the page to display the correct revision on the page.

Modules that came out of the CSI project

Modules that are currently integrated with SPS.




  • Nodes
  • Any other entity that supports Revisions

If you are going to be in Drupalcon Munich please come to one of the sessions or BOF

Team Architect at Phase2, Neil thrives on working with the development team to come up with creative implementations for complex situations. Neil enjoys pushing Drupal past its boundaries to implement cutting edge concepts, and has a ...

Jul 03 2012
Jul 03

Posted Jul 3, 2012 // 2 comments

After wrapping up my first DrupalCon this past March in Denver, I thought I would pass along some insight of my experience as well as tips and tricks for those who may be gearing up for DrupalCon Munich. At such a large conference, with so many hardcore Drupal fans everywhere, one is bound to get a little overwhelmed, maybe even feel the urge to crouch in the fetal position, but that would be a mistake! Take a deep breath and plan ahead:

  • Keynotes will give you a nice look into how people are thinking of the overall future success of Drupal.
  • There are a lot of smart people everywhere you turn. Talk to them, get to know them. There is certainly a conversation about a topic of interest everywhere you turn.
  • There are typically multiple sessions that you want to go to at the same time (so many options), plan in advance.
  • There is a nice range of topics for beginners to advanced individuals. Sessions are typically more 'glanced over' topics where as BoFs may be more in depth for those looking to explore further.
  • During the DrupalCon, keep hydrated, just a good general rule of thumb.
  • Make sure your laptop is charged up.  Wall sockets run out quickly.
  • There will be a good mix of social events, activities and parties to let your inner-geek relax a bit, take advantage of these.
  • Great sponsor events *cough* phase2 free bar *cough*

With so much going on at DrupalCon, I definitely felt overwhelmed by the event.  With such a broad range of topics going on all the time, on more than one occasion you do have to sacrifice one session to check out another.  Thankfully the sessions do get posted online, so downloading them at a later date is certainly an option. 

The other option I didn’t get to explore was the BoFs (birds of a feather) sessions.  These openly scheduled topical sessions are submitted by the attendees themselves and happen at various times during the day.  I'm looking forward to exploring this option more at the next DrupalCon to really get deep into conversations regarding topics of my interest. The overall feeling of BoFs would most likely fall in the lines of ‘compsci-301’ rather than ‘intro to computers’; definitely something to look forward to next time. Certainly plan ahead and check out the schedule of posted BoFs to see what you may want to attend

All in all, my experience with DrupalCon Denver was overwhelmingly positive. People are in love with the technology being presented and there are a lot of brilliant minds to learn from and talk to.  There are so many great sessions, BoFs, events and activities going on that you could have a different agenda each time you go and still just scratch the surface.  Remember, if you start to feel overwhelmed in Munich, keep calm and Drupal on.

Josh Cooper’s user interface development skills play a vital role in bringing great design ideas into fully functioning websites.  His specializations in HTML, CSS, Javascript plus his focus on Drupal as a platform, make Josh an ...

Jun 19 2012
Jun 19

It’s been a busy past several days in Barcelona (for the Drupal Developer Days) and most of us who’d been sprinting during the week before seemed to be in the same condition by Sunday—rapidly running out of energy from progressive sleep deprivation from an increasingly later return to our hotels. But it’s been an exciting week for Drupal core (and contrib) development and significant work has been completed on the Drupal core (mostly building up Drupal 8, but also some for added features in Drupal 7) while a lot of important decisions have been made which will likely shape development in a number of initiatives for the coming months until the sprints at DrupalCon Munich.

In addition to the Sprint I was primarily involved in (I was just trying to get my feet wet with assisting the Drupal 8 core development process by joining the multilingual sprint, but I did write my first committed core patch—admittedly this was a very basic patch), there were also sprints running for “Views in core”, Entity API, Media initiative, Mapping in Drupal 7, configuration management, abstracting social networking, search-related sprints, the Drupal.org upgrade… and possibly more still. I’ll cover some of the highlights of the week that I’m most knowledgeable about.

Multilingual Initiative

The multilingual initiative sprinted all week before the Developer Days sessions, and even continued through the weekend. And a lot of key decisions were made and important code changes committed and pushed to the central Drupal 8.x repository.

New user interface translation improvements in Drupal 8

This is something I got to do a bit with, but Swiss developer, Michael Schmid (Schnitzel on d.o), of Amazee Labs, was the primary developer working on this task during the Sprint. He and his colleague, Vasi Chindris, were among the stars of the week. It was a real privilege to get to look over their shoulders and to get Michael’s support when it came to using Git to manage code in the sandbox we were using for the issue. (Thank you, once again, Michael!) Once everyone was happy with the work, it got committed to core. This new sandbox workflow, used for larger issues, helps avoid a lot of bugs creeping into the main branch, as has happened during previous periods of intense core development. Of course the tests and test bots catch a lot of issues which could otherwise be major headaches for all concerned (automated testing was also a part of Drupal 7 development). If you recall, the long wait for Drupal 7’s release was due to hundreds of critical bugs. Now this should be a thing of the past since we have an established threshold for critical issues; and the core team only commit new patches to the central repository when we are below that threshold (15 “critical” bugs, 100 “major” bugs… among other thresholds specified).

New system for translating Drupal’s user interface

The new user interface translation system allows you to keep imported (community contributed) translations separate from customized translations and search for a particular translation within either or both categories as well as filter by translated strings, untranslated strings, or both. If you have any unsaved translations, they are highlighted to help remind you not to leave the page without saving them and there discussion about providing a dialogue to prevent a site admin from accidentally leaving the page with unsaved changes, too. There is also an issue to allow the string search to be non-case-sensitive (checkbox) to find more strings that contain a particular word or phrase, regardless of text case. Since this feature came up in discussion after the rest of the user-interface changes had already been made, we elected to put the discussion about adding this feature in a separate issue. If you have ideas for what might further improve the Drupal 8 user-interface translation workflow, your input is valued.Customized and imported (community) translations are stored separately


New content language options

Drupal 8 has new language settings per content typeYou can enable translation for a particular content type and also choose to hide the language selector (automatically selecting the language for a new piece of content by any of a number of contextual rules). The automatically selected language for a new piece of content can be any particular language enabled on your site, “not specified”, “not applicable”, “multiple”, the “site’s default language”, the “current interface language”, or the “author’s preferred language”. While all these settings might arguably be a bit confusing for new users, they should help smooth the content creation and translation workflow for most sites. Of course the option to “enable translation” is hidden if the default language for the content type cannot be resolved to a single language (i.e. for “not specified”, “not applicable”, or “multiple”), since translation does not make sense here.

Translate the English UI to… English!

Drupal 8 — Enable English UI translationIn the edit preferences for the English language, you can enable translation to English and then it’s easy to change, for instance, the “Log out” link to “Sign out” (or “Disembark”, “Abandon ship”, “Terminate session” or anything else you might want on a particular site). Of course this could also be useful for fixing any oddities you find in the UI strings provided by contributed modules if you find a mistake in a field description, for instance, you don’t need to wait for a module developer to commit your patch or add a “site English” custom language just to modify a few strings.

Configuration Management related to Multilingual sites

Drupal core team leads and other sprinters discussed multilanguage configuration

One of the biggest issues of the week was determining how multilingual configuration would be handled in Drupal 8. The core team knew that they wanted to store language configuration in files rather than in the database, so that it’s easy to “push” new language configurations to an established site that already has content, among other benefits of this approach. But this brought with it a number of challenges which the Multilingual Initiative team, Configuration Management Initiative team, and other interested parties discussed in several sprint discussions through the week. Many of the standard configurations for a site might also differ, depending on the language: you might, for example, want a different site name or site slogan or logo for each language. There were three different proposals for how to handle multilingual configuration, and to keep a long story short, the final decision was to go with “Plan B” (or a minor variant, thereof). You can still lend your voice to the “review” process in the main issue for the language configuration system in Drupal 8. If you would like an overview of the plans, there is a nice graphic by Gábor Hojtsy (the Multilingual Team lead) which outlines the differences between the three proposals and some variants.

Drupal 8 Configuration Management

Greg Dunlap (“heyrocker” on drupal.org) presented the new configuration management

Angie Byron, aka “webchick” gave a quick overview of the configuration management initiatives goals, tooOne great session from the weekend was the Introduction to the Drupal 8 Configuration Managment System by Greg Dunlap (“heyrocker” on Drupal.org), the Configuration Management Initiative team lead. There has been some good progress in determining what this is going to look like, some of which took place during the sprints in Barcelona. Basically, this will be a bunch of smaller files stored within a logical directory structure in the sites/[…]/files directory. The new configuration system is currently planned to be YAML-based (rather than PHP or XML, which were used in earlier visualizations of the system). And the goal, as described by a slide in Angie Byron’s Sunday-morning keynote, “Drupal 8: What you need to know” is to be like “Features in core, only better”. The aim is to help us remove the complications involved in pushing configuration changes, modified in a development or staging environment, to a site that already has user-created content that we don’t want to lose. The main problem with the current system is that there is no consistent system: configuration settings are scattered across multiple tables, variables, files, and other locations and there is no consistent structure in any case. The idea is now to have a contexts, which Drupal responds to, when determining which configurations files to use.

Angela Byron (“webchick”) talks about the problems the new configuration management system aims to solve

What it should look like when loading a configuration from module code, is something like this:

  $config = config('image.style.large.yml';

And when setting and saving configuration data:

  $config = config('system.performance');
  $config->set('cache', $form_state['values']['cache']);

The YAML code for the image example, which saves configuration for the “large” image style would look something like this:

  name: large
      name: image_scale
          width: '480'
          height: '480'
          upscale: '1'
      weight: '0'
      ieid: image_scale_480_480_1

This should be pretty easy for developers and site builders to learn to work with and of course an interface is planned which should automatically build the configuration files, when edited by site builders. Configurations will be loaded into the “active store”. Changes are saved back to the active store and back to the YAML files so they can easily be moved between sites (staging and production sites, or completely different sites if they should have some settings in common). Building up an ideal import/export system for configurations is one of the major remaining hurdles. Update: heyrocker’s presentation slides are now available for download, so you can see other examples of Drupal 8 configuration.

Other Drupal 8 news

Twig library committed to core!

Drupal 8 now has Twig in the core/vendor directoryOne of the new developments which has received some press is that Twig, the templating system designed by Fabien Potencier, the innovator behind Symfony, which also bundles Twig, has now been added to the Drupal core repository.

However, the fact that the Twig library is in the repository does not mean that it’s ready for any kind of use yet, except for those who are working to build a new templating engine for Drupal, which uses it. How this works is still open to discussion; according to webchick, it may be that we keep both PHP-based and Twig-based templating engines to ease the pain of this change. On the other hand, while there is a learning curve involved, there are many advantages to Twig, especially in terms of security (removing PHP vulnerabilities from themes, altogether), and the saying that “the drop is always moving” applies here. It may be that Twig is the only templating engine which will be supported by Drupal 8, but if you feel strongly about this or have ideas for how to do this “right”, it’s a good time to get involved.Twig vs PHP template syntax

Context-based layout and blocks

Angela Byron lays out the plan for Drupal 8 layout with contexts

Everything in Drupal 8 will be a block or a layout area and blocks can have multiple contexts which determine their behavior (and whether or not they are displayed). This is going to be a major change which should produce much more flexible layouts and site designs. Of course this will touch on every major Drupal initiative: configuration, HTML5, mobile, multilingual… all are involved.

Drupal 8 will have clean, semantic HTML5 (and will abandon IE)!

Say goodbye to the messy nested div hell! Drupal 8 code is going to be much smaller and cleaner which will make designer/themer types love Drupal and make it possible to produce code that renders nicely, regardless of display size. Oh, and don’t worry about trying to support older versions of Internet Explorer; the community has decided it’s time to put that tiresome task to rest. Yay!

Drupal 8 development needs you!

Webchick, heyrocker, Gábor Hojtsy… all made the same point: As a community effort that’s still underway, the Drupal 8 effort needs more of the community at large to get involved and find ways to help out. There is a lot of complexity, but there will be smaller tasks that anyone could work on, so there’s going to be something for everyone. Even non-coders can help by testing, filing bug reports, helping manage the issue queues, making suggestions, documenting finished features and APIs. There are several places where you can get involved:

  • The core initiatives overview page provides information about when the different teams meet in IRC and in which channels among other information which can help people who want to find ways to get involved.
  • Drupal Ladder is a project aimed at helping more people learn how to contribute to Drupal
  • [ … ] (Comment below if you have other tips for where to get involved)

Big thanks to the organizers, sprint leads, and session speakers

The Drupal Developer Days in Barcelona were a big success because of all of you pulling together to make things happen. The local organizers made us all feel welcome and provided a lovely venue and took us out on the town just about every night. The sprint leaders helped find ways for everyone to play a part in building Drupal 8 or contributing in other ways, and the sessions were awesome.

May 11 2012
May 11

Drupalcon MunichHere we go again! Drupalcon Munich is just around the corner - August 20 - 24th. That may seem like a long time, but for a veteran of organizing one of these events, I can tell you that the work is ramping up rapidly. All my best to our friends and colleagues over the pond who are, undoubtably, working like crazy. I'm looking forward to enjoying the next convention not being behind the scenes.

Over the last few months I've presented on Agile Scrum twice. Once, as one of the Drupalcamp Austin Keynotes and a second time at Drupalcon Denver with my good friend Stacey Harrison. The presentation evolved from one of the events to the next. I've continued to wear my presenter hat and am ready to do Mark III on the topic of Hybrid Agile Project Management.

Learn from the experiences of Examiner.com's team. We've done it all - cowboy, waterfall, extreme, and agile scrum.

Learn why...

  • Waterfall doesn't always work
  • Agile has a place, but isn't the holy grail
  • Cowboy can kill the relationships you have with your stakeholders
  • How "Fixed Scope" is a lie
  • That a combination of approaches is the answer
  • The Examiner team has carefully honed, updated, improved, and iterated its process for over two years. It continues to evolve, improve, and make development more consistent and predictable.

Project management requires a blend of techniques and tools to effectively shepherd projects from ideation to release. We'll explore and discuss different tools and methodologies that can help make your project successful.

I'd love the opportunity to continue to share my learnings over the last 16 years with a particular focus on the immediate previous 9-12 months. Examiner's process has changed, evolved, improved, and continues to become increasingly awesome. If you're interested in seeing me present, please pop onto my proposal and leave a supporting comment!

Over the last few years I have become great friends with Rick Nashleanas of Monarch Digital. On the last day of Drupalcon Denver, he and I spent quite a few hours chatting, eating, and drinking and ended up cooking up a plan to present together. We're hoping this first faure together might occur in Munich. Come chat with us about recruiting and retention, about active listening and communicating, and about being mentored and mentoring.

Drupal has been around for about a decade. Information Technology predates it about about 5000 years - the Premechanical, the Mechanical, and the Electromechanical segued into The Electronic Age in the 1940s. In the 1950s what we would recognize a Project Management began evolving. There have been Project Management truisms across time.

Sit with two veteran IT managers and leaders (who also predate Drupal) to discuss:

  • Recruiting - Where and HOW do you find people?
  • Retention - How do you keep and nurture those you have?
  • Zen and the art of listening... and hearing. How to hear your clients, your peers, your subordinates, and those you report to.
  • Mentorship - Designers, Coders, Project Managers - How to grow within and beyond your discipline.

Attendees should bring questions and ideas that can be explored by the entire group.

If you'd like to see Rick and me engage in entertaining, informational, and engaging buffoonery - please write a supportive comment on our proposal. Here's to our next community event! Sharing, contributing, and participating brings me joy. I hope I get the chance in Munich.

May 10 2012
May 10

Listen online: 

Florian Lorétan, one of co-leads for DrupalCon Munich, takes a moment to discuss what is happening with the upcoming conference and what people can expect. He introduces the overall theme "Open Up! Connecting Systems and People" and explains what it means, how it will tie in to the sessions, and why it's important.

This Drupal Voices was recorded at the 2012 DrupalCon in Denver.

Release Date: May 10, 2012 - 3:00pm


Length: 5:12 minutes (3.61 MB)

Format: mono 44kHz 97Kbps (vbr)

Mar 22 2012
Mar 22

As announced on stage at DrupalCon Denver, we have just opened the Call for Papers for DrupalCon Munich 2012, as well as keynotes, call for trainings, scholarships, and registration. The Drupal Association and the Munich DrupalCon committee have been preparing for the next DrupalCon for months now. Things will move into high gear once DrupalCon Denver closes its doors, later this week.

Announcing ...
Keynote speakers
DrupalCon Munich announces three keynotes by open source and industry visionaries, including Dries Buytaert - the founder of the Drupal project talking about the future of Drupal on Tuesday, August 21; Anke Domscheit-Berg, a renowned expert in open government and open data, speaking on Tuesday, August 22; and Fabien Potencier, CEO of SensioLabs and founder of the Symfony project speaking on Wednesday, August 23.

Call for papers
Your contribution is needed! Come to Munich and share your expertise with the most amazing open source community in the world. Submit your session ideas at http://munich2012.drupal.org/call-for-papers

Early Bird registration opens today!
Registration for DrupalCon Munich is now open. The special early-bird rate is €350 for the first 300 tickets, after that the price is €400 until June 15, and 475 until July 31. Late registration after this date until August 17 will be €525. On-site registration will be €575. The is a limited number of tickets available at a rate of €200 for students and non profit organisations (all prices inclusive of VAT).  Register now at http://munich2012.drupal.org/register.

Call for trainings
The Drupal project needs more contributors, site builders, users, and developers. We’re looking to cover the gamut from beginner to highly advanced trainings. Trainers and training companies, submit your trainings now! http://munich2012.drupal.org

Scholarship applications are now open
Drupal is for everyone and everyone can enrich the project. If you would like to come to DrupalCon Munich but cannot afford the cost, a limited number of scholarships will be available. Submit your application at http://munich2012.drupal.org

Keep up-to-date with all things Drupalcon Munich; follow @drupalcon on Twitter.

-- Florian Lorétan (floretan) and Karsten Frohwein (kars-t), co-chairs of DrupalCon Munich

Feb 29 2012
Feb 29
Florian Lorétan holds out the official DrupalCon Munich promotional beer coaster

Over the past weekend at DrupalCamp Essen, I had the opportunity to sit down with Florian Lorétan, who has been instrumental in organizing and coordinating all the work which goes into bringing the next European DrupalCon to Munich, Germany. Since the last time we’d spoken, at Drupal City (the Drupal Camp held in Berlin, September 2011, less than a month after the initial announcement in London), there had been a lot of new developments. I asked Florian to catch us up.

Lowell: I’m Lowell Montgomery from Cocomore and I’m here in the BoF room at DrupalCamp Essen, speaking with Florian Lorétan, Munich’s community representative and a co-founder of Wunderkraut, about new developments in the planning of DrupalCon Munich. So what’s the latest news, Florian?

Florian: There are a lot of things going on right now. One of the big things we have on our plates right now is just making all these developments communicable. There’s a lot of work being done on the website, both on content and also on making the content look good — so it’s styling all the content types, different views, new content types, different blogs — and making sure that the sponsors get the attention they deserve on the website and also preparing for the session poll results which will open in a few weeks. One of the things that needs to be communicated are the featured sessions. We have some very exciting speakers coming from the outside — some very exciting topics, too. This is not completely final; but we do have some sessions which are confirmed, so this will probably be going up on the website in the next couple of weeks.

Florian: If it’s ready before DrupalCon Denver, we’ll put it on the website then, but at the latest it will be there at Denver.

Lowell: And you mentioned that the sponsor slots are pretty much all filled?

[…] For Munich, we still have Silver (very limited), Bronze, Sponsor Lunch, Sponsor Coffee Break, Sponsor a contest (like Tropo's hackathan or Twilio contest) [ … ]

Megan Sanicki, from email update, 29 Feb, 2012

Florian: All the top ones are sold out; Diamond, Platinum, Gold, and I think Silver, too, is sold out. The day stage sponsors, the beer garden sponsor, the coffee sponsor; are also given away. With Wunderkraut, we’re also happy to get the contribution lounge and contribution sprint sponsorship slots, which is something that fits for us, but it’s also a one-of-a-kind sponsorship of our community. I think that it’s been going very quickly; we weren’t expecting things to go that fast. Megan Sanicki is responsible for all the finances and sponsorships for DrupalCon and she’s has been doing a fantastic job at it. I think it’s really great that the sponsors have shown such incredible enthusiasm. I think it’s an indicator of how much interest there is in the conference and I hope that the attendees show as much interest as the sponsors have.

Lowell: That’s great news. But there are still unlimited Bronze sponsorships available, though, right?

Florian: Indeed there are. And it’s still a great way for Drupal-related companies to help make this an event which everyone in the community can afford to attend, while also getting good value. I’m not sure of the exact pricing and details right now, but on the DrupalCon Munich website the sponsorship packages are fully described. There may also still be some other opportunities for special sponsorships, but the opportunities for getting a booth or table are getting very limited, if not completely sold out.

Lowell: So one thing I really wanted to ask you about is: how can people who aren’t already involved in the planning do something to help make sure this the most awesome DrupalCon Europe to date?

Florian: The best thing to do is really just to spread the word: blog about it, tweet about it, make a presentation about it at the local user group, to get people up to speed, to get people to know what it’s about. There’re still a lot of people who don’t know exactly what DrupalCon is, and what the goals of DrupalCon are. Many people think that it’s a for-profit event, which it’s not, it’s really an event that’s fully targeted at getting the Drupal people of all kinds together, whether they are business people, developers, designers; getting all these people from the Drupal world together and really also growing the Drupal community, so reaching out, outside all those who already do business with Drupal. And this is one of the main goals of this specific conference; our slogan is “Open up: Connecting systems and people” and behind this “open up”, we also want to reach out to related communities, so to people working with new Javascript technologies which can be combined with Drupal, reaching out to people from the Typo3 community, which is particularly strong in Germany; it’s also an open-source project — in some ways it’s a competitor, but we have a lot in common and I think it’s great to have that kind of open discussion, to really be able to have that as some positive and constructive exchange of ideas. So this is one of the things that we are looking for in our featured sessions: to reach out to people who would not normally be participating at DrupalCon, to get people from the outside so that we can have a wider range of topics and also have topics that are interesting for people who are not working exclusively with Drupal.

Lowell: For people who do know what a DrupalCon is and live far away, say in North or South America; it’s easier for them to get to Denver. What can you say to encourage them to come to DrupalCon Munich other being able to go to interesting beer gardens and see Germany?

Florian: Well, a lot of people travel to DrupalCons both for professional reasons and as tourists and a lot of people bring their families for the trip to DrupalCon, so we are planning all the special events and parallel activities with DrupalCon.

Florian: Right, Drupalganger outings and also making sure we have some cultural activities.

Florian: Besides that, Germany is probably the largest Drupal market in Europe and the market with the biggest potential. There is a lot of demand and a lot of growth potential. And so I think it’s inevitable that there will be a lot of interest from the outside to get some presence in the German market, so for large companies it’s really a very interesting market to open branches, do more business with Germany, and also for the European market: more and more we are seeing that we’re not dealing with local projects anymore. It’s not a local Drupal shop working for a local company; we’re seeing companies from all over the world doing projects for clients all over the world. Since the German market has a lot of weight in the global economy, I think it’s important to have connections there; it’s important to have a presence there. And also there are a lot of very important contributors to Drupal core and to contrib modules who are from Germany. There’s a very active community in Germany. So for people who are more interested in the community-contribution aspects, there’s a lot of activity in Germany and the rest of Europe, too. So one of the things we are particularly looking at is turning the contribution lounge into a place which really supports and encourages people to contribute, to work with each other, and to have conversations about improvements that can be made to Drupal, to contrib modules, to the way we do business, to the way we do marketing, to the way we do design. We want this conference to be a conference where people participate actively. It’s not a conference where people just go, watch awesome sessions and take notes, and then go home. It’s really a conference where people are active, they discuss things, they meet people, they make new connections, they do business, they write code; it’s really a hands-on conference.

Lowell: Right. So there’s a lot that takes place at a DrupalCon and a lot that goes on in the half-year between the DrupalCons, so if people only attend once-per-year at the conference closer to them, they are missing a lot and missing the opportunities to meet and connect with other members of the community who might not be able to make the longer trips to Europe or to North America.

So are there other ways that people outside of Germany could help support the preparation processes?

Florian: Actually for the teams doing the coordination and organization of the event before the start of the conference, we already have a pretty good team. We have about 30 people involved, split between the design team, the website building team, the track chairs, the people doing the coordination of various events; there are also people working on the marketing. We really actually have a very good team. We have a couple of positions coming up, but what we’re really looking for are people who can make a time commitment, and who can take up responsibility and say I’m going to dedicate myself to do that and we need people who are reliable, because when we are working with such a big team of people, if we have people who are not reliable, then we just spend more time looking after people and we just want people to get the things done. But there are couple of opportunities and if someone wants to get involved, they should just contact us directly through the contact page and say “Hey, I’m available and I have one day a week that I can dedicate to this cause.” And their contact will be forwarded to the correct person. Otherwise there’s going to be the possibility to be involved on-site maybe one or two days before the conference helping with registrations, with distributing T-shirts, with showing the way, helping by being a room monitor during the conference, just making sure that things start on time, and that the speakers have water and so on. But for this kind of volunteering, we’ll post a form on the website one or two months before the event. It’s currently too early to start working on that.

Lowell: Right. How does that work, anyway? If you want to help out at the event, can you do that just for part of the day, so that the rest of the time they can be in sessions and participate in other aspects of the conference?

Florian: Yes. This is generally done in half-day slots or something like that, so we generally have plenty of people who just want to help. I’ve done it before; it’s a lot of fun. You work with other people who are also really passionate about what they do. So it’s a fun experience. You normally get a T-shirt for it and that’s pretty much it, but it’s a great opportunity to start being involved. So sign up for our newsletter on the website and you’ll be notified when we have the call for volunteers.

Lowell: Okay. So is it time yet to register for the conference and buy a ticket or when does that happen?

Florian: It’s not open yet. There are still some things to do to finalize the budget and determine the ticket price. This will be coming soon; it will probably be open a couple of days before Denver, but the official announcement, when we expect a lot of people to register, will happen on the last day at Denver.So it should be ready in a couple of weeks.

Lowell: What are your expectations about how many people might be in attendance at DrupalCon Europe?

Lowell Montgomery, at left, interviews Florian Lorétan at DrupalCamp EssenFlorian: Well, we have enough space for 2500 people. This is bigger than other European conferences, but at the same time, well… there’s been steady growth in the community. Also Munich has a very central location in Europe. It’s very easily accessible from pretty much anywhere by either plane or train, so I’m expecting a lot of people to come. Also, since we want to reach out more to people outside the community, it’s not going to be an event that’s just for a niche group. We want to make it a great event that we hope will attract people from outside the community. I personally expect the conference to sell out. It might not be possible to buy tickets at the entrance. If we get as much interest from attendees as we got from sponsors, if it goes as quickly, then we will definitely be sold out.

Lowell: That’s great! Unfortunately, I’m not personally going to be able to get to Denver… between the cost of airfare, the cost of staying in a hotel for a week, and other expenses, it’s just not in my personal budget right now, so I’m wondering how the prices of hotel accommodations in Munich compare to the costs in London and in winter-tourist-season Denver?

Florian: In Munich, the conference is taking place at a hotel where they’ve offered conference attendees a special price which includes, among other things, free Wi-Fi in the rooms. There are various advantages. You can already make reservations by phone or by e-mail just by mentioning DrupalCon and there’ll be a special form for booking your hotel accommodations which should be ready soon. Otherwise, Munich is not a cheap city, but there are some budget priced hotels in the area and the local transportation is good, so it should be possible to stay at other hotels and easily get to and from the conference location. Public transportation there is great and I would certainly recommend anyone coming for the week, especially if they are staying at another hotel, to buy a public transportation ticket for the week. I think it’s 13 or 14 Euros.

Lowell: That’s a good deal. Do you have any final thoughts you’d like to share with us.

Florian: Well one of the things that we did in London is that when we announced the conference in Munich we handed out stickers. The logo for the conference is actually a beer coaster. And our design team from Cocomore came up with the idea, “Hey, the logo is a beer coaster, how about printing real beer coasters?” And so we looked into that, and then when we were looking at the quantities, we realized that we could actually use a lot of those. And so a couple of weeks ago they were printed and then just last week we received them in our office. It’s two very big and very heavy boxes full of beer coasters, and now we’re distributing those at various Drupal events. so we’re here at DrupalCamp Essen and people are very excited about them already and they’re taking them back to their respective user groups. We’re taking them to CeBIT, the largest IT conference in Europe, where Drupal has a booth. We are also taking many of them to DrupalCon Denver and to many other events. And so one of the things that were going to do with these is we’re going to have a contest for the most creative use of these coasters. So it’s going to be on Twitter; just post a creative use of your beer coaster. And, of course you first need to get your hands on one of them. So if you’re in Denver, be sure to get one. And if you’re not going to Denver, make sure you ask someone who’s going to Denver to get one for you. I’m sure it’s going to be a lot of fun, so more details will be coming up soon. Make sure you get your hands on one of those beer coasters. The design team from Cocomore really did a fantastic job! It’s been a pleasure working with them.

Lowell: I agree. I think the DrupalCon site really looks terrific, too.

Well, thank you for taking the time to talk with me today and I’m definitely looking forward to Munich.

Florian: You’re welcome, Lowell. I’m looking forward to it, too.

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web