1) Johanna Bergmann and Megan Sanicki took the stage early this morning to discuss the importance of Drupal.org's Supporting Partner Program. With financial support from businesses worldwide, Drupal.org is able to employ a tech team, whose primary goal it is to continually improve the community's home on the web.
2) Lisa Welchman was Wednesday's keynote speaker. Her talk was about governing our community and how to strike a balance between too much control and not enough. She encouraged us to hold close our culture and our values as a community, but also warned us not to exclude outsiders, those that aren't hard-core tech.
3) Drupalcon Labs are new to the schedule this year, and very popular it seems. These two-hour, hands-on sessions have proven to be chock-full of relevant information. Today's lab Twig It — Ship It! demonstrated Twig as an effective and easier-to-understand alternative to Drupal's previous PHPTemplate theme engine.
4) Our very own Michael Schmid presented a Business Showcase today, where he explained our second-screen solution for The Voice of Switzerland. And be sure to check out his encore presentation tomorrow, where he will discuss the ins and outs of Translation Management.
5) And finally, a few of us Amazee's joined the crowd at Vyšehrad Beer Garden to enjoy some cold drinks, brats, and beautiful views of Prague.
Last year at Drupalcon, Munich we introduced The Periodic Table of Drupal Modules, much to the delight of the Drupal community. This year, we've updated our table with a current list of the most-commonly-installed modules and are providing it to you at the wallpaper size of your choosing. In addition, we're introducing a handful of other custom-designed, Drupal-related wallpapers for your enjoyment. If you'd like a custom-sized wallpaper for your device, please leave us a comment below and we'll try to accommodate those we've left out.
1) The lean booth: As you might know (from our previous blog post), we had to come up with a new booth concept. A visit to the do-it-yourself shop did the rest and it took us (just) an amazing 20 bucks to get our platinum cottage refurbished. A rejuvenation cure!
Over 1600 Drupalistas will be heading to Prague and every single attendee will bring her & his story of traveling to Prague, getting infected by the Drupal flu and leaving with a ton of unique impressions: Stemming from late night sessions in the coder lounge, attending the trivia night or catching up with fellows in a beer garden! They are all valuable parts of the DrupalCon experience and illustrate the diversity of the community.
For this reason we have launched Contrib.to, a platform to share and preserve these memories.
The platform is built on the battle proven foundations of Drupal 7 and Likemag, a disruptive client project.
We want to invite you to share your impressions with the rest of the community!
(Image: DrupalCon Prague)
The majority of the Amazee Labs team will be heading to Prague. Here are you chances to meet up with us:
Sunday, 22 September
Monday, 23 September
- 08:00 - 15:15 CXO @ Panorama Hall · Wunderkraut
- Drupal 8 Multilingual sprint @ Prague Convention Centre, in Terrace 2
Tuesday, 24 September
- 13:00-15:15 Performance Lab @ Club C · Cloud Troopers (Co-hosted by Schnitzel)
- Exhibit Hall @ Booth 2
Wednesday, 25 September
- 10:45-11:45 How To Provide A Real-Time Second Screen Experience With Drupal @ Terrace 1 · Capgemini (Hosted by Schnitzel)
- Exhibit Hall @ Booth 2
Thursday, 26 September
- 13:00-14:00 Translation Management @ Club A · Amazee Labs (Co-hosted by Schnitzel)
- 14:15-15:15 Translation Management Tool Deep Dive @ Dressing Room, Congress Hall 123 (Co-hosted by Schnitzel)
- Exhibit Hall @ Booth 2
- 21:00- Trivia Night @ Hilton Hotel
Friday, 27 September
- Drupal 8 Multilingual sprint @ Panorama Hall · Wunderkraut
Saturday, 28 September
Sunday, 29 September
For real-time updates of our whereabouts, especially for our evening outings, check our Twitter account.
Our preparations for DrupalCon Prague are slowly reaching fever pitch. Since it's less than a fortnight to go we want to share some of our enthusiasm with you. Here is an exclusive preview of two goodies we'll be giving away at the conference.
The first item are gorgeous stickers which certainly will visually enhance any object and spread the message of what Drupal does.
The second one is a super limited edition t-shirt with the same 'Making your web work' motive.
The major question that remains is how you'll get your hands on them. For a sticker just swing by our booth and pick one up, regarding the t-shirt let's just say: watch this space.
Hopefully these two items will have whet your appetite, but remember there is one further item we'll keep under lock and seal until Prague...
Stay in touch – join our newsletter!
Photo by Bjørn Giesenbauer
In less than a month's time the focus of the global Drupal community will shift to the capital of the Czech Republic for the European edition of this year's DrupalCon.
We are proud to announce that for a third year in a row we decided to sponsor Europe’s premier Drupal event. And again, we opted to increase our contribution and will welcome you at our platinum booth in the exhibit hall!
Omega 4 looks very different than Omega 3. When we first wrote about some of their differences back in January, we reported on four major themes:
- Zones & Regions
- Pluggable Layouts
After getting our hands dirty for the first time with the new theme, these were the most obvious changes. And while these topics are still important to note for those still looking to make the transition from 3 to 4, there are other improvements to the theme which also deserve attention.
In general, Omega 4 is a vastly more flexible version of its predecessor. As a follow-up post to our original findings, here are even more reasons why:
Essentially, Omega 4’s theme extensions have been improved in four areas: layout, development, asset management, and compatibility improvements. We’ve touched on the new layouts before, but there’s more to them you should know:
Total Layout Control
With Omega 4 Layouts, you can define how pages are laid out through code. There are no predefined breakpoints which makes for a completely fluid (truly responsive) site.
Layouts can be added via the “layouts” folder of an Omega 4 sub-theme.
Given the file structure in the example above, you could even switch your layout contextually with a hook_omega_layout_alter function:
This feature completely removes the need for the Delta module commonly used with Omega 3.
Development, made easier
Some cool new features have also been added to assist in the theme development process. In a nutshell (and taken from a great resource, Omega 3.x vs. Omega 4.x - Comparing Apples and Oranges), Omega 4 provides the following development additions:
- Rebuild theme registry on page load
- Rebuild CSS and JS aggregates on page load
- Browser width indicator
- Region demo mode
(Some pretty spiffy improvements if you ask us...)
These features make for better site performance and happier Frontend lives.
Browser & Viewport Compatibility
Conditional HTML classes are now added, for example “lte-ie9” in Internet Explorer versions 8 and below. This is a big win when optimizing sites for cross-browser consistency.
There’s also Cleartype support for Windows, customizable Viewport metatags, and ChromeFrame & IE Edge support.
Next — the powers of Drush! If you navigate (via the command line) to a Drupal site with Omega 4 & Drush installed, there’s a slew of new Omega-specific commands, with two notable ones being omega-wizard (owiz) and omega-guard (ogrd).
Omega-wizard is a guide through the process of setting up and enabling a subtheme, and omega-guard enables the use of Omega 4‘s LiveReload built-in support.
Have a look at the others as well. Omega-export and omega-revert can greatly assist during site-deployments.
Preprocess, Process, and Theme Files
And if you’re a developer fed up with the days of having cluttered, unorganized template.php files, this one’s for you. :)
Omega 4 allows the themer to provide separate preprocess, process and theme functions to their Drupal site via organized, structured theme files. These files are autoloaded and are no longer to blame for overloaded template.php files, especially in the case of themes requiring a heavy load of PHP.
Also, according to fubhy, the Omega 4 developer, “this feature has been improved tremendously since 3.x and performs much better now.”
Finally, and if you didn’t know already, SMACSS is where it’s at. Omega 4 has adopted the “Scalable and Modular Architecture for CSS” principals and applied them directly to both of its available subtheme starterkits.
If you’re not familiar with SMACSS however, it’s basically just a guiding set of methodolgies to write maintainable CSS. Due to CSS’s flexible nature, it’s easy to make a mess of it. SMACSS helps with that.
And if you’re going to use the omega-wizard Drush feature, go ahead and choose the “extended” starterkit. It has a fuller SASS structure included with more modular components, making it easier to understand and organize your project and different Drupal components.
So that's it for now! We're still loving Omega 4. Are you?
Ladies and Gentlemen, it's our absolute pleasure to introduce Amazee Labs' latest release: Classic Driver.
Here's a quick Drupal 7 question; imagine you've setup a panel page which, in a pane, includes a webform. Now a user tries to submit the form with invalid data. What's the expected behaviour?
Depending on your settings it can display a neat in-place notification or end in carnage and UX hell! To avoid the latter be sure to implement webforms this way:
- Open or create the webform node you want to use and navigate to the "Webform" tab. Enter the "Form settings". Here you can enter a "Confirmation message" and set the "Redirection location". In our implementation we went for "No redirect (reload current page)". The most important bit in this setting is that you tick the checkbox "Available as block". You can find it by expanding the "Advanced Settings" area. Once you made these setting save the node.
- Go to the desired panel, add the newly available webform block , which you can find in the "Miscellaneous" section of the "Add content to" modal window and save the panel.
- Now it is time to turn our attention back to the block we created in step one. Open it and make sure that you tick the the "Show all webform pages in block" checkbox and save the node again. That's all. The checkbox in this step is like Dries' hair gel - it is the glue that will make sure everything works and looks smooth.