Today our Group is launching Amazee Talents, a program to win bright minds like you for a 3 month internship at Amazee Labs or Amazee Metrics.
Get our Newsletter
Yesterday, just shortly after the sun sprung up and sparked southern California’s beautiful coastal lines, the doors of LA’s Convention Center opened. Welcoming with it, a first wave of eager Drupalistas and surrounding them by its air conditioned walls. And for the subsequent days that are surely to follow, it will continue to receive and house those, transforming it, to the home of DrupalCon 2015.
Reasons for language fallback
Let's assume you have a website divided by countries. The site structure is:
- Global (en, de, fr)
- Germany (de)
- France (fr)
- Switzerland (de, fr)
You have your content translated to three languages. Normally, this works, but there could be cases when you need languages per country. Words might have a slightly different meaning from country to country (examples) or spelling might be different (en-US vs en-GB, or using "ß" in de-DE vs "ss" in de-CH). Or, for example, the "Contact us" page can contain a country specific information - locations.
So, the site structure can be turned to:
- Global (en, de, fr)
- Germany (de-DE)
- France (fr-FR)
- Switzerland (de-CH, fr-CH)
This can bring a translation nightmare until you have a language fallback ;)
Having the language fallback, you would only translate strings/content to the "base" languages and, in special cases, you may also translate to "country" languages.
Fortunately, there is a module for that. The Language fallback.
Last week, a few coworkers and I went to the Drupal Developer Days in Montpellier. With the main focus being on sprints, contribution to core and on pushing the release of Drupal 8 forward, the Dev Days are a great event for drupalistas to meet the community, share knowledge and work on Drupal.
The DDD was the best drupal related event I’ve been to so far. Its relative small number of attendees - about 300 instead of the 2000+ that attend the european DrupalCons - made it effortless to meet new people. The event was well organised, with good infrastructure and freshly cooked meals every day.
As a site builder interested in contributing more to the community I started the first sprint day in the mentoring sprints learning the best practices for contributing to Drupal. I was surprised at the kindness and patience from the mentors who spend all their time making new members feel welcome at the expense of having fun with their own code and projects.
For the third time, Drupalcamp London warmly welcomed passionate drupalistas who flew in from all over the world to do Drupal, talk Drupal and live even more Drupal.
Voting for the Drupal Association Board’s Director At Large position opens this Monday, March 9th. My two main reasons for seeking this role, why I feel I am a qualified candidate, and a discussion on the responsibilities of this position are outlined in the following post.
For the first time, DrupalCon happened in Latin America! Dagmar, Emma and me spent a week in Bogotá to speak about Drupal and to connect with the local communities.
It is awesome to be here! Everything was well prepared and we were very warmly welcomed.
We just completed our third Drupal 8 project: SGG - Schweizer Gemeinnützige Gesellschaft. After relaunching our own website and helping out with Drupal.com (our first two Drupal 8 sites), we are excited to launch our first client website 100% on the upcoming major release of our favorite open source CMS.
After we had built the community site Intergeneration and the voting platform CHymne using Drupal 7, we now chose Drupal 8 for the relaunch of the corporate website of SGG. The compact feature of the site allowed us to apply the strengths of Drupal 8 as per today and so we created the association's new website relying entirely on Drupal 8 core functionality.
Building the new SGG website was a team effort; continue reading for the findings of each of us while we were creating the new site on the latest beta release of Drupal 8.