Inhalt abgleichen
Drupal.org - aggregated feeds in category Planet Drupal
Aktualisiert: vor 22 Minuten 37 Sekunden

Lullabot: Behind the Screens with Jason and Stew of Amazee Labs

9. Oktober 2017 - 6:00
In this episode, Chris sits down with Jason Lewis and Stew West of Amazee Labs to get the low down on Drupal Camp Cape Town. They discuss what it's like organizing a Drupal camp in Southern Africa; convince you to visit Cape Town; and give some thanks to their amazing colleagues at Amazee. Also, if the internet goes out, keep an eye out for Amazee's (probably) first ever touring Drupal band!

Daniel Pocock: A step change in managing your calendar, without social media

8. Oktober 2017 - 19:36

Have you been to an event recently involving free software or a related topic? How did you find it? Are you organizing an event and don't want to fall into the trap of using Facebook or Meetup or other services that compete for a share of your community's attention?

Are you keen to find events in foreign destinations related to your interest areas to coincide with other travel intentions?

Have you been concerned when your GSoC or Outreachy interns lost a week of their project going through the bureaucracy to get a visa for your community's event? Would you like to make it easier for them to find the best events in the countries that welcome and respect visitors?

In many recent discussions about free software activism, people have struggled to break out of the illusion that social media is the way to cultivate new contacts. Wouldn't it be great to make more meaningful contacts by attending more a more diverse range of events rather than losing time on social media?

Making it happen

There are already a number of tools (for example, Drupal plugins and Wordpress plugins) for promoting your events on the web and in iCalendar format. There are also a number of sites like Agenda du Libre and GriCal who aggregate events from multiple communities where people can browse them.

How can we take these concepts further and make a convenient, compelling and global solution?

Can we harvest event data from a wide range of sources and compile it into a large database using something like PostgreSQL or a NoSQL solution or even a distributed solution like OpenDHT?

Can we use big data techniques to mine these datasources and help match people to events without compromising on privacy?

Why not build an automated iCalendar "to-do" list of deadlines for events you want to be reminded about, so you never miss the deadlines for travel sponsorship or submitting a talk proposal?

I've started documenting an architecture for this on the Debian wiki and proposed it as an Outreachy project. It will also be offered as part of GSoC in 2018.

Ways to get involved

If you would like to help this project, please consider introducing yourself on the debian-outreach mailing list and helping to mentor or refer interns for the project. You can also help contribute ideas for the specification through the mailing list or wiki.

Mini DebConf Prishtina 2017

This weekend I've been at the MiniDebConf in Prishtina, Kosovo. It has been hosted by the amazing Prishtina hackerspace community.

Watch out for future events in Prishtina, the pizzas are huge, but that didn't stop them disappearing before we finished the photos:

Bay Area Drupal Camp: Sign-up for BADCamp Training Classes

8. Oktober 2017 - 19:17
Sign-up for BADCamp Training Classes Anne Sun, 10/08/2017 - 10:17am

The following training classess still have spots available:  

 

Local Drupal 8 Development with Containers - Wednesday

8am-noon - by Mobomo with Miles McLean and Cameron Eagans

There are many ways to develop a Drupal site, but there are few that offer as many advantages as a fully self-contained, local environment. This training session will get hands on with setting up an environment from scratch using Docker containers to emulate production servers, Composer to manage packages, Drush to manage configuration, Drupal Console to generate code, and source code management to tie it all together.

 

Getting Started with Drupal - Wednesday

by Agaric & Digital Echidna with Mauricio Dinarte

This training is aimed to people just starting with Drupal. Basic concepts will be explained are later put into practice. The objective is that someone, who might not even know about Drupal, can understand the different concepts and building blocks to create a website using this CMS.

 

SEO & Accessibility - Wednesday

by Hook 42 with Aimee Degnan and Carie Fisher

SEO stands for "Search Engine Optimization." Improving your website's SEO can translate into more visitors, better conversions, and more sales.

Accessibility refers to the design of products, devices, services, or environments for people who experience disabilities.

When properly configured, Drupal is a very SEO-friendly and Accessible web framework. The trick is to know which Drupal modules you need to install and how to optimally configure them. Configuration doesn’t stop at the module level - a solid content strategy is required to make the most Accessible and optimized website. “Content is King” and our job is to make Drupal showcase content in the most effective way to all consumers and search engines.

 

Object Oriented PHP - Wednesday

by Chapter Three

With the move to Drupal 8 everyone who works in the PHP layer will be exposed to more and more to object­ oriented code. Come learn the basics of working with objects in PHP and how OOP can help you to write well­ structured code

 

Drupal Crash Course for Non-Developers - Wednesday

by Promet Source with Margaret Plett

Are you responsible for project management, content, or vendor selection and preparing to work with Drupal? This one-day training delivers all of the tools you need to get started. Delivered by an Acquia Certified Drupal Developer, this training will answer the questions you didn’t even know to ask!

 

Component-based Theming with Twig - Thursday

by Forum One with Chaz Chumley

Join Forum One as they walk through the theming variations that started with the traditional theme-centric design and has quickly moved into component-based design. Together you will master Component-based theming with Twig as you work to identify patterns, define components, utilize command line tools such as Composer, NPM and Grunt to quickly create a PatternLab managed theme. Learn how to work smarter in developing components that can easily be integrated into project after project without having to recreate them yourself.

 

Theming Drupal 8 - Thursday

by Drupalize.me with Joe Shindelar

Themes combine HTML, CSS, JavaScript, and Drupal in order to make beautiful websites. Creating truly unique themes requires knowing how to use the Twig template language to manipulate HTML, how to add CSS and JavaScript assets in a way that's compatible with Drupal's caching, all while maintaining the flexibility that Drupal is known for.

 

Content Strategy for Drupal 8 - Thursday

by Evolving Web with Suzanne Deracheva

Drupal is a powerful tool for managing structured content. Many Drupal projects revolve around producing, displaying and organizing content effectively. This course will walk you through the process of creating a content strategy for your next Drupal project, and planning out how that content will be structured in Drupal. Whether you're creating a brand new site or migrating to Drupal, you'll learn techniques that will help you build a solid content strategy and a successful Drupal website.

 

Intro to Backdrop CMS - Thursday

by Nate & Jen Lampton

Backdrop CMS is for the small to medium sized business, non-profits, educational institutions, and companies or organizations who are delivering comprehensive websites on a budget. This introductory training will cover the basics of creating and administering a website with Backdrop CMS.

 

Drupal 8 Configuration System Basics - Thursday

by DrupalEasy with Mike Anello

The Drupal 8 configuration system can provide great advantages to managing the configuration of a site, but it can also cause massive headaches if used improperly. This presentation will provide an overview of how the Drupal 8 configuration system works, best practices on basic workflows to utilize it effectively, and a small sampling of some of the contributed modules available to enhance it.

 

 

BADCamp is 100% volunteer run and 100% funded by our sponsors and the support of our local community. Thank you!

Drupal Planet

Matt Glaman: Drupal 8 Development Cookbook - Second Edition

8. Oktober 2017 - 2:54
Drupal 8 Development Cookbook - Second Edition mglaman Sat, 10/07/2017 - 19:54

During DrupalCon Vienna, the second edition of the Drupal 8 Development Cookbook was published! The Drupal 8 Development Cookbook published just over a year ago, right after Drupal 8.1 was released. I had written the book for 8.0 with "just in case" notes for what might change in Drupal 8.1. What I was not prepared for: how well the minor release system worked and provided rapid gains in feature changes.

Drupal.org blog: An update on projects created for Drupal

7. Oktober 2017 - 9:00

About six months ago we made a significant change to the way that modules, themes, and distributions are created on Drupal.org.

In the past, contributors had to first create a sandbox project, and then request manual review of their project in the Project Applications issue queue. The benefit of this community-driven moderation process was that modules were vetted for code quality and security issues by a group of volunteers. Project maintainers who completed this process also received the benefit of security advisory coverage from the Security Team for stable releases of their projects.

Unfortunately, the rate of project applications outpaced what volunteers could keep up with, and many worthy projects were never promoted to full project status, or moved off of Drupal.org to be hosted elsewhere.

To ameliorate this issue, we changed the process so that any confirmed user on Drupal.org may now make full projects.

To mitigate the risks of low code quality or security vulnerabilities we added new signals to project pages: including highlighting which release is recommended by the maintainer, displaying recent test results, and indicating whether the project receives security coverage both on the project page and in the composer 'extra' attribute. We're continuing to work on identifying additional signals of project quality that we can include, as well as surfacing some of this information in Drupal core. We also converted the project applications issue queue into a 'request security advisory coverage' issue queue.

What we hoped to see

We knew this would be a significant change for the project and the community. While many community members were excited to see the gates to contribution opened, others were concerned about security issues and Drupal's reputation for code quality.

Our prediction was that the lower barrier to contribution would result in an increase in full projects created on Drupal.org. This would indicate that new contributors or third party technology providers were finding it easier to integrate with Drupal and contribute those integrations back for use by others.

At the same time, we also expected to see an increase in the number of full projects that do not receive coverage from the security team. The question was whether this increase would be within an acceptable range, or represent a flood of low quality or insecure modules.

The results

The table below provides statistics about the full projects created on Drupal.org in the 5 months before March 17th, 2017 - when we opened the creation of full projects to all confirmed users.

Full projects created from 2016-10-16 to 2017-03-17…

#

% of projects created in this period

… without stable release

431

55.76%

… with stable releases

342

44.24%

… with usage >= 50 sites

237

30.66%

… with usage >= 50 sites and without stable release

68

8.80%

… with usage >= 50 sites and with stable release

169

21.86%

… with an open security coverage application*

18

2.33%

Sub-total with security coverage

342

44.24%

Sub-total without security coverage

431

55.76%

Sub-total with security coverage and >=50 usage

169

21.86%

Sub-total without security coverage and >= 50 usage

68

8.80%

Total

773

* note: full projects that did not have stable releases were not automatically opted in to security coverage when we opened the full project creation gates.

… and this table provides statistics about the projects created in the 5 months after we opened the creation of full projects to all confirmed users:

Full projects created from 2017-03-17 to 2017-08-16…

#

Diff

% of projects created

Diff %

… without stable release

851

+420

69.53%

+97%

… with stable releases

373

+31

30.47%

+9%

… with usage >= 50 sites

156

-81

12.75%

-34%

… with usage >= 50 sites and without stable release

64

-4

5.23%

-6%

… with usage >= 50 sites and with stable release

92

-77

7.52%

+46%

… with an open security coverage application

62

+44

5.07%

+344%

Sub-total with security coverage

182

-160

14.87%

-53%

Sub-total without security coverage

1,042

+611

85.13%

+242%

Sub-total with security coverage and >=50 usage

54

-115

4.41%

-32%

Sub-total without security coverage and >= 50 usage

102

+34

8.33%

+150%

Total

1,224

+451

+58%

As you can see, we have an almost 58% increase in the rate of full projects created on Drupal.org. We can also see a significant proportional increase in two key areas: projects with greater than 50 site usage and no security coverage(up 150% compared to the previous period), and projects that have applied for security coverage(up 344% compared to the previous period). Note: this increase in applications is for projects *created in these date ranges* not necessarily applications created overall.

This tells us that reducing friction in applying for security coverage, and encouraging project maintainers to do so should be a top priority.

Finally, this last table gives statistics about all of the projects currently on Drupal.org, regardless of creation date:

Full projects (7.x and 8.x)

#

% of Total

Rate of change after 2017-03-17

… with the ability to opt into security coverage

8,718

36.15%

-1.33%

… with security coverage and stable releases

8,377

34.74%

-1.49%

… without security coverage

15,396

63.85%

+1.33%

… without security coverage and with stable releases

464

1.92%

+1.04%

… with security coverage and >=50 usage
 

6,475

66.91 / 26.85%

-0.54%

… with security coverage and stable releases and >=50 usage

6,308

65.19 /26.16%

-0.65%

… without security coverage and >=50 usage

3,202

33.09 /13.28%

+0.54%

… without security coverage and with stable releases and >=50 usage

130

1.34 /0.54%

+0.51%

Sub-total with >=50 usage

9,677

40.13%

-1.72%

Total

24,114

From the overall data we see approximately what we might expect. The increase in growth of full projects on Drupal.org has lead to a modest increase in projects without security coverage.

Before the project application change, all full projects with stable releases received security advisory coverage. After this change, only those projects that apply for the ability to opt in(and then do so) receive coverage.

What has this meant for security coverage of projects hosted on Drupal.org?

1.92% of all full 7.x and 8.x projects have stable releases, but do not receive security advisory coverage. It is likely no accident that this translates into 464 projects, which is nearly equivalent to the number of projects additional projects added compared to our old growth rate.

Of those only 130 of those projects report more than 50 sites usage(or .54% of all 7.x and 8x full projects).

Next steps

From this analysis we can conclude the following:

  1. The opening of the project application gates has dramatically increased the number of projects contributed to Drupal.org.

  2. It has also increased the number of projects without security coverage, and the number of applications for the ability to opt in to coverage among new projects.

In consultation with the Security Working Group, we recommend the following:

  • For now, leave the project creation projects as it stands today - open to contribution from any confirmed user on Drupal.org.

    • Less than 2% of all Drupal projects with stable releases currently lack security coverage. The rate at which this is increasing is significant (and in the wrong direction) but not rapid enough to merit changing the project application policy immediately.

  • Solve the problem of too many security advisory coverage applications. The security advisory application queue has the same problem that the old project applications queue had - not enough volunteers to manually vet all of the applications - and therefore a significant backlog of project maintainers waiting on the ability to opt into coverage.

    • Recommendation: Implement an automated best practices quiz that maintainers can take in order to be granted the ability to opt into security advisory coverage. If this process is as successful as we hope, we may want to consider making this a gate on stable releases for full projects as well.

We look forward to working with the Security Working Group to implement this recommendation and continue to improve the contribution experience on Drupal.org, while preserving code quality and security.

Annertech: DrupalCon Vienna 2017 - a Retrospective

6. Oktober 2017 - 22:21
DrupalCon Vienna 2017 - a Retrospective

Last week the Annertech team headed to Vienna for a week of Drupal learning and sharing. With thirteen different tracks and various summits, there was a lot of great sessions to choose from. We were also privileged and honoured to have the opportunity to present five sessions ourselves, and of course, we once again played host to the Drupal Trivia Night.

Dries Buytaert: Hermès using Drupal

6. Oktober 2017 - 17:40

Since its founding in 1837, Hermès has defined luxury. Renowned as an iconic brand within the fashion industry, Hermès is now setting the trend for how customers shop online. This week, Hermès launched its new site in Drupal!

Hermès married the abilities of Drupal as a CMS and Magento as an eCommerce engine to provide their customers with highly engaging shopping experience. Hermès' new site is a great example of how iconic brands can use Drupal to power ambitious digital experiences. If you are in the mood for some retail therapy, check out https://www.hermes.com!

Acquia Developer Center Blog: Continuous Integration Testing with Acquia Cloud CD

6. Oktober 2017 - 16:03

In my role as a Solutions Architect at Acquia, it’s exciting for me to be working with a growing number of customers who are moving from agile development processes to Continuous Integration (CI) and even Continuous Delivery (CD) processes.

Acquia Cloud CD provides the platform to enable this migration, however customers often ask us for best practices on their journey to a fully automated Continuous Delivery/Deployment model.

Tags: acquia drupal planet

Valuebound: An overview of JSON API: A text-based data exchange format

6. Oktober 2017 - 11:35

People develop APIs for a variety of reasons, such as to create a tool to facilitate internal processes or an external product for customers or to build a third party tool. And for such purpose JSON comes to the rescue. The open standard format JSON follows shared conventions that help in increasing productivity, take advantage of generalized tooling, and focus on the web applications. 

If you are a developer you must have noticed that there is very little information on the web regarding JSON API when compared to its usability. In this blog post, I will share an overview of JSON API. Let's try and understand what is JSON API? Its advantages over…

Valuebound: An overview of JSON API: A text-based data exchange format

6. Oktober 2017 - 11:35

People develop APIs for a variety of reasons, such as to create a tool to facilitate internal processes or an external product for customers or to build a third party tool. And for such purpose JSON comes to the rescue. The open standard format JSON follows shared conventions that help in increasing productivity, take advantage of generalized tooling, and focus on the web applications. 

If you are a developer you must have noticed that there is very little information on the web regarding JSON API when compared to its usability. In this blog post, I will share an overview of JSON API. Let's try and understand what is JSON API? Its advantages over…

ADCI Solutions: At DrupalCon 6204 sandwiches were eaten. What else should you know?

6. Oktober 2017 - 5:12

A week has passed since the end of DrupalCon Vienna. It was a huge milestone for our team and we're happy to keep up with the speed of Drupal evolution.

 

Missed the event? Here are some outputs.

 

Valuebound: How to Handle Resource Intensive Tasks on Queue With Drupal Queue Worker/API

6. Oktober 2017 - 3:34

It's never too late to share something useful with mates. And in this blog, I am going to discuss Queue Worker/API and how to implement it in Drupal 8. After completing this blog cum tutorial you will find yourself at a moderate level of expertise in implementing Queue API.

A couple of months back, we had a situation in one of our project where we had to pull data from a centralized server and update that content to the site almost every day. In order to overcome this scenario, we started using cron, but faced a situation where we were missing few contents because of time out. After a little research and discussion, we (our team) decided to implement queue worker. And yes! It worked.

Let’s start with Queue API.

Queue API enables us to handle a…

Nextide Blog: Untapped areas for Business Improvements

6. Oktober 2017 - 0:24

Many organization still struggle with the strain of manual processes that touch critical areas of the business. And these manual processes could be costlier that you think. It’s not just profit that may be slipping away but employee moral, innovation, competitiveness and so much more.

By automating routine tasks you can increase workflow efficiency, which in turn can free up staff for higher value work, driving down costs and boosting revenue. And it may be easier to achieve productivity gains simpler, faster, and with less risk that you may assume.

Most companies with manual work processes have been refining them for years, yet they may still not be efficient because they are not automated. So the question to ask is, “can I automate my current processes?”.

Lullabot: Web Accessibility with Marcy Sutton

5. Oktober 2017 - 18:00
Mike and Matt are joined by renowned web accessibility expert Marcy Sutton, along with Lullabot's own Helena McCabe to explore various web accessibility topics.

Ixis.co.uk - Thoughts: Ixis lands new energy sector contract

5. Oktober 2017 - 15:55
Ixis, a leading Drupal specialist signs deal to provide development, hosting and support services to international energy company Uniper.

Roman Agabekov: Sending emails from Drupal-powered sites. Setting up Exim under Debian

5. Oktober 2017 - 15:47
Sending emails from Drupal-powered sites. Setting up Exim under Debian

Once you have the web server set up and running, you need to make sure your Drupal site can send emails, like registration confirmation, password change etc.

For inbound email, you may want to use email services like that offered by Google Apps. They offer good spam protection and secure storage.

To send email from a Drupal-powered site, you can use an SMTP module and do it all through a third party mail service. Alternatively, you can set up your own SMTP server. This article describes setting up an Exim server that allows sending emails.

admin Thu, 10/05/2017 - 13:47 Tags

InternetDevels: New opportunities for websites: congrats on Drupal 8.4.0 released!

5. Oktober 2017 - 13:07

Every six months, there comes a fresh Drupal 8 minor release full of lucrative features — it’s the essence of Drupal 8’s continuous innovation policy. And another big day has come! Drupal 8.4.0 is out on October 4, making this autumn especially rich in gifts. Just two weeks after the appearance of Drupal Commerce 2.0 for Drupal 8 online stores, Drupal 8.4.0 takes its turn in the spotlight. Let’s see why.

Read more

Paul Johnson: Introducing Drupal's vast Creative Commons image library

5. Oktober 2017 - 10:14

For several years a team of photographers have captured the essence of DrupalCon through the lens. Michael Cannon and more recently Suzanne Coates have done a sterling job formalising the photographic efforts into a professional (volunteer) operation. Not only is this a prime example of contributing to open source without code, we have curated a vast library of Creative Commons licensed images available for anyone to use.

Our long term objective has been to create a large library of high quality Drupal related imagery available for free so journalists, bloggers, Drupal end users and community members can easily find photos to brighten your news articles, blog posts, marketing materials. Please respect the CC licensing which requires attribution to the photographer. I look forward to seeing many more of these images appearing across the internet.

Below are links to the Flickr Groups for Drupal and DrupalCon's leading to over 10,000 images. Huge thanks to the many photographers who have contributed to this vast and colourful resource.

DrupalCon Mumbai Dries mass selfie. Photo: Michael Cannon

Sprint first timers at DrupalCon Barcelona 2016 Photo: Josef Jerabek

DrupalCon Vienna 2017 PreNote - Photo Dominik Kiss

Acquia Partner summit at DrupalCon Vienna 201. Photo Paul Johnson

Dries Buytaert delivers his State of Drupal Keynote 2017. Photo by Paul Johnson

Enlightened by the code. Photo by Boris Baldinger

Drupal Mentors - DrupalCon Dublin 2016. Photo Michael Cannon

Reflections of the group photo at DrupalCon Barcelona. Photo: Josef Jerabek

DrupalCon Amsterdam - Coder vs. Themer. Photo Bastian Widmer

Photo Michael Cannon

Lullabot: Lullabots Speaking at BADCamp

5. Oktober 2017 - 1:24

Are you going to San Francisco for BADCamp? No need to wear some flowers in your hair (although that would be festive), but you should definitely check out these presentations brought to you by our Lullabots and the Drupalize.Me team. The event will be held October 18-21 at the University of California at Berkeley. And, if you haven't registered yet, here's a handy link for convenience! It's FREE!

Intro to Backdrop CMS Thursday, October 19, 8:00 am - 5:00 pm

with Jen & Nate Lampton, Senior Technical Architect at Lullabot

If you aren't already familiar with Backdrop CMS, it's a simple and easy-to-use CMS built for the budget-conscious SMBs, educational institutions, and non-profits that need comprehensive CMS solutions that won't break the bank. Jen and Nate will give you an intro to Backdrop CMS and conduct a hands-on site building session from exploring pages and posts to deploying changes using Configuration Management. Check out the full details as there are pre-requisites for this session.

Theming Drupal 8 Thursday, October 19, 8:00 am - 5:00 pm

with Joe Shindelar, Lead Developer & Lead Trainer at Drupalize.Me

Front-end developers: You're probably in a situation where you have an existing site that needs a little facelift or you're creating a new theme from scratch. Joe will show you everything you need to know about how Drupal 8's theme system works so you can make your websites beautiful. Also, if you attend this session, Joe has a little Drupalize.Me gift for your continued learning.

Debugging, Profiling, & Rocking Out with Browser-Based Developer Tools! Friday, October 20, 1:30 pm - 2:15 pm

with Mike Herchel, Senior Front-End Developer at Lullabot

Front-end developers have come to rely on browser-based tools for developing the modern web, but keeping up with the continuously evolving changes and features often presents challenges. Never fear! Mike will make it simple by walking you through live examples sharing tricks and tips for using Chrome, Firefox, and Safari developer tools, as well as common troubleshooting solutions.

So long and thanks for all the requests: Front-end performance in the age of http/2 Friday, October 20, 4:45 pm - 5:30 pm

with Marc Drummond, Senior Front-End Developer at Lullabot

Curious to know how http/2 affects front-end performance when aggregating your CSS and JS? Marc says, "Don't panic!" New front-end performance techniques don't have to be drastically different from what you already know. In addition to recapping the basics of how http/2 is changing the way browsers process requests, Marc will take a look at performance strategies, stats, and studies on http/2 that will encourage attendees to continue the conversation and knowledge-sharing.

Big BADCamp Party Friday, October 20, 8:00 pm - 1:00 am 

And, of course, don't miss the party! We're proud to be a sponsor this year.

Photo by Changyu Hu

Drupal blog: Drupal 8.4.0 is now available

4. Oktober 2017 - 22:20
What's new in Drupal 8.4.0?

This new version is an important milestone of stability for Drupal 8. It adds under-the-hood improvements to enable stable releases of key contributed modules for layouts, media, and calendaring. Many other core experimental modules have also become stable in this release, including modules for displaying form errors inline and managing workflows.

The release includes several very important fixes for content revision data integrity as well as an update to stop the deletion of orphaned files that was causing data loss for many sites, alongside numerous improvements for site builders and content authors.

Download Drupal 8.4.0

Important: If you use Drush to manage Drupal, be sure to update to Drush 8.1.12 or higher before updating Drupal. Updating to Drupal 8.4.0 using Drush 8.1.11 or earlier will fail. (Always test minor version updates carefully before making them live.)

Inline Form Errors

The Inline Form Errors module provides a summary of any validation errors at the top of a form and places the individual error messages next to the form elements themselves. This helps users understand which entries need to be fixed, and how. Inline Form Errors was provided as an experimental module from Drupal 8.0.0 on, but it is now stable and polished enough for production use.

Datetime Range

The Datetime Range module provides a field type that allows end dates to support contributed modules like Calendar. This stable release is backwards-compatible with the Drupal 8.3.x experimental version and shares a consistent API with other Datetime fields. Future releases may improve Views support, usability, Datetime Range field validation, and REST support.

Layout Discovery API

The Layout Discovery module provides an API for modules or themes to register layouts as well as five common layouts. Providing this API in core enables core and contributed layout solutions like Panels and Display Suite to be compatible with each other. This stable release is backwards-compatible with the 8.3.x experimental version and introduces support for per-region attributes.

Media API

The new core Media module provides an API for reusable media entities and references. It is based on the contributed Media Entity module.

Since there is a rich ecosystem of Drupal contributed modules built on Media Entity, the top priority for this release is to provide a stable core API and data model for a smoother transition for these modules. Developers and expert site builders can now add Media as a dependency. Work is underway to provide an update path for existing sites' Media Entity data and to port existing contributed modules to the refined core API.

Note that the core Media module is currently marked hidden and will not appear on the 'Extend' (module administration) page. (Enabling a contributed module that depends on the core Media module will also enable Media automatically.) The module will be displayed to site builders normally once once related user experience issues are resolved in a future release.

Similarly, the REST API and normalizations for Media are not final and support for decoupled applications will be improved in a future release.

Content authoring and site administration experience improvements

The "Save and keep (un)published" dropbutton has been replaced with a "Published" checkbox and single "Save" button. The "Save and..." dropbutton was a new design in Drupal 8, but users found it confusing, so we have restored a design that is more similar to the user interface for Drupal 7 and earlier.

Both the "Comments" administration page at `/admin/content/comment` and the "Recent log messages" report provided by dblog are now configurable views. This allows site builders to easily customize, replace or clone these screens.

Updated migrations

This release adds date and node reference support for Drupal 6 to Drupal 8 migrations. Core provides migrations for most Drupal 6 data and can be used for migrating Drupal 6 sites to Drupal 8, and the Drupal 6 to 8 migration path is nearing beta stability. Some gaps remain, such as for some internationalization data. The Drupal 7 to Drupal 8 migration is incomplete but is suitable for developers who would like to help improve the migration and can be used to test upgrades especially for simple Drupal 7 sites. Most high-priority migrations are available.

Moderation and workflows

The Workflows module is now also stable, however it only provides a framework for managing workflows and is not directly useful in itself. The experimental Content Moderation module allows workflows to be applied to content and is now at beta stability. Content moderation workflows can now apply to any entity types that support revisions, and numerous usability issues and critical bugs are resolved in this release.

Platform features for web services

Drupal 8.4 continues to expand Drupal's support for web services that benefit decoupled sites and applications, including a 15% performance improvement for authenticated REST requests, expanded REST functionality, and developer-facing improvements.

Further details are available about each area in the 8.4.0 release notes.

What does this mean for me? Drupal 8 site owners

Update to 8.4.0 to continue receiving bug and security fixes. The next bugfix release (8.4.1) is scheduled for November 1, 2017.

Updating your site from 8.3.7 to 8.4.0 with update.php is exactly the same as updating from 8.3.6 to 8.3.7. If you use Drush, be sure to update to Drush 8.1.12 or higher before using it to update Drupal 8.3.7 to 8.4.0. Drupal 8.4.0 also has major updates to several dependencies, including Symfony, jQuery, and jQuery UI. Modules, themes, and translations may need updates for these and other changes in this minor release, so test the update carefully before updating your production site.

Drupal 7 site owners

Drupal 7 is still fully supported and will continue to receive bug and security fixes throughout all minor releases of Drupal 8.

Most high-priority migrations from Drupal 7 to 8 are now available, but the migration path is still not complete, especially for multilingual sites, so you may encounter errors or missing migrations when you try to migrate. That said, since your Drupal 7 site can remain up and running while you test migrating into a new Drupal 8 site, you can help us stabilize the Drupal 7 to Drupal 8 migration path! Testing and bug reports from your real-world Drupal 7 sites will help us stabilize this functionality sooner for everyone. (Search the known issues.)

Drupal 6 site owners

Drupal 6 is not supported anymore. Create a Drupal 8 site and try migrating your data into it as soon as possible. Your Drupal 6 site can still remain up and running while you test migrating your Drupal 6 data into your new Drupal 8 site. Core now provides migrations for most Drupal 6 data, but the migrations of multilingual functionality in particular are not complete. If you find a new bug not covered by the known issues with the experimental Migrate module suite, your detailed bug report with steps to reproduce is a big help!

Translation, module, and theme contributors

Minor releases like Drupal 8.4.0 include backwards-compatible API additions for developers as well as new features. Read the 8.4.0 release notes for more details on the improvements for developers in this release.

Since minor releases are backwards-compatible, modules, themes, and translations that supported Drupal 8.3.x and earlier will be compatible with 8.4.x as well. However, the new version does include some changes to strings, user interfaces, and internal APIs (as well as more significant changes to experimental modules). This means that some small updates may be required for your translations, modules, and themes. See the announcement of the 8.4.0 release candidate for more background information.