Packt Publishing's ever growing Drupal bookshelf expanded with Drupal 6 Performance Tips in February. The book rightly earned its title from being some tips without trying to pin down a comprehensive guide. Maybe even better titling would have been to attach a "for beginners" to the end. Contents of the book really cater for beginners with little coverage of topics outside Drupal's (and some major contributed modules) own internal solutions to performance problems. Its subtitle hints that it provides best practices which I'd respectfully dispute.
What's entirely surprising is that the 220 page volume starts off with 50 pages on upgrading a Drupal 5 site to Drupal 6. While the most current performance tweaks are usually documented for latest versions of Drupal, assuming the reader must have started off with an old Drupal site might not be the best way to set the tone for the book. However, the author comes back to upgrading modules regularly at a later stage in the book, which I've valued. It clearly underlines the need to come back and update your environment once in a while. (That module upgrade explanation is at an absolutely unexpected point in the book, which makes it even better positioned).
After some organization around travel and accommodation (which is still in flux to some degree), looks like there is nothing in the way for me to attend Drupalcamp Timisoara 2010 and contribute some content to the session schedule as well. Fun! This Drupalcamp is taking place in the Politehnic University of Timisoara in one month on June 5th and 6th, and is primarily English. I'm spotting others coming from as far as Belgium, Serbia, Moldova, Hungary, Austria and Germany.
The two sessions I've submitted for the schedule are the following:
"Come for the software, stay for the community" could become Drupal's new slogan (see the discussion), so what better title to use to explain what Drupal is about? In this session I intend to provide a brief overview of what Drupal is and instead of delving into technical details, focus more on how the different avenues to improve Drupal work. Systems like distributions, localizations, issue queues, the core and contributed modules repositories, the security team, automated testing and so on. How can you collaborate with the community and make money on the way?
This session is aimed at beginners or those who could use a good high level overview of different areas of Drupal.
Drupal 7 is about to be released sometime later this year. We don't yet know when, but it is steadily marching towards in its release cycle. As always, this new version of Drupal comes with all kinds of bells and whistles promising to improve our lives. What's even better is that many contributed modules are pledged to release on the day of Drupal 7's release. Automated testing is now the norm and Drupal Gardens is doing an immense deployment of beta testing on a Drupal 7 based service so no Drupal release will be as well tested as this one. Come see the improvements coming up in this release and see why the Drupal 6 maintainer is envious.
I've intended to announce this development at Drupalcon San Francisco but unfortunately the session on this was merged with a more general i18n session which was coupled by the ash cloud above Europe, so I could not go. Evidently, collaborative software translation is not a mainstream topic. On the other hand, I keep receiving requests of the general applicability of the tools Drupal.org uses about every two weeks, and this interest always amazes me. While the localization server tool used on localize.drupal.org grew out of needs of the Drupal community, the solutions were architected to be useful in a general purpose software translation environment. While the architecture was there, it was lacking useful UI controls to just run it as a generic software translation tool.
Existing non-Drupal users like the Gallery 2/3 project and the Musescore desktop app utilize custom data connector modules, which the localization server nicely supports, allowing for custom code to gather data for translation. Gallery even uses a custom Localization client port for clients to submit translations to the server, even though their software is not Drupal based. However, translating arbitrary software without writing your custom connector code was not possible earlier.
At the Hungarian community, we are organizing yearly local Drupal conferences ever since 2006 under the "Drupal Conference" and "Drupal Weekend" names. We've also just had our 22nd monthly meetup in a row. We've hosted Drupalcon Szeged 2008. Over these years, we've found that naming for all these events is tricky, and nowadays, the "Drupalcamp" name is sticky for local Drupal conferences. However István Palócz of the Hungarian community had a different dream around camps.
This year, we're gonna have the first Drupal Summer Camp in Hungary (and by the looks of Google search results maybe the first Drupal Summer Camp ever). Unfortunately (at least for my non-Hungarian speaking audience), the event is all in Hungarian (except all the jargon thrown around that is :).
The camp is on from the 23th of June to the 26th and is organized with community participation in mind. People can get experience translating interfaces and sharing their translations, look into drupal.org project maintainership aspects, work with the issue queues to get problems solved, etc. By the nature of being together for four consecutive days (with a complete dormitory floor rented for cost-concious and/or community addicted attendees), lots of hands-on experience can be gathered.
Website admin skins/themes clearly have a big market. Just see many different options for Drupal hosted on drupal.org or some nice commercial ones on themeforest.net (not Drupal specific). Administration themes are great when you'd like to separate your administration interface from your front-end. And several Drupal studies showed that many people need this separation to understand where content is managed and what does everybody else see of the site. Of course your mileage may vary and there are all kinds of sites where community participation is on a level that admin/front end separation is meaningless. The point of this blog post is not even administration themes, so let's shelve that discussion.
Websites often replace traditional web applications as well, when the "front end" of the website is already some kind of data input / management UI, where the data is usually not in the form of textual posts with comments tagged by topics. Navigation is not primarily search based because pages for different functionality in the site are not searchable in a traditional sense. Finally, menus are not built by the site builders but rather the application author, putting in menus and navigational elements via code suited for the application.
In Drupal, this kind of theming needs a different approach compared to traditional admin themes, because the web application will most probably not offer the usual Drupal admin functions. For this role, a theme more like the general ones of themeforest's admin looks fits more.
With Drupalcon San Francisco just a few days away, being another great event including two days of "pure coding" and a ChX coder lounge each day for those who are inclined to join, I figured it would be a good idea to share some tips if you are about to work on Drupal 6 issues. Given the close to 2700 attendees coming, I don't know how many to expect on the code sprint days right before and after the conference, but I guess there will be people with diverse backgrounds as usual.
Drupalcamps are growing like mushrooms around this region of Europe. While we've had one day Drupal conferences in Hungary for several years now, the Czechs joined the ranks last year and now Slovaks and Romanians will enjoy a gathering of like-minden drupalers this year. The next event coming up is Drupalcamp Bratislava on Feb 27th and 28th, 2010.
As it turns out, the honored Jakub Suchy will not be able to present at this Drupalcamp about Drupal security, so I was approached to step in. I was more than happy to participate and continue spreading awareness of security best practices. I hope to pack a good amount of tips for site maintainers and module/theme developers at the same time.
As it currently looks like, Drupalcamp Bratislava is full, but you can still sign up for the waiting list in case not all registered attendees will be able to come.
I remember how skeptical I was looking at some presenters traveling around to multiple conferences with "the same" presentation a decade or so ago. Having been a course instructor for years and being a presenter for even longer, it looks completely different now. It's not that the topics you cover under the same looking umbrella can be quite different, you also find much better ways to express whatever you want to tell your audience as you experience feedback.
Of course the best would be to present your story crystal clear from the start, but despite being an enthusiastic follower of Garr Reynolds and Nancy Duarte, you'll undoubtedly need lots of time anyway to take a relaxed look on your story and distill to the level needed to form a great presentation. I've actually found it quite hard to refine my slides without actually showing/presenting them to an audience. The faces, questions, smiles and sometimes plain staring expressions you get tell you how you'd done and you can derive ways of how can you improve.
Two interesting examples are my slides on Drupal 7 and localize.drupal.org.
Last year DrupalCon Szeged 2008 introduced a few new technologies for helping people find out where things are happening both in terms of on-site conference activities and extracurricular fun. We've introduced a digital whiteboard which was using fixed size Drupal node displays set up in a wiki form, so everyone could edit any whiteboard item. This was helpful for people checking in from hotel rooms for announcements and also on-site because the building was so huge (see below) that running to the whiteboard every so often was not an option.
Even after 1.5 years, people keep asking about certain things on the website, so I decided to start off with the whiteboard and explain how we did it. Sharing the exact solution we used to do would not cut it though, since we used Drupal 5 and some custom code based formatting, which would not be up to today's standards. So I recreated the whiteboard using the latest Acquia Drupal codebase instead, merely configuring some content types, permissions and a view.
For this starter recipe I used Drupal core and Views only from the Acquia Drupal package, so you can also repeat with just these modules only.
In an attempt to revitalize my blog, I recently switched themes, this time to the cool Magazeen theme and decided to highlight some fresh and inspiring content by cherry-picking tweets. Inspired by Dan Cederholm's Simplebits, where "tweets" were mixed with blog posts way before twitter was started, I decided to aggregate some of my tweets on my site. Let's see how I've done it.
