All RPGs and Storygames by Tod Foley are now available at DrivethruRPG. Bring these games to your table!
This module is a lightweight alternative to surveys such as Foresee to collect data from users visiting your site.
Drupal added the html5shiv asset library to core as a polyfill for older browsers that were not compatible with HTML5 elements.
All of the browsers listed in Drupal's browser support policy are HTML5 compatible so this asset library is deprecated in Drupal 8.8 and will be removed in Drupal 9.
This module provides a replacement asset library for sites that still need to support older browsers.
Drupal Association blog: Drupal Core Beta Testing Program call for the upcoming Drupal 8.8.0 release
As announced in December 2018, the Drupal Association assists the Drupal project by coordinating a beta testing program for minor releases of Drupal core.
Agencies and other organizations who are supporting ambitious Drupal 8 sites are invited to be part of the beta testing program. This means that, when a beta release is about to be made, we can help core maintainers work with organizations on the Beta Testing Program to install the beta core release on real-world examples of Drupal websites, in their staging environments. The beta testers can then feedback to the core maintainers any issues they see running the beta core release in a structured way.
Being part of the Beta Testing Program is a key contribution to the Drupal project and also helps organizations to be very aware of any changes relevant to their supported websites.
Would your organization, and the Drupal project, benefit from participating in the Beta Testing Program? You can apply to join:
Agencies and site owners who maintain large and complex Drupal 8 production sites. In particular, sites that use a wide range of contributed and custom modules or have large volumes of content.
For several years, Google has leveraged Drupal as the primary tool for developer portals built for its popular Apigee Edge API platform. With the introduction of the production-ready Drupal 8 distribution in May 2019, an announcement was made that support for the D7 platform would expire in 12 months. Concurrent with that announcement we know that D7 end-of-life will occur in November of 2021. This means that many Apigee portals will need to make the move to Drupal 8 or Apigee’s integrated portals in the near future.
In this article, we will walk through the steps to migrate Apigee portals from Drupal 7 to 8. The first decision you will need to make is whether to upgrade your existing custom build or move to the new Drupal 8 kickstart distribution. To help guide this decision, let’s first take a look at what the Apigee distribution for Drupal 8 has to offer and why you would want to leverage this platform.
Apigee Developer Portal Kickstart (D8)
The Apigee documentation site has excellent instructions on how to set up a developer portal using their Drupal 8 distribution. We will take a quick look at the features that come with the newest install profile.
Apigee Kickstart Homepage screenshot
The Apigee distribution once again has a nice out-of-box experience. This time around the base theme leverages a Bootstrap base theme that makes it easy to brand and customize your site.
The content types you see will be familiar: Article, Basic page, FAQ, Forums, and a new Landing page content type. Video, images, and audio are now more appropriately Media types in Drupal 8. The SmartDocs content type is gone in favor of a new API Doc type that supports the OpenAPI format (see below).
API doc screenshot
Adding content is now more flexible in Drupal 8 with the implementation of Paragraph types. Paragraphs allow you to add different components onto the page in any order you like. See the homepage example below.
Apigee Paragraphs screenshot from Homepage
In Drupal 8, Apigee also added some new block types. Blocks are still useful for components that need to live on more than one page.
Apigee block types screenshot
The great thing about Apigee’s distribution is that it also includes sample content which makes getting set up a breeze.
For organizations setting up a portal for the first time, leveraging this distribution is the way to go. For portals being upgraded from Drupal 7, this is more of a judgment call. If your portal has been heavily customized it might be better to move forward with a traditional Drupal 8 upgrade which we will cover under Custom Migrations. If, however, your organization’s portal previously had taken advantage of out-of-box functionality, then it makes sense to migrate content to Apigee’s D8 project which we will walk through next.
The maintainers of the Apigee kickstart distribution have supplied a module to make migrations as painless as possible. The apigee_kickstart_migrate sub-module provides the Migrate module configuration that maps Drupal 7 content to their newer Drupal 8 counterparts. Again, this is most helpful for portals that did not heavily customize content in Drupal 7. Included in this sub-module are instructions on how to run the migrations and how to extend migrations with custom fields.
The following table shows how content is mapped from the Drupal 7 portal to Drupal 8.
Drupal 7 (Devportal)
Drupal 8 (Kickstart)
Basic page (page)
Basic page (page)
Forum topic (forum)
Forum topic (forum)
When would you go with a custom Drupal 8 upgrade over leveraging the Kickstart project?
Where you run into trouble with distributions in Drupal is when you lean on so many customizations that the distribution gets in the way more than it saves time. In those instances, it’s better to stick with your own custom implementation.
The Mediacurrent team recently released the Migrate Pack module to make things easier for developers. This module has been tested against several sites and distributions including the Apigee Drupal 7 install profile.
The approach here would be to install Migrate Pack and the two additional Apigee modules in lieu of leveraging the distribution. The two key Apigee features you will need are the Apigee API Catalog and Apigee Edge modules. All of these projects should be installed using Composer.
If your theme was built custom in Drupal 7, then it will need to be manually ported to Drupal 8’s Twig-based theme engine. The other option is to instead borrow the Bootstrap-based theme included with Apigee’s distribution. It should be said that if the latter approach is taken, it might be better to migrate everything to the new Kickstarter rather than cherry picking the theme.Next Steps
Apigee has very good support and documentation to get you started on moving to Drupal 8. For issues and bugs specific to the Drupal distribution, the Github project issue queue is the best place to look. The Migrate Pack module also has its own issue queue on Drupal.org should you run into problems.
Mediacurrent has logged over 100,000 hours in Drupal 8 development, many of which are Drupal 7 to 8 upgrades. We would love to work with you on your next project.
A note from our fabulous DrupalCon Minneapolis program committee:
With a December 4, 2019 deadline we are one-third of the way through the DrupalCon Minneapolis 2020 session submission period. The program committee is thrilled with what we’ve seen so far, with many compelling sessions to review—from accessibility to Xdebug. If you aren’t one of the early submitters, however, we still need your voice! And we are here to support you.
Grids module will allow you enable/integrate any grid to your Drupal theme.
The works is in progress...
Sorry, but it's not for production use yet.
Maria Espie Vidal, writer for Timedoctor.com, wrote a post for our blog in which she breaks down the role of an IT project manager. Check it out and gain a better understanding of the multifaceted job of IT project management.READ MORE
There has been a lot of thoughtful debate about the Drupal project's contribution credit algorithm in recent weeks, and some great ideas have been proposed. In the meantime, however, we've also been monitoring concerns about gaming of the current algorithm. Making changes to the contribution credit algorithm must be done with care, because it has a significant impact on how we recognize contributions and also on the ecosystem of Drupal service providers. Today the Drupal Association engineering team deployed a quick tune-up to the contribution credit algorithm.
This change strengthens the existing multiplier which weighs issue credits based on the usage of the project. Issues on more highly used projects will now be weighted even higher, and those on lower usage projects will be weighted lower.
We're calling this a tune-up with good reason. This is not a fundamental update of the credit system; this is a small change to help resolve some recent issues with the current version of the algorithm.
Developing a true 'Contribution Credit 2.0' system is a much larger project, but one we're hoping to undertake soon.
In the meantime:
- If you have feedback on the small change we made today, you can find the issue here.
- If you'd like to propose new ideas about the next generation of the system, please do so in this issue.
As the community thinks about the contribution credit system, we encourage you to remember that there will always be a human element to recognizing contribution - and our goal should be a system that enables better interaction between project contributors.
Autumn is here! One of the things we’re looking forward to this month is DrupalCon Amsterdam from the 28th - 31st Oct 2019. Autumn is the most magical time to visit Amsterdam! An opportunity to mingle with the Drupal community in Amsterdam, what else could a Drupaler wish for?
QED42’s support for the Drupal Community around the world is unwavering. Would it be sponsoring DrupalCamps, DrupalCons, organizing Drupal meetups, or contributing to Drupal.org.
And we hope you will join us at DrupalCon Amsterdam, this month!| Meet us!
QED42 is proud to be a Silver sponsor this year. If you are a Drupaler you wouldn’t miss visiting QED42’s booth. We are known for our exuberant booth vibes, designs, activities, and goodies. It is our tradition of unveiling a new Drupal t-shirt design at every DrupalCon. Check out the story behind our Hindi Drupal t-shirt series here - https://www.qed42.com/blog/story-behind-our-hindi-drupal-t-shirt. Our Drupal t-shirt design for #DCA is inspired by the vibrant and spirited culture of Amsterdam. Accompanied by a couple more goodies that you will absolutely adore!
This year, QED42 will be showcasing a wide range of our capabilities including:
- Decoupled Drupal
- Gatsby e-commerce demos
Come say Hi to our team at DrupalCon Amsterdam Booth No - 16, we would love to discuss ideas around how Drupal meets the ever-changing needs of the digital world.| Sessions
Our Drupal experts are presenting at DrupalCon Amsterdam 2019. You can find us at these sessions:Houdini - New Era of CSS
- Date: 28th Oct 2019
- Time: 15:00 - 15:40
- Location: G 103
- Track: Drupal + Frontend
- Level: Intermediate
- Speakers: Vidit Anjaria and Saket Kumar
Here’s a sneak peek of our session - https://www.qed42.com/blog/building-powerful-custom-properties-CSS-houdiniDesigning the future of the Drupal Admin UI
- Date: 30 Oct 2019
- Time: 09:00 - 09:40
- Location: G 103
- Track: Drupal + Frontend
- Level: Beginner
- Speakers: Archita Arora, Sacha Eggenberger, and Cristina Chumillas
There are some exciting keynotes lined up for you at DrupalCon Amsterdam!- Tuesday, October 29 at 9:00 AM | Talk: Driesnote
Speaker: Dries Buytaert - Founder- Wednesday, October 30 at 1:30 PM | Talk: If I can do it, so can you
Speaker: Sue Black - Professor of Computer Science and Technology Evangelist, UK Government Strategic Advisor, Women’s Equality Party candidate for London Mayor 2020, Professional Speaker, Author- Tuesday, October 29 at 1:30 PM | Talk: Humanity in tech
Speaker: Boris Veldhuijzen Van Zanten - CEO and Co-founder of thenextweb.com- Monday, October 28 at 1:30 PM | Talk: Drupal core initiative leads keynote
Attending DrupalCon Amsterdam? Don’t forget to1 flash your badge and spread the word - https://events.drupal.org/amsterdam2019/spread-word. Follow @DrupalConEur for recent updates around the event.
Drop by our Booth 16 and meet the QED42 team! We would love to share our exciting projects and learn more about your experiences and challenges with Drupal.Ruchika.Mohite Wed, 10/09/2019 - 16:58
If you want to cache the output of a render array differently depending on if the site is visited by a known crawler or not, this is the module you need.Use cases
Say you want Google to index all pages of a search result, even if you want the average user to get an infinite scroll. You can then want to display a "next page" link to google only. Or maybe to crawlers only:
Drupal is a wonderful Content Management System with tons of features that solve many problems for editors and content managers. A developer can take different approaches to achieve the same result, and the Drupal update process is no exception.
It is possible to update Drupal either with Composer, Drush, or manually within the CPanel interface. The first two methods imply that you have at least mid-level experience with the command line and secure shell access to your public host. The third method is more visual and is suitable for developers beginning with Drupal.
Keep reading, if you want to learn how to update your Drupal site with this method.