Drupal Planet

xjm: Fund xjm as a Drupal core release manager

3 months 2 weeks ago
Fund xjm as a Drupal core release manager Hi, I'm xjm. I'm a Drupal core committer, one of eighteen people who are trusted to accept (merge) code changes to the Drupal project for the hundreds of thousands of sites that rely on it.

My role on the committer team is that of a release manager. We're the folks who actually create the Drupal core releases that you can install on your site.

xjm Sun, 12/11/2022 - 12:44

DinoTechno.com: Top 4 New Features of Drupal 10

3 months 2 weeks ago
Drupal 10 is expected to be released on 14 December, 2022 which is a very good news for all webmasters using this great CMS on their website. Drupal 10 expected to be one of the best releases ever with a lot of features to make managing websites easier and more powerful. Although Drupal 10 has […]

Salsa Digital Drupal-Related Articles: CivicTheme is now available with GovCMS

3 months 2 weeks ago
CivicTheme for GovCMS It was great to participate in the GovCMS Mega Meetup last week, especially presenting and introducing CivicTheme — an open source, inclusive and component-based design system to the GovCMS community. More about CivicTheme Even more exciting was the announcement that CivicTheme is part of the official GovCMS roadmap. But what does this mean? CivicTheme is built and optimised for GovCMS SaaS out-of-the-box (OOTB) website projects. So if your website is hosted on GovCMS SaaS (or PaaS) you can use Civic OOTB immediately to build and manage your website, or you can adapt it to suit your GovCMS web project.

Evolving Web: Picture Perfect: Selecting and Preparing Images for the Web

3 months 2 weeks ago

Images are a crucial consideration when you’re updating or expanding your website. Done right, they're a powerful tool for communicating your message and enriching the user experience. Done wrong, they can leave a bad impression and weaken your digital presence. 

This guide explains how to pick meaningful images that create a connection with your audience. You’ll also learn how to optimize, resize, and compress images so they’re ready for the web. 

Selecting the Right Images

Take time to explore the images available to you. You can search and download free images via Unsplash and Pexels



Here are some key points to consider:

  • Quality. Choose images with a high resolution and correct exposure to show users you care about quality. Avoid images that are low-res, blurry, tilted, or incorrectly exposed.
  • Tone. Images should match how your organization wants to come across. If there are people in the image, think about the impression their poses and clothing give – for example, do they seem professional, friendly, or casual?
  • Inclusivity. Pictures are a great way to connect with your audience. Portraying different people can help make them feel welcome. Be inclusive of all races, genders, ethnicities, abilities, sexual orientations, and other characteristics. Pay particular attention to traditionally underrepresented groups. 
  • Variety. Show a variety of environments to keep things interesting for users. Have some images that feature people and some that don’t. Switch things up with different crops and angles.
  • Composition. Images with simple compositions and no clutter tend to be less distracting and overwhelming. This allows users to focus on what’s really important.
  • Distinctiveness. Look for images that make your platform stand out from the crowd. Avoid generic stock photos as they’re boring and leave a poor impression on users. 
  • Design specifications. For example, banner images can be tricky to pick due to their unusual dimensions. Avoid close-ups of people as their heads may get chopped off on mobile. Ensure any text over the banner is legible. 
Examples of Well-Chosen Images

The Princeton International website encourages students to explore international learning opportunities. Its visual design is inspired by travel websites to create a sense of adventure. It includes a variety of eye-catching photos that showcase the exciting destinations and diverse cultures students can experience. 



The Canada Foundation for Innovation website features banner images that reflect the key themes of each page. A variety of colours, environments, and angles creates visual interest, while simple compositions ensure they don’t get distracted. The white text is positioned over darker and cleaner parts of the image so that it’s easy to read.



The OCAD U Admissions website features student-created art in a variety of striking styles. It’s a bold visual direction that supports the university’s reputation for excellence in art, design, and digital media.




Making Touch-Ups

Once you’ve chosen your images, use a photo editing app to fine-tune them. There are a variety of correction tools in Photoshop under Adjustments. Or you could try a free app such as Pixlr or GIMP





Adjust the following settings if necessary to enhance your photo and match it to the style of other images on your site: 

  • Exposure to change the overall brightness of the image.
  • Brightness to change mainly the brightness of midtones. 
  • Contrast to control the difference between shadows and highlights.
  • Saturation to control how colourful your image is. 
Image Source - phlearn.com


Use the crop and rotation tools to fix bad angles and reduce visual clutter. You’ll also need to crop images to the aspect ratio specified by your platform’s design. Aspect ratio is the ratio of width to height. For example, an aspect ratio of 1:1 is a perfect square. If you had a 2500px by 3500px image, you’d need to crop the top or bottom of the image by 1000px for a 1:1 aspect ratio.

Saving Images at Retina Dimensions

Retina dimensions are a nice way to create a higher-resolution image. It means saving an image at double the required dimensions. 

Here’s an example. Let’s say that we are designing a picture for a banner whose actual dimensions are 2400 x 1600px. We would save it as 4800 x 3200px to create a retina image. 

The image won’t appear bigger than usual if you’re using web components. Drupal will automatically fit the image into the given physical space. By squeezing twice the number of pixels into the same space, it creates a higher pixel density and therefore a better quality image. 

A retina image may appear bigger if you’re creating a WYSIWYG page. You can either force the image dimensions in the front-end or upload the image at its normal (non-retina) dimensions. 

Compressing Images for Faster Load Times

It’s important to balance image quality with image compression. Compressing your images reduces their file size so that loading them is faster and takes less data. This makes your platform more accessible, especially to users with slow-speed internet connections and those who are using mobile data while they’re on the move. 

Images should typically be no larger than 300-500KB. Smaller is usually better, especially for smaller-scale images. If many of your images exceed this, users will experience a slow and laggy web performance.

You can run an action in Photoshop to automatically batch and save multiple images in one clean sweep. Export your images at a quality between 80-85%. Finally, compress the images with a free tool like TinyPNG or Compressor before uploading them to your platform.



Image Defining Focal Points in Drupal

Drupal automatically scales your images for desktop, mobile, and tablet. This means you don’t have to upload different versions of the same image. 

Some images will scale at the same aspect ratio meaning the image will look the same except smaller or bigger. Other images (e.g. mobile banners) may be cropped to fit various devices meaning parts of the image may not always be visible. 

You can control how images scale on different devices by selecting a focal point on the image in Drupal. Preview the image on desktop, mobile, and tablet to ensure it looks good before publishing.

Need more guidance?

This article is a great starting point for adding visual interest to your site and ensuring your images look as good as possible. 

Want to take your knowledge to the next level? Sign up for training in UX design or content strategy. 

//--> //--> //--> //--> //-->

+ more awesome articles by Evolving Web

Peoples Blog: Drupal 10 is coming in a few days!

3 months 2 weeks ago
Drupal 10 is planned to be released in December 2022. Drupal 10 will be straightforward upgrades like Drupal 8 to 9. Upgrade processes used are more or less similar. Mostly you need to keep your current site up to date with the latest drupal core and contributed projects. What is new in Drupal 10? Drupal 10 is a refined version of Drupal 9 with the certain features Claro administration theme i

Lullabot: Drupal 10: Everything You Need to Know

3 months 3 weeks ago

Drupal 10 will be released on December 14, 2022, with new features and new possibilities. Here's what you need to know.

Making Drupal beautiful with Claro and OIivero

Drupal 10 will have two new default themes, and we are proud to say that we helped push these initiatives forward so that they would be ready and stable for this release.

Salsa Digital Drupal-Related Articles: Celebrate the launch of Drupal 10 with Salsa

3 months 3 weeks ago
Drupal 10 Melbourne Meetup launch Join us for the Drupal 10 Melbourne launch at 4.30pm on 15 December 2022.  To celebrate the next evolution of Drupal 10 we’re hosting a D10 launch party to coincide with its global release.  As part of our regular commitment to Drupal and the Melbourne Drupal Meetup, Salsa has moved the Meetup to host the Drupal 10 launch celebration. We’ll be providing a special venue (Hub Australia Church Street) for this event, with drinks and food — you just need to bring yourself!  We’ll also be highlighting and presenting Salsa’s contribution to Drupal 10 with the Drupal 10-ready CivicTheme design system.

Opensource.com: 16 reasons DDEV will be your new favorite development environment

3 months 3 weeks ago
16 reasons DDEV will be your new favorite development environment Randy Fay Wed, 12/07/2022 - 03:00

What's so different about DDEV? It's a container-based local development environment. Here are a few reasons you should give it a try.

In 2022, you have a wide variety of local development environments to choose from, whether you're a designer, developer, tester, or any kind of open source contributor…

PreviousNext: 5 simple tips to increase your Drupal contributions without gaming the system

3 months 3 weeks ago

How and why we contribute influences our impact on the Drupal community and ecosystem. So, how can we become positive, long-term contributors?

by lee.rowlands / 7 December 2022

Ok, so joke link-bait titles aside, this is actually a pretty serious topic. There was a Talking Drupal podcast episode about it and a lot of chatter on Twitter that was nicely summarised in this Drop Times article

As someone with a long history of contributing to Drupal, I want to wade in on the topic in a constructive fashion to try and help achieve the best outcome for the project and contributors. So, here's some advice from a long-time contributor. Feel free to take it with a grain of salt.

Tip 1 - Work out why you want to contributeSource: https://drupalsouth.org/news/2022/drupalsouth-2022-videos-and-photos

Both individuals and companies need to determine their reasons for contributing. If your reason is to increase your contribution credits and improve your position in the marketplace, then stop. You're doing yourself and your employees a disservice and likely creating additional work for others.

For organisations

If you're an organisation, your motivations should be something like this:

  • To improve your reputation in the Community
  • To ensure Drupal's long-term livelihood
  • To align Drupal with you and your client's strategic goals - Drupal is a do-ocracy
  • To improve your staff members' reputations in the Community
  • To grow your staff skillsets with mentoring from the brightest Drupal minds in the world
  • To enhance your reputation as an employer of choice for members of the Community

Co-founder of PreviousNext, Kim Pepper, gave an excellent presentation on the benefits to an organisation that encourages contribution. His talk might be four years old; however, it's still relevant. 

PreviousNext has always encouraged contribution, making us an attractive employer for developers. Our average staff tenure is more than five years, which is unheard of in the tech industry. Additionally, it helps when you're pitching for new projects if you have RFQ line items asking you to demonstrate you understand a feature and someone in your team is a maintainer or significant contributor to that feature.

For individuals

If you're an individual, your motivations should be something like:

  • To improve your skillset or learn a new concept. You will be amazed by how encouraging and helpful our community is for people who are helping move issues forward. If you come to an issue without an ego and with a willingness to ask for assistance, you are more likely to leave with a new concept/skill under your belt.
  • To increase your reputation in the community. People follow Drupal.org issues and get emails of activity. They may not have time to participate in every issue they follow, but they keep abreast of what is happening and who is driving the issue forward. Your username is your individual brand. If folks see a name popping up time and again, it builds recognition of your individual brand.
  • To widen your professional network. This gives you the ability to approach community members to ask for help. If you've worked on an issue with someone who maintains a key module and you have trouble with that module, that individual is more likely to be receptive to a request for help. The shared experience of working together to improve Drupal builds that relationship. Karma is something you can spend as well as earn.
  • To make friends all over the world. One of the true joys of contribution is the ability to work with amazing people all over the world. You will hear many tales of lifelong friendships people have formed with people on the other side of the world through contribution
  • To improve your resume and employment options. This one is kind of obvious, but if your personal brand value is on the ascent, this obviously makes you a recruitment or promotion target, or perhaps it gives you some justification for a pay rise. And employers shouldn't fear this. You want your people to be their best because when their value rises, so does yours.
  • To have fun. Because if it's fun, everything else is easy.

Whether you're an individual or an employer, it helps to define your contribution goal. Use it to guide your contributions and view each contribution through the lens of your goal. If it doesn't bring you closer to your goal, is it worthwhile? Is there some other way you could contribute?

Tip 2 - Treat contribution as a long-term investmentSource: https://commons.wikimedia.org/wiki/File:Gfp-wisconsin-madison-sunset-over-the-train-tracks-by-the-lake.jpg

Some forms of contribution are like a sugar hit. Sure, you get a credit, but do you get anything else out of it? Does it bring you closer to your goal? Some examples here include:

  • Rerolling an issue that doesn't apply. Then not sticking around to help address remaining tasks, like getting tests passing.
  • Fixing coding standards violations and nothing else.
  • Adding a README to a project.
  • Fixing the capitalisation of a module name in an info file.
  • Attaching screenshots to an issue that already has them.

Now don't get me wrong. I'm not saying that all of these aren't valuable contributions. Some of them are valuable contributions and move the project forward. The reroll might breathe life into a stale issue, the coding standards violation fix might result in the issue passing tests for the first time, and a new README improves our documentation. 

These are useful contributions for a new contributor getting used to the mechanics of creating patches or merge requests. However, once you have mastered that skill are you advancing your contribution goals from above if you continue to do it? Are you learning anything new? Are you robbing other newcomers of an opportunity to get started contributing? 

So if you're beginning, these type of tasks could easily be what helps you achieve your first contribution goal–but set a limit, acknowledge that you've achieved that goal, and then set a new goal and leave this to other newcomers.

Core committer, security team member and release manager Jess (xjm) (side note, she's looking for work, you should consider hiring or sponsoring her to continue her work on core) once wrote

Even if I ... never visited Drupal.org again, and threw my laptop in Lake Monona, I would continue to get commit mentions for work I did in the past.

And she is 100% right. For the last 11 months, I've been busy on a major client project, but I've continued to receive commit mentions for investments I made in issues in the past. Contribution is a long-term investment, and so you need to wait for that investment to mature. Things can happen slowly at times. 

Drupal is a huge and complex project run mostly by volunteer effort. It has a reputation for stability, which sometimes means things take a bit longer in order to consider all the possible side-effects, which leads me into my next tip.

Tip 3 - Get into a regular habitSource: https://flic.kr/p/D2n1Nq

The best way to improve your contribution 'investment' yield is to get into a regular habit. Set yourself a target for regular contribution. But to be 100% clear, the target should be for 'acts of contributing' rather than 'contribution credits'.

Back when Drupal 8 was nearing release, I started the patch a day challenge. Little did I know it would be a further two years until Drupal 8 came out. But I kept up the challenge and uploaded at least one patch a day on average for those two years. When Drupal 8 came out, I wound up close to the top ten contributors. To further illustrate xjm's point above, some of these investments continue to result in commit mentions even now, nearly seven years later.

Now, I realise this isn't something everyone can do. At the time, I was working part-time and caring for two school-aged children, so I had some spare time every afternoon as well as an employer willing to give me sponsored contribution time of around 6 hours a week. The luxury of time is something only some have. But getting yourself into a regular habit lets you build up an investment that will mature with time. 

Former colleague Donna Benjamin (@kattekrab) once said something along the lines of, "A website is like a garden, not a house, you need to continually tend to it" (sorry if I'm paraphrasing incorrectly, Donna). Contribution is similar; a little bit each day or week, and your investment will bear fruit.

Tip 4 - Find your nicheSource: https://flic.kr/p/y89qMj

The Drupal mentoring team's website slogan was once 'We've got issues'. It's a fun play on the number of tasks in the Drupal issues queues that's still true today. There are over 60,000 open issues for Drupal core alone (9 and 10 only). And the number of open issues for contrib would easily be just as many. So, there are plenty of opportunities for contribution.

My advice would be to find your niche. You could:

  • Find something you care about.
  • Find something no-one cares about.
  • Find something to fix/change that would make your day job easier.

For me (@larowlan), my introduction to core development was to find something no-one cared about: the forum module.

For my colleague Mohit Aghera (@mohit_aghera) it was the Needs tests tag (2500 issues in core alone). Through this effort, Mohit gained a deep understanding of writing tests for Drupal core, a highly valued skill–so much so that we asked him to come and work for us.

For Stephen Mustgrave (@smustgrave), it is the Needs review queue status (2700 issues in core alone). By reviewing other people's work, Stephen achieves his contribution goal of learning the inner workings of Drupal and gives back to something he uses every day. Reviewing is an under-appreciated contribution task that allows you to learn from and teach other developers by reviewing and suggesting changes to their code, all whilst steadily increasing the areas of core you understand. Stephen is now a maintainer of the Block Content module in core and (at the time of writing) proposed as maintainer for both the Telephone and Text modules. In addition, he has built relationships with several core contributors who know him by name and recognise his value to the community.

Tip 5 - Contribute in ways that help the ecosystemSource: https://flic.kr/p/2kBZB1V

The health of Drupal relies on contributions from the community. If contributions don't benefit the long-term health of the ecosystem, does Drupal continue to be relevant and innovative? Contributions that actively move the project forward are more likely to have a greater velocity.

Think of helpful contributions like:

  • Contributing to the readiness of the next major release - (Drupal 10 readiness at the time of writing) issues in this space get a lot of focus as we're working towards a given release date with set objectives. These issues move faster. They're also where innovation occurs, which keeps your skills up to date. Helping port contrib modules to the next major version also applies here, as you keep up-to-date with new changes, help the ecosystem and get faster results.
  • Joining an initiative - groups working towards a common goal generate a much faster turnaround on issues. There's nothing worse than working on an issue and uploading a patch only to see it sit in 'needs review' for a long time. Working in a team will increase your network in the project (see goals above) but is also more likely to lead to a faster outcome. If you need help determining where or how to contribute, folks in these teams will definitely be able to point you towards places to help. There are strategic initiatives and community initiatives to choose from.
Tip 6 - Bonus tip for organisations Source: https://flic.kr/p/8pheyT

Suppose you're an organisation looking to increase your contribution but are unsure how to start. In that case, one approach could be to sponsor an existing experienced contributor to establish, grow or maintain your team's capabilities. As mentioned above, Core committer, security team member and release manager Jess (@xjm) is looking for work, as is Core Javascript Maintainer Théodore Biadala (@nod_).

Here at PreviousNext we sponsor V Spagnolo (@quietone) to work on Drupal core. When announcing this sponsorship, we described it as a new and exciting way for PreviousNext to give back to the project as well as the community

In this scenario, @quietone works solely on Drupal contribution, but there are other models where organisations can bring in an experienced Drupal contributor for a mix of contribution and client work. For example, Kristen Pol (@Kristen Pol) is employed by another Australian agency to work on client projects and to help turbo-charge company Drupal contribution efforts. With her existing network of contacts and experience contributing to Drupal, Kristen can help her colleagues navigate the issue queues and contribute. With Kristen on the team, they get the dual benefit of Kristen applying her expertise on client projects and her contribution experience to help their team maximise the impact of their contributions.

Thoughts and comments?

What do you think? Let me know in the comments, or feel free to reach out to me on the shiny new Drupal Community Mastodon Instance. And of course, if you want to get more involved with contributing to Drupal, say hi in the Drupal community slack on any of the many general or specialist channels we have dedicated to co-ordinating contribution such as #contribute, #d10readiness or #bugsmash.

Tagged Contribution
2 hours 29 minutes ago
Drupal.org - aggregated feeds in category Planet Drupal
Subscribe to Drupal Planet feed