Get our Newsletter






Introduction to GraphQL

Amazee Labs is heavily invested in exploring and adopting new techniques and technologies. For nearly two years we’ve been openly exploring Decoupled Drupal. Among the things that we’ve researched during this time, React and GraphQL certainly stand out as two of the sharpest new tools in our ever growing toolbox. Based on these, we’ve since established a full application architecture and infrastructure.

In the upcoming weeks leading up to DrupalCon Vienna, we want to share our experiences and learnings in a series of blog posts.

July 28, 2017

Nested Paragraphs translation

Looking back, translating content in Drupal 7 wasn't a straightforward task. It involved enabling a number of modules to do all the translations properly. And in Drupal 8, the Multilingual Initiative took big steps forward to enhance multilingual support for users.

Since its introduction in May, 2011, huge efforts by everyone involved resulted in hundreds of issues resolved and many great improvements have since been made that now drastically simplifies the site building process.

June 30, 2017

Creating nested lists with panelizer and view panes

For one of our customer projects, we wanted to have a list with all past projects. There are two types of projects selected among applicants every year: a winner and there are several finalists or runner ups.

The idea was to show the winner of each year followed by the finalists/runner ups of the year. This should be done in a list where the actual year is the top one followed by the others.

June 25, 2015
When
Where
Zurich

Drupal 7 total language fallback

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 ;)

Languages

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.

April 28, 2015
5