UI Suite Material is a site builder friendly Material Design 2 theme for Drupal, using the UI Suite Initiative.

UI Suite Material allows site builders to use Material Design 2 directly from Drupal backoffice (layout builder, manage display, views, blocks...) in a low-code way.

Work in progress. Not production ready yet.

UI Suite Material is a site builder friendly Material Design 2 theme for Drupal, using the UI Suite Initiative.

UI Suite Material allows site builders to use Material Design 2 directly from Drupal backoffice (layout builder, manage display, views, blocks...) in a low-code way.

Work in progress. Not production ready yet.

The question we want to answer in this blog post is whether Drupal is still the leading CMS platform in 2022 and beyond. If you have been thinking of trying out Drupal, this article will help you decide whether it is still worth it in 2022. Let’s jump right in!

The question we want to answer in this blog post is whether Drupal is still the leading CMS platform in 2022 and beyond. If you have been thinking of trying out Drupal, this article will help you decide whether it is still worth it in 2022. Let’s jump right in!

The question we want to answer in this blog post is whether Drupal is still the leading CMS platform in 2022 and beyond. If you have been thinking of trying out Drupal, this article will help you decide whether it is still worth it in 2022. Let’s jump right in!

UI Suite Protocol is a Site Builder friendly Mozilla Protocol theme for Drupal, using the UI Suite Initiative.

UI Suite Protocol allows site builders to use Mozilla Protocol directly from Drupal backoffice (layout builder, manage display, views, blocks...) in a low-code way.

Social shares can significantly increase your brand exposure, expand your reach, boost your website traffic, and benefit your SEO. Of course, all this works much better if your shared content looks attractive, relevant, and well-formatted on social media.  Content preview snippets are built automatically when someone shares a link on Facebook, Twitter, LinkedIn, and so on. They include a title, a description, an image, or other details. Can you control how they look and make them so irresistibly clickable? Yes, sure, you can do this by setting up social media meta tags on your website. 

Social shares can significantly increase your brand exposure, expand your reach, boost your website traffic, and benefit your SEO. Of course, all this works much better if your shared content looks attractive, relevant, and well-formatted on social media.  Content preview snippets are built automatically when someone shares a link on Facebook, Twitter, LinkedIn, and so on. They include a title, a description, an image, or other details. Can you control how they look and make them so irresistibly clickable? Yes, sure, you can do this by setting up social media meta tags on your website. 

Have you ever spent a lot of time on something for your project, only to throw it away? Often someone else interacts with your work and uncovers something important. Perhaps the issue came from a stakeholder, real users, or the implementation team, and their input is important. But now, you have to go back to the drawing board. We can relate.

Have you ever spent a lot of time on something for your project, only to throw it away? Often someone else interacts with your work and uncovers something important. Perhaps the issue came from a stakeholder, real users, or the implementation team, and their input is important. But now, you have to go back to the drawing board. We can relate.

Have you ever spent a lot of time on something for your project, only to throw it away? Often someone else interacts with your work and uncovers something important. Perhaps the issue came from a stakeholder, real users, or the implementation team, and their input is important. But now, you have to go back to the drawing board. We can relate.

In this article we are going to see how your Drupal team can do code reviews and available tools or libraries which help people in the team to do the code reviews seamlessly. It’s pretty important to follow a few guidelines as well, so that all people or developers in the team are on the same page. Firstly, for the code reviews to be at their best, the committed code should be more organis

In this article we are going to see how your Drupal team can do code reviews and available tools or libraries which help people in the team to do the code reviews seamlessly. It’s pretty important to follow a few guidelines as well, so that all people or developers in the team are on the same page. Firstly, for the code reviews to be at their best, the committed code should be more organis

ECA rules engine for Drupal: RC1 released Jürgen Haas Wed, 06/22/2022 - 17:25

A huge milestone for the ECA team has finally being reached: it is available for everyone to give it a try. ECA and its main modeller BPMN.iO are considered stable and ready for testing and almost production ready. This is a big achievement after 11 months and around 3.000 hours of architecting, developing and testing the new rules engine for Drupal 9 and 10.

We gave a talk at Drupalcon Portland 2022 about the Unified Government Website project we have been working on, as well as the migration of the Japanese Digital Agency website to a Headless CMS (Drupal + Next.js) as a feasibility study.

The talk consisted of three parts:

1. Migration of the Digital Agency website to a headless CMS
2. Research project for the realisation of a unified government website
3. The future direction of the project

This blog post describes the first part above.

We gave a talk at Drupalcon Portland 2022 about the Unified Government Website project we have been working on, as well as the migration of the Japanese Digital Agency website to a Headless CMS (Drupal + Next.js) as a feasibility study.

The talk consisted of three parts:

1. Migration of the Digital Agency website to a headless CMS
2. Research project for the realisation of a unified government website
3. The future direction of the project

This blog post describes the first part above.

We gave a talk at Drupalcon Portland 2022 about the Unified Government Website project we have been working on, as well as the migration of the Japanese Digital Agency website to a Headless CMS (Drupal + Next.js) as a feasibility study.

The talk consisted of three parts:

1. Migration of the Digital Agency website to a headless CMS
2. Research project for the realisation of a unified government website
3. The future direction of the project

This blog post describes the first part above.

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 for the Drupal community.

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

• George DeMet
• Nikki Flores
• Julian Taylor
• Donna Bungard
• Mike Anello

The main goal for this meeting was to get status updates from all tasks discussed at the previous meeting in an effort to better understand the Code of Conduct landscape in other communities. In addition, some updates were provided related to identifying other community stakeholders in the overall process of updating our Code of Conduct.

The following Codes of Conduct were reviewed by individual team members and discussed during the meeting:

• A11yTalks
• Gitlab
• Uplift Together
• Contributor Covenant
• Enspiral

Much of the discussion was related to how each Code of Conduct provided examples of negative and/or positive behaviors and the pros and cons of each approach. The level of prescription for infractions was also a common thread in the discussion, including how some CoCs provide very clear and precise guidance while others (like the current Drupal Code of Conduct) provide a great deal of leeway to those responsible for enforcement.

We also discussed the fact that many CoCs are not stand-alone documents, but rely on supporting documents, much like the Drupal Values and Principles.

Finally, 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, please let us know at drupal-cwg at drupal dot org.

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 for the Drupal community.

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

• George DeMet
• Nikki Flores
• Julian Taylor
• Donna Bungard
• Mike Anello

The main goal for this meeting was to get status updates from all tasks discussed at the previous meeting in an effort to better understand the Code of Conduct landscape in other communities. In addition, some updates were provided related to identifying other community stakeholders in the overall process of updating our Code of Conduct.

The following Codes of Conduct were reviewed by individual team members and discussed during the meeting:

• A11yTalks
• Gitlab
• Uplift Together
• Contributor Covenant
• Enspiral

Much of the discussion was related to how each Code of Conduct provided examples of negative and/or positive behaviors and the pros and cons of each approach. The level of prescription for infractions was also a common thread in the discussion, including how some CoCs provide very clear and precise guidance while others (like the current Drupal Code of Conduct) provide a great deal of leeway to those responsible for enforcement.

We also discussed the fact that many CoCs are not stand-alone documents, but rely on supporting documents, much like the Drupal Values and Principles.

Finally, 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, please let us know at drupal-cwg at drupal dot org.

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 for the Drupal community.

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

• George DeMet
• Nikki Flores
• Julian Taylor
• Donna Bungard
• Mike Anello

The main goal for this meeting was to get status updates from all tasks discussed at the previous meeting in an effort to better understand the Code of Conduct landscape in other communities. In addition, some updates were provided related to identifying other community stakeholders in the overall process of updating our Code of Conduct.

The following Codes of Conduct were reviewed by individual team members and discussed during the meeting:

• A11yTalks
• Gitlab
• Uplift Together
• Contributor Covenant
• Enspiral

Much of the discussion was related to how each Code of Conduct provided examples of negative and/or positive behaviors and the pros and cons of each approach. The level of prescription for infractions was also a common thread in the discussion, including how some CoCs provide very clear and precise guidance while others (like the current Drupal Code of Conduct) provide a great deal of leeway to those responsible for enforcement.

We also discussed the fact that many CoCs are not stand-alone documents, but rely on supporting documents, much like the Drupal Values and Principles.

Finally, 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, please let us know at drupal-cwg at drupal dot org.