Since the release of Drupal 8, Drupal 6 is no longer supported by the Drupal Community. Because of this, many sites need to be migrated to Drupal 7 or 8, and quickly!

That means that at Evolving Web we've been doing a lot of Drupal 8 migration projects lately, either D6 to D8 or D7 to D8. I would like to talk about the things we have to take into account when running these projects.

As of December 4th, 2016, at least 82,000+ sites are running Drupal 6. Since Drupal 6 is no longer actively supported by the Drupal community, a lot of people urgently need to migrate to a newer version! So, what if you have of those sites and want to move to the most recent Drupal version?

As Drupal 8 "relies" on a Configuration Management (CM) system, one of its cool improvements is restoring a Drupal 8 site from an existing configuration instead of only a database dump. This means that you can do a brand new Drupal installation and replicate an existing configuration on your new fresh database!

Whenever we start a new Drupal project, we have to choose what kind of theme we're going to create. Are we going to use a framework like Bootstrap or Zurb Foundation? If so, do we start with a contrib base theme or do we implement the framework ourselves? Are we going to use a classic Drupal base theme like Zen or AdaptiveTheme? Or are we going to build the theme 'from scratch' starting with Drupal core or a core base theme? 

Drupal 8 Configuration Managment (CM) is a "killer feature" for a web Content Management System (CMS). When setting up a Drupal site, we spend a lot of time on site configuration: Roles, Permissions, Content Types, Menus, Vocabularies, etc. In most CMS's, all these changes are stored in their databases, making it hard to deploy, track, reuse and rollback important changes.

Drupal 8 Configuration Managment (CM) is a "killer feature" for a web Content Management System (CMS). When setting up a Drupal site, we spend a lot of time on site configuration: Roles, Permissions, Content Types, Menus, Vocabularies, etc. In most CMS's, all these changes are stored in their databases, making it hard to deploy, track, reuse and rollback important changes.

A detailed tutorial on creating custom fields in Drupal 8 using the field API.

A detailed tutorial on creating custom fields in Drupal 8 using the field API.

If you are a web designer, chances are you have heard about Material Design.

Material Design is a popular "design language" developed by Google that came out in June 2014. Since then, it has kind of become the visual identity of most of Google's mobile applications for Android. Many mobile app developers are using it and the approval rate among web designers is also rising, mostly because of its simplicity and the influence of mobile apps on responsive design.

If you are a web designer, chances are you have heard about Material Design.

Material Design is a popular "design language" developed by Google that came out in June 2014. Since then, it has kind of become the visual identity of most of Google's mobile applications for Android. Many mobile app developers are using it and the approval rate among web designers is also rising, mostly because of its simplicity and the influence of mobile apps on responsive design.

Drupal has a powerful menu system, but most of the content on a typical Drupal website doesn't end up in the menu navigation. Articles, blog posts, events, you name it. Most content is linked to from views, not directly from a menu. So how do we make it easy for users to know where they are in the hierarchy of the site if they are looking at content that isn't in a menu?

Drupal has a powerful menu system, but most of the content on a typical Drupal website doesn't end up in the menu navigation. Articles, blog posts, events, you name it. Most content is linked to from views, not directly from a menu. So how do we make it easy for users to know where they are in the hierarchy of the site if they are looking at content that isn't in a menu?