Drupal Planet

As previously reported, the Community Health Team has started to have regular, bi-weekly meetings in an effort to develop and update the Code of Conduct (CoC) for the Drupal community.

Community Health Team members present at this week's meeting were

• George DeMet
• Julian Taylor
• Jordana Fung
• Mark Casias
• Mike Anello

During the meeting, we created milestones leading up to our December 14 goal of having a revised Code of Conduct ready for adoption. This time frame allows us ten 2-week sprints. We settled on a timeline based on one, 2-week public review period and two, 2-week community stakeholder review periods. We created a Trello board with initial tasks for each sprint.

George DeMet will be responsible for managing and prioritizing our backlog of tasks. Donna Bungard will facilitate our meetings and hold us accountable and ensure all team members have tasks for each sprint.

Our main task for the current sprint is to populate a new Miro board with elements of our current Code of Conduct and other Codes of Conduct that we'd like to include in our community's next Code of Conduct. Jordana Fung will schedule daily Slack reminders to the team to add things to the board.

At our next meeting on August 10, we will discuss and decide which elements will be part of an initial outline to be shared with community stakeholders for feedback. This outline will include what, if anything, we are proposing to keep or discard from our current Code of Conduct as well as any elements that we are considering adopting from other Codes of Conduct.

In previous outreaches to the community related to our current Code of Conduct, the most common request has been that our Code of Conduct be more specific and actionable; this will be an important guiding principle for the team.

If you know of any Code of Conducts from other communities that you feel have elements we should emulate, please let us know at drupal-cwg at drupal dot org or via Twitter @drupalcommunity

A number of Drupal-related groups and individuals have confirmed their willingness to provide feedback to this effort as the process proceeds. If you, or a Drupal-related group, is interested in being part of this process as a community stakeholder, please let us know at drupal-cwg at drupal dot org.

Ten years ago, to be a successful brand, you had to have a website and be present on the Internet. In 2022, this is not enough. Developing the best digital experience is the primary weapon for today.

Your Drupal development company is back in business! Here is a new guide where you can find answers to the following questions:

The Taxonomy Manager module provides a different user interface for the management of taxonomy terms, particularly in batch operation. Terms can be added or deleted in bulk, instead of one by one. In addition, it provides features to export all taxonomy terms and search. This terms-export feature is beneficial for transferring the terms in bulk from one site to another.

In this tutorial, you’ll learn how to install and use the Taxonomy Manager module.

Throughout all the change and innovation of the past 20 years, there has been (seemingly) little change in the formats we use to share images online. 

But changes are already here! Let’s take a quick look at the image formats we all use now, and learn about new formats we could be using instead.

Welcome to the first Drupal 10 Global Porting Day, organised by the Drupal Association! This 30-hour event will take place in all time zones across the world. The Global Porting Day is the first of its kind, where everyone involved will be focused on porting Drupal 9 projects. Join us in this rare opportunity; make history whilst we help to ensure that the release of Drupal 10 goes ahead smoothly. 

Read on to learn how we approach challenging migration relics.

Since we started Drupal Career Online over a decade ago, our 12-week best-practice focused course has grown and evolved; not only in the area of curriculum, but also in the resources we provide around it in an effort to create a truly holistic learning experience for students. Until now, we’ve referred to these aspects of our program loosely as our "learning community." 

The thing is, it’s grown into quite an extraordinary, multi-facetted body of people and programs that continues to develop beyond our early plans and goals. With the extensive breadth and reach these elements have grown to include, it’s time for an official name, and to impart the anatomy of the DrupalEasy Learning Community.  

First and foremost we need to recognize the heart of the DrupalEasy Learning community, which beats strong thanks to the students, alumni, mentors, instructors, contributors, scholarship sponsors and supporters who have helped our learning-minded cooperative thrive over the past 11 years. We are fortunate to have the trust, loyalty and friendship of the active alumni; from our first class held in-person at our riverfront classroom on Florida’s Space Coast in 2011, to the multiple scholarship sponsors from across North America who are now leveraging our programs to diversify their teams and the wider Drupal Community.
 
Of course, Drupal Career Online was always meant to be more than just an instructor-taught course. Drupal is more than just code, so the DCO, and in fact all of our courses, have been developed to integrate the community aspect into not just what we teach, but how we teach it. The DCO is 84 hours of curriculum combined with resources and amazing people who make it a truly complete, educational experience centered in a diverse community of people who continually seek getting better at all things Drupal.  

DrupalEasy is committed to:

• Teach comprehensive Drupal knowledge & best-practice skills
• Teach and integrate community engagement in everything that we do
• Provide comprehensive resources for lifelong learning

We accomplish this through ongoing supplemental elements that serve to enrich our courses, support our participants and help to build a sense of community. 

The DrupalEasy Learning Community has developed to include eight supporting features that augment course curriculum and that are designed to create a holistic learning experience and engage students to excel in the Drupal ecosystem:

Office hours, sometimes referred to as lab hours, have been a staple of our learning community since we started our long-form Drupal program, and key to making and maintaining connections and friendships around learning Drupal. Current students and all alumni are welcome to join our weekly office hours to work through issues, ask and answer questions and learn from others. It’s a great way for students to stay connected in an informal, but very useful way.

Another original feature of Drupal Career Online that makes a huge difference to many students are the amazing members of the Drupal community who generously donate their time to provide mentorship to current Drupal Career Online students. Many of these mentor/mentee relationships remain ongoing after the student completes the course. 

A more recent development of the DrupalEasy Learning Community is the scholarship program supported by web development agencies, the Drupal Association, and other organizations that underwrite tuition for qualified students who also have the opportunity to join the providing organization as an intern or junior developer after graduation. 

Just like Drupal, our curriculum is always evolving. As such, students and alumni have access to curriculum updates for the course they graduated from, which includes our class slides, lesson guides, and videos. We frequently hear from alumni who revisit lessons long after they graduate in an effort to keep their skills fresh and up to date.

Attending a Drupal event for the first time can be a bit scary and overwhelming, so we’ve set up a way to make things a bit less daunting for those who would like some guidance. Alumni who would like some support simply fill out a form, and we introduce them to someone (a well seasoned Drupal event guru) who is attending the same event and is willing to show them the ropes. The goal is to have the guru provide suggestions, introductions, and a friendly face for the alumni. We've been doing this informally for a few years now, and just recently set it up as a formal program. 

Starting with the very first class of Drupal Career Online we strive to welcome our students as new members of the Drupal community. As class progresses, we are almost continuously introducing them to more and more members of the Drupal community, including their community mentor and our alumni (via shared office hours and our dedicated Slack workspace.) By helping students grow their Drupal networks, we also help them get more comfortable, and make it easier to grow their Drupal skills. For some of our students and alumni, the Drupal community Slack workspace can be intimidating and overwhelming - our goal is to help folks join the wider Drupal community at their own pace, starting with the DrupalEasy Alumni Network.

Drupal Career Online’s alumni community is special to us, and so, we have created the DrupalEasy Community Grants program with them in mind. Any alumni family, friends and co-workers are eligible for DrupalEasy Legacy Grants to help them experience our career technical education program (the DCO) and our continuing education programs including long-form courses and workshops (those where we control enrollment.) Alunni Grants for other DrupalEasy training (again, where we control enrollment) are also available.  We've had more than a few individuals who have taken Drupal Career Online in both its previous Drupal 7 version and again in the Drupal 8/9 version - the latter with significant grants to help their ability to take the course. In addition, we always try to show the love to our alumni themselves who steer friends and co-workers to our long-form program, with what we hope are thoughtful recognition. We also provide Group and Team Grants for those who seek to take our courses and join our DrupalEasy Learning Community in numbers. 

For any graduates who are looking for employment, we try to provide introductions and pass along opportunities for positions as we become aware of them. We continually receive requests from a variety of organizations who are looking to hire Drupal Career Online graduates. This usually comes in the form of introductions to DrupalEasy partners who have job openings, one-on-one guidance, and resume reviews.

It is extremely gratifying that we can provide all of these programs to our long-form Drupal training students and alumni, and that the DrupalEasy Learning Community has grown into the hundreds. Over the past 11 years, we've seen the results of efforts in the form of successful Drupal professionals working all over the world. While we're formalizing the eight programs that support our learning environment, we'll continue to experiment with additional elements (like early access to upcoming courses) in our never-ending effort to help build the Drupal Community by nurturing the DrupalEasy Learning Community.

If you are interested in learning more about Drupal Career Online and experiencing the DrupalEasy Learning Community, join us next Wednesday for a Taste of Drupal (add TOD link) information webinar. 

In early 2010, Jason Grigsby pointed out that simply setting a percentage width on images was not enough, and that you needed to resize these images for a better user experience (src). According to him, you can save over 75% of the weight of those images if you serve the right-sized images on a smaller screen. Ever since, the debate on responsive images has evolved into finding the best solution to render perfect, responsive images without any hassle.

Drupal 9 does a fabulous job of offering out-of-the-box solutions for responsive images (since Drupal 8). Read more about how responsive images work in Drupal 9 and learn to implement it using a simple step-by-step process.

When you’re confused, leave it to the browser. And that’s exactly what Drupal 9 helps you do with the help of the Breakpoints module and the Responsive images module.

But first, what are breakpoints? To be able to provide the most optimal image size for a device, you need to define different screen sizes in CSS, called breakpoints. Of course, you cannot possibly have all of them covered but you should specify some rough and reasonable sizes that could cover most devices.

The Breakpoint module is in Drupal 9 core and has some preconfigured height and width of different viewports available with the built-in themes, you can add your own breakpoints in your custom themes’ breakpoints yml file as well.
 
Drupal 9's Responsive image module uses a picture tag to render a flawless responsive image based on the breakpoint of the original image. The Picture module that was previously in Drupal 7 is now the new Responsive Images module in Drupal 9.

One of the major problems with images in web development is that browsers know nothing about the images and are clueless about what sized images are rendering in relation to a viewport of different screens until the CSS and Javascripts are loaded.

However, the browser can know about the environment in which the images are rendered, which includes the size of the viewport and the resolution of the screen.

As previously mentioned, responsive images use the picture element which basically has sizes and srcset attributes that play a major role in notifying the browser to choose the best images based on the image style selections.

Drupal 9 has done a great job in providing the responsive images module in core. This will help the browser download lower-sized images for devices with lower screen resolution, resulting in better website load time and improved performance.

1. Enable Responsive images and breakpoint module.
2. Set up the breakpoints for your projects theme.
3. Set up image styles for responsive images
4. Creating a responsive image style for your theme
5. Assign the responsive image style to an image field.

Since both modules are part of Drupal 9 core, you will not need to install them or add any other module. All you have to do is enable the Responsive images module since the breakpoint module will be installed with the standard profile. If not, enable the breakpoint module.

To enable the modules, go to Admin->Extends, select the modules and enable them.

Setting up the theme’s breakpoints is the most important part of building a responsive website in Drupal 9.

If you are using a core theme like Bartik, Seven, Umami, or Claro, you will already have the breakpoints file and you don’t have to create a new one.
 
However, if you are using a custom theme for your project, it is important that you define the breakpoints in the "yourthemename.breakpoints.yml" file, which can be found in your theme’s directory, usually found in "/themes/custom/yourthemename".

Each breakpoint will assign the images to a media query. For example, images that are rendered on mobiles might be smaller, that is with a width less than 768px, whereas medium screens will have a width between 768 px to 1024 px.

Each breakpoint will have: 

• label:  Is the valid label given for the breakpoint.
• mediaQuery: The viewport within which the images are rendered.
• weight:  For the order of display.
• multipliers: A measure of the viewport's device resolution. Normally, 1x will be used for standard sizes and 2x for retina display.

Now let’s create an image style for each of the breakpoints. You can configure your own  image styles at Admin -> Config -> Media -> Image-styles. 

Click on ‘Add image style’.  Give a valid name for your image style & use the Scale and crop effect which will provide cropped images. If the images are stretched, add multiple image styles for different viewports.

This is where you provide multiple image style options to the browser and let the browser choose the best out of the lot.

To create a new responsive Drupal 9 image style, navigate to:

Home -> Admin -> Config-> Media-> Responsive-image-style and click on ‘Add responsive image’. 

Give a valid name for your responsive image style and then select the breakpoint group (choose your theme). Next, assign the image styles to the breakpoints listed. 

There are multiple options for the image style configurations.

• Choose single image style: Where you can select a single image style that will be rendered on the particular screen
• Choose multiple image style: Where you can select multiple-image style and also specify the viewport width for the image style

In the end, there is an option to select a fallback image style. The fallback image style should only appear on the site if an error occurs.

Once all the configurations are done, move to the image field by adding the responsive image style. To do that go to the field’s Manage display section and select the responsive image style that we created previously.

Now add content and check the results on the page with a responsive image style.

 Image at a minimum width of 1024px (For Large Devices).

Image at minimum width of 768px (For Medium Devices).

Image at maximum width 767px (For Small Devices).

Image optimization has been a major challenge for websites that want to be more responsive. You either have to let go of the image quality or increase the page load time. But with the Drupal 9 Responsive Images module and the Breakpoints module (now in core!), you can now scale or crop images at any breakpoint for different resolutions.
Are you looking for a proven Drupal development company to build impressive responsive Drupal websites? We’d love to help! Talk to us today.

Author: Akshay Devadiga

​​Meet Akshay Devadiga, a Drupal developer by profession. During his spare time, he loves to travel and always tries to include adventure sports in his itinerary. When he’s not traveling or working, he’s usually found preparing happiness in the form of good food :)

Leave us a Comment

Today we are talking about GraphQL with Alexander Varwijk.

www.talkingDrupal.com/357

• What is GraphQL
• Common use cases
• Why GraphQL over JSON:Api
• How is it being used?
• How to use it with Drupal
• Is there a standard?
• How do you customize it?
• What resources do you recommend?

• Book module listener Amit
• Building a GraphQL API - Beyond the basics
• GraphQL API examples
  • Shopify
  • GitHub
• The GraphQL specification repository on GitHub
• The Drupal GraphQL module
• The GraphQL PHP library
• GraphQL in the Open Social Drupal distribution
• Serving GraphQL Subscriptions Using PHP and Drupal
• The GraphQL documentation website
• Production Ready GraphQL - Marc-Andre Giroux
• GraphQL specification for servers and clients
  • http://spec.graphql.org/
  • https://github.com/graphql/graphql-spec/
• GraphQL OAuth
• The GraphQL Compose module
• UrQL
• Relay
• ReScript
• Caching & GraphQL: Setting the Story Straight

Alexander Varwijk - www.alexandervarwijk.com/ @kingdutch

Nic Laflin - www.nLighteneddevelopment.com @nicxvan John Picozzi - www.epam.com @johnpicozzi Ryan Price - ryanpricemedia.com - @liberatr

Earlier this year Drupal developer Jacob Rockowitz introduced the Schema.org Blueprints module (schemadotorg) to the Drupal community. Having spent a lot of time thinking about Schema.org and content models recently, this module immediately peaked my interested. For background, Schema.org “is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured […]

The post Drupal Schema.org Blueprints Module appeared first on Daggerhart Lab.

While at DrupalCon Portland this past April, several agency leaders gathered together to talk about the future of Drupal. One topic discussed, and something Dries highlights annually in his blog, is how organizations support Drupal. Organizations of all sizes are making use of Open Source software at increasing rates (enjoying the benefits of higher quality, greater reliability, more flexibility, and lower costs) but sustaining Open Source continues to be challenging. 

Open Source software is built on the foundation of a community working together to scale and sustain it. The Drupal community, in particular, deeply relies on collaboration. The community is made up of thousands of contributors who are constantly innovating to build a superior Open Source Content Management System (CMS). 

In the Drupal community, there’s an amazing camaraderie that comes from contributing, but there are so many more benefits for organizations who give back to Open Source. During the discussion at DrupalCon, a few of the benefits we discussed included:

• Higher quality software - Awareness leads to greater stability. When you’re an organization who uses specific Open Source software, it’s important to make sure it continues to run flawlessly in the future.
• Recruiting - Top Open Source & Drupal talent want to work in a contrib-centric culture. Companies that create a culture of giving back will attract this talent. 
• Free training for employees - People tend to learn best by hands-on experience. By contributing, staff are exposed to new concepts, new approaches, new techniques for completing tasks, and so much more.
• Innovation - As a contributor to Open Source, you have the opportunity to steer the ship and influence the direction the software takes. You also have the ability to prototype and do faster release cycles.
• Brand equity/marketing - Companies want to do business with other companies who give back. By taking a contrib-first approach, you’ll attract and win more opportunities. 
• Corporate social responsibility - Using Open Source instead of proprietary alternatives often saves a business a significant amount of money. Many consider it a social responsibility to give back and support Open Source when they benefit from it.

Now onto the important part — how you can help. Whether you are an organization that uses Open Source platforms as part of your service or use Open Source solutions in your technology stack, there are several ways you can contribute. Here are a few ways you can start making contributing a priority for your organization:

• Get leadership buy-in - Find an internal champion or small group of people who can champion giving back.
• Align on the mission - Pair profit with purpose. Organizations that see the benefits and believe in the sharing and collaboration aspect of Open Source succeed best.
• Provide staff dedicated time (during business hours) - Often, the reason for not giving back is lack of time. It can be helpful if an organization dedicates time (ideally on a weekly basis) for team members to contribute. 
• Recognize contributions - Recognize employees, especially first-time contributors.
• Create a contribution-first culture - While working on projects, think about what portions are custom and what could possibly be reused. For anything that can be reused, train your team on how to contribute these improvements. 
• Work with organizations who are active contributors - By working with other companies who contribute, you are supporting the growth of Open Source. Pfizer and The State of Georgia are great examples of organizations who have prioritized working with companies who contribute to Drupal.
• Encourage all team members to contribute - There is a place for both technical and non-technical team members to give back. Marketers can assist with event planning and overall strategy, designers can create mockups for Open Source site improvement or logos for specific features, and technical writers and trainers can improve documentation. 

Some of you may have heard Dries talk about makers versus takers in his writing or talks on Open Source. Simply put, makers invest in giving back to Open Source software while takers use Open Source without contributing back. 

Let’s say your organization is saving $100,000 by using Open Source over a proprietary solution. A maker might contribute back $50,000 through hiring staff members to contribute or giving financially to the Open Source organization. A taker might only give $5,000, putting themselves at a competitive advantage by benefiting from Open Source without investing. The Open Source community needs organizations with a maker mindset to continue innovating and improving Open Source solutions.

If you’re a part of the Drupal community, you can likely rattle off a handful of agencies and individuals who have been strong contributors for many years. Mediacurrent has always been a strong believer in giving back to Open Source and we take an Open Source approach in everything we do. Although it’s great to see the continued support of these organizations and individuals, we still need to diversify and grow this list of contributors to assure the future of Drupal.

The Drupal Association is making great strides in improving the contribution process, which will help, but as a community we need to continue to encourage participation from all Open Source users. The future of Drupal depends on it. 

You’ll always run into roadblocks when considering making the leap to creating a contrib-first culture, but the benefits far outweigh these challenges. Start asking yourself what your company can do to contribute. Maybe you start small and work towards dedicating more time and resources in the coming months. It takes a community to step up to make Drupal and other Open Source software scalable and sustainable.

Acquia recently turned 15. Over the past 15 years, I've heard the name "Acquia" pronounced in all sorts of different ways.

It was Jay Batson, my co-founder, who came up with the name "Acquia".

When it came time to pick a name for our company, Jay insisted that the name started with the letter A. I remember questioning the value of that. In a world where people search for things, who looks up things in alphabetical order?, I asked.

In the end, Jay was right. I learned a great many things the past 15 years, including how common alphabetical listings still are. You'd be amazed how often Acquia ranks number one in listings. It gave us a small edge.

For more background on how the name Acquia came to be, and some other Acquia trivia, check out Jay's blog post "ah-kwe-eh".

In web development we often find ourselves writing custom WordPress plugins, Drupal modules, or themes that have external package dependencies. It’s standard to use Composer for Drupal and WordPress package management. So often we find projects that require their custom code dependency in the root composer.json file of the project. Though quick, that solution is […]

The post Composer Managed Custom WordPress & Drupal Dependencies appeared first on Daggerhart Lab.

The Media oEmbed iframe route does not properly validate the iframe domain setting, which allows embeds to be displayed in the context of the primary domain. Under certain circumstances, this could lead to cross-site scripting, leaked cookies, or other vulnerabilities.

This advisory is not covered by Drupal Steward.

Install the latest version:

• If you are using Drupal 9.4, update to Drupal 9.4.3.
• If you are using Drupal 9.3, update to Drupal 9.3.19.

All versions of Drupal 9 prior to 9.3.x are end-of-life and do not receive security coverage. Note that Drupal 8 has reached its end of life.

Drupal 7 core does not include the Media module and therefore is not affected.

• Heine of the Drupal Security Team

• Lee Rowlands of the Drupal Security Team
• Alex Pott of the Drupal Security Team
• Samuel Mortenson
• xjm of the Drupal Security Team
• Heine of the Drupal Security Team
• Joseph Zhao, provisional member of the Drupal Security Team
• Vijay Mani, provisional member of the Drupal Security Team
• Alex Bronstein of the Drupal Security Team
• Neil Drumm of the Drupal Security Team
• Benji Fisher, provisional member of the Drupal Security Team
• Jen Lampton, provisional member of the Drupal Security Team
• Dave Long, provisional member of the Drupal Security Team