Drupal (core)

As per my last update on the board resolution related to the at large director elections, on the community committee, we’ve decided to create a Drupal.org project to open discussion with the community in subjects and areas that require it. You can ... [More] find more details on the task-force attributions on this Drupal.org issue, and we’re hoping to recruit a diverse group of volunteers to drive the conversation and come up with a recommendation. Everyone is welcomed to join the discussion at any point. If you’re interested, please do self-nominate by commenting on the issue! Note: This blog has the comments disabled, please feel free to send me a message through my contact page if you need to discuss anything related to the community and the Drupal Association. You can also tweet at me or find me in Drupal Slack or the distributed matrix network as pcambra. #Drupal [Less]

Date:  2022-February-23 Description:  Drupal 7's End-of-Life extended to November 1, 2023 More than a decade after its first release, Drupal 7 is still widely used across the web. It can be found powering civic engagement in government ... [More] installations; managing vast amounts of content for faculty, students, and staff in educational institutions; and providing the digital backbone for many businesses and non-profit organizations. Drupal 9 is well-maintained, secure, stable, and feature-rich, but many organizations still rely on Drupal 7. The teams that built and still maintain these legacy Drupal installations, and the end users they serve, are important constituents of the Drupal community. Although these users should still plan their upgrade to a newer version of Drupal, if they are unable to upgrade before the currently announced end-of-life, it would not be responsible of us to leave them vulnerable. Therefore, we are announcing that moving forward, the scheduled Drupal 7 End-of-Life date will be re-evaluated annually. As of today, we are extending the end-of-life by one year to November 1, 2023. The Drupal project lead, Dries Buytaert, the Drupal Association, and the Drupal Security Working Group have been monitoring the Drupal 7 ecosystem since the previous end-of-life extension. As a majority of all sites in the Drupal project are still on Drupal 7, we have decided that there is a clear need to provide additional support to the members of our community still using this version. At the end of the day, we have a moral imperative to keep as many of those sites secure as we can. We will announce by July 2023 whether we will extend Drupal 7 community support an additional year. Factors that we will consider are community support, Drupal 7 usage, and active Drupal 7 maintainers. Current support is made possible thanks to the many Drupal 7 maintainers and companies that are paying to support Drupal 7. You can donate to the Drupal Security Team on our Donations page. For press contacts, please email [email protected]. Coordinated By:  The following people contributed to this public service announcement. Michael Hess Tim Lehnen Greg Knaddison Dries Buytaert xjm Gábor Hojtsy Madison Atkins [Less]

Date:  2022-February-23 Description:  Drupal 7's End-of-Life extended to November 1, 2023 More than a decade after its first release, Drupal 7 is still widely used across the web. It can be found powering civic engagement in government ... [More] installations; managing vast amounts of content for faculty, students, and staff in educational institutions; and providing the digital backbone for many businesses and non-profit organizations. Drupal 9 is well-maintained, secure, stable, and feature-rich, but many organizations still rely on Drupal 7. The teams that built and still maintain these legacy Drupal installations, and the end users they serve, are important constituents of the Drupal community. Although these users should still plan their upgrade to a newer version of Drupal, if they are unable to upgrade before the currently announced end-of-life, it would not be responsible of us to leave them vulnerable. Therefore, we are announcing that moving forward, the scheduled Drupal 7 End-of-Life date will be re-evaluated annually. As of today, we are extending the end-of-life by one year to November 1, 2023. The Drupal project lead, Dries Buytaert, the Drupal Association, and the Drupal Security Working Group have been monitoring the Drupal 7 ecosystem since the previous end-of-life extension. As a majority of all sites in the Drupal project are still on Drupal 7, we have decided that there is a clear need to provide additional support to the members of our community still using this version. At the end of the day, we have a moral imperative to keep as many of those sites secure as we can. We will announce by July 2023 whether we will extend Drupal 7 community support an additional year. Factors that we will consider are community support, Drupal 7 usage, and active Drupal 7 maintainers. Current support is made possible thanks to the many Drupal 7 maintainers and companies that are paying to support Drupal 7. You can donate to the Drupal Security Team on our Donations page. For press contacts, please email [email protected]. Coordinated By:  The following people contributed to this public service announcement. Michael Hess Tim Lehnen Greg Knaddison Dries Buytaert xjm Gábor Hojtsy Madison Atkins [Less]

Customize the administrative experience to make it easier for content editor users to manage content, user accounts, and content blocks.

Drupal 10 release windows Our release schedule includes three potential release dates for Drupal 10.0.0, depending on when critical requirements are completed: June 15, 2022, if key requirements are completed by March 11 August 17, 2022, if key ... [More] requirements are completed by May 13 December 14, 2022, if key requirements are completed by September 9 Our new target release date for Drupal 10.0.0 is August 17, 2022 With about two weeks remaining until the March deadline, we are confident that the critical requirements will not be completed by that date. Therefore, we are officially announcing that our new target release date for Drupal 10.0.0 is August 17, 2022, and the beta deadline for critical requirements is May 13, 2022. We need your help to complete requirements by May 13! The community has already done an amazing job preparing for Drupal 10. Many key Drupal 10 release requirements are complete! That said, there is still a lot more to do! Even with three months remaining until the May deadline for Drupal 10's beta requirements, we need your help to make an August release possible. There are also numerous pending improvements that are not hard requirements for Drupal 10's release, but that are still critically important to its long-term support and maintainability. See the list below for the most urgent needs. Stabilize CKEditor 5 and deprecate CKEditor 4 Issue: #3238333: Roadmap to CKEditor 5 stable in Drupal 9 The most significant change in Drupal 10 is probably the upgraded WYSIWYG editor. Drupal 8 and 9 core both integrated with CKEditor 4, which will be end-of-life at the end of 2023. We must upgrade to CKEditor 5 for Drupal 10 to receive security coverage beyond 2023. Numerous contributors have been collaborating with CKSource for more than a year to create a new beta-stability experimental module integrating CKEditor 5 with Drupal 9. There is still a significant amount of work remaining to make it stable. After the module is stable, CKEditor 4 will also need to be decoupled from other core modules, deprecated, and moved back to contrib. Much of the work needed to stabilize the CKEditor 5 module requires knowledge of JavaScript. If you can, help us solve the outstanding issues on the roadmap to a stable CKEditor 5. Join the #ckeditor5 channel in the Drupal community Slack to coordinate with other contributors. Learn more about CKEditor 5. Update Drupal core's JavaScript dependencies to the latest major versions Issue: #3238507: Drupal 10 JavaScript dependency plan The Drupal core Frontend Framework Managers and JavaScript Package committers have defined a plan for all of Drupal core's JavaScript dependencies for Drupal 10. We could especially use help with this plan, starting with the following: First, we need to address several known security vulnerabilities in the development dependencies. The meta issue for this is #3258933: [meta] Update JavaScript dependencies for Drupal 10 to address security issues. Then, our development dependencies should all be updated to the latest major versions in Drupal 9.4.x and 10.0.x. (See #3246148: Update JavaScript dev dependencies to lates major releases before 9.4.0.) Our production JavaScript dependencies also need to be updated to the latest minor and patch versions in Drupal 9.4.x and 10.0.x. (Since Drupal 9.3.0, Drupal core has a simplified process for updating our production JavaScript dependencies!) Finally, individual issues for major upgrades of our production JavaScript dependencies should be filed on a case-by-case basis when a newer major version is available. Add any new issues filed for these tasks to the meta issue for the JavaScript dependency plan. Thanks! Make Olivero the default frontend theme of the Standard profile, and deprecate Bartik Issue: #3219958: [META] Make Olivero the default theme for Drupal 10 The new Olivero frontend theme for Drupal core has had great community momentum, and is already available as a stable theme in Drupal 9.3. The next step is to make it the default theme of the Standard profile. This will make Drupal look like the modern platform it is and will improve the evaluator experience. It will also allow us to deprecate Bartik and move it into contrib, which will improve core's maintainability. Make Claro the default administration theme of the Standard profile, and deprecate Seven Issue: #3066007: Roadmap to stabilize Claro Claro is a beautiful, accessible, modern administration theme that greatly improves Drupal's administrative user experience. It's been available as a beta experimental theme in core for several years now, and it is already used on many sites. Only a few critical bugs remain to make it stable. Once Claro is marked stable, additional work is needed to make it the default administration theme of the Standard profile, which will give Drupal 10 a fresh new look. Finally, once Claro is in the Standard profile, Seven can be deprecated and removed from core for better core maintainability. We could use your help on all these issues! Test and stabilize the experimental Theme Starterkit so that legacy base themes can be removed from core Issue: #3050378: Replace Classy with a starterkit theme The new experimental Theme Starterkit is a tool for generating new themes. It will allow us to provide an experience that more closely matches theme developer workflows, because we will be able to introduce incremental improvements to the theme. Once Starterkit is stable, we can remove both Classy and the Drupal 8 version of the Stable base theme from core. Additionally, if we fix #3050386: Allow loading CSS and JavaScript directly from templates, core can do away with the stable base themes entirely. This will allow us to simplify core process for markup bug fixes and deliver more markup improvements in minor releases, improving the core theming experience for core maintainers, contributors, and site owners alike. Learn more about Starterkit. I'm no good with JavaScript or CSS. Can I still help with the Drupal 10 release? Yes, absolutely! The categories above need help the most urgently, but there are many other critical issues of all sorts that need to be completed before the May deadline. Join the #d10readiness channel in the Drupal community Slack for help finding Drupal 10 issues that fit your skillset. [Less]

Drupal 10 release windows Our release schedule includes three potential release dates for Drupal 10.0.0, depending on when critical requirements are completed: June 15, 2022, if key requirements are completed by March 11 August 17, 2022, if key ... [More] requirements are completed by May 13 December 14, 2022, if key requirements are completed by September 9 Our new target release date for Drupal 10.0.0 is August 17, 2022 With about two weeks remaining until the March deadline, we are confident that the critical requirements will not be completed by that date. Therefore, we are officially announcing that our new target release date for Drupal 10.0.0 is August 17, 2022, and the beta deadline for critical requirements is May 13, 2022. We need your help to complete requirements by May 13! The community has already done an amazing job preparing for Drupal 10. Many key Drupal 10 release requirements are complete! That said, there is still a lot more to do! Even with three months remaining until the May deadline for Drupal 10's beta requirements, we need your help to make an August release possible. There are also numerous pending improvements that are not hard requirements for Drupal 10's release, but that are still critically important to its long-term support and maintainability. See the list below for the most urgent needs. Stabilize CKEditor 5 and deprecate CKEditor 4 Issue: #3238333: Roadmap to CKEditor 5 stable in Drupal 9 The most significant change in Drupal 10 is probably the upgraded WYSIWYG editor. Drupal 8 and 9 core both integrated with CKEditor 4, which will be end-of-life at the end of 2023. We must upgrade to CKEditor 5 for Drupal 10 to receive security coverage beyond 2023. Numerous contributors have been collaborating with CKSource for more than a year to create a new beta-stability experimental module integrating CKEditor 5 with Drupal 9. There is still a significant amount of work remaining to make it stable. After the module is stable, CKEditor 4 will also need to be decoupled from other core modules, deprecated, and moved back to contrib. Much of the work needed to stabilize the CKEditor 5 module requires knowledge of JavaScript. If you can, help us solve the outstanding issues on the roadmap to a stable CKEditor 5. Join the #ckeditor5 channel in the Drupal community Slack to coordinate with other contributors. Learn more about CKEditor 5. Update Drupal core's JavaScript dependencies to the latest major versions Issue: #3238507: Drupal 10 JavaScript dependency plan The Drupal core Frontend Framework Managers and JavaScript Package committers have defined a plan for all of Drupal core's JavaScript dependencies for Drupal 10. We could especially use help with this plan, starting with the following: First, we need to address several known security vulnerabilities in the development dependencies. The meta issue for this is #3258933: [meta] Update JavaScript dependencies for Drupal 10 to address security issues. Then, our development dependencies should all be updated to the latest major versions in Drupal 9.4.x and 10.0.x. (See #3246148: [meta] Update JavaScript dev dependencies to latest major releases before 9.4.0.) Our production JavaScript dependencies also need to be updated to the latest minor and patch versions in Drupal 9.4.x and 10.0.x. (Since Drupal 9.3.0, Drupal core has a simplified process for updating our production JavaScript dependencies!) Finally, individual issues for major upgrades of our production JavaScript dependencies should be filed on a case-by-case basis when a newer major version is available. Add any new issues filed for these tasks to the meta issue for the JavaScript dependency plan. Thanks! Make Olivero the default frontend theme of the Standard profile, and deprecate Bartik Issue: #3219958: [META] Make Olivero the default theme for Drupal 10 The new Olivero frontend theme for Drupal core has had great community momentum, and is already available as a stable theme in Drupal 9.3. The next step is to make it the default theme of the Standard profile. This will make Drupal look like the modern platform it is and will improve the evaluator experience. It will also allow us to deprecate Bartik and move it into contrib, which will improve core's maintainability. Make Claro the default administration theme of the Standard profile, and deprecate Seven Issue: #3066007: Roadmap to stabilize Claro Claro is a beautiful, accessible, modern administration theme that greatly improves Drupal's administrative user experience. It's been available as a beta experimental theme in core for several years now, and it is already used on many sites. Only a few critical bugs remain to make it stable. Once Claro is marked stable, additional work is needed to make it the default administration theme of the Standard profile, which will give Drupal 10 a fresh new look. Finally, once Claro is in the Standard profile, Seven can be deprecated and removed from core for better core maintainability. We could use your help on all these issues! Test and stabilize the experimental Theme Starterkit so that legacy base themes can be removed from core Issue: #3050378: Replace Classy with a starterkit theme The new experimental Theme Starterkit is a tool for generating new themes. It will allow us to provide an experience that more closely matches theme developer workflows, because we will be able to introduce incremental improvements to the theme. Once Starterkit is stable, we can remove both Classy and the Drupal 8 version of the Stable base theme from core. Additionally, if we fix #3050386: Allow loading CSS and JavaScript directly from templates, core can do away with the stable base themes entirely. This will allow us to simplify core process for markup bug fixes and deliver more markup improvements in minor releases, improving the core theming experience for core maintainers, contributors, and site owners alike. Learn more about Starterkit. I'm no good with JavaScript or CSS. Can I still help with the Drupal 10 release? Yes, absolutely! The categories above need help the most urgently, but there are many other critical issues of all sorts that need to be completed before the May deadline. Join the #d10readiness channel in the Drupal community Slack for help finding Drupal 10 issues that fit your skillset. [Less]

A fundamental aspect of Drupal development is ensuring images are displayed optimally – with a high enough resolution that the integrity of the image is not compromised, but not so large that load times are delayed. As Internet connection speeds ... [More] increase, developers and those who can quickly download a page, can easily overlook excessively large page weight. It is important, however, for developers to keep in mind that users with slower connections may be frustrated with images that are slow to load. [Less]

How to Find and Hire Drupal Developers: The Ultimate Guide Maitreayee Bora Tue, 02/22/2022 - 17:35 If you're looking to hire the best Drupal developer for your project, you've come to the right place. In this blog post, we will ... [More] discuss some tips on how to find and hire expert Drupal developers for your needs. We'll also provide a few resources that can help you get started. So, without further ado, let's get started! All you need to know before you hire Drupal developers What to look for before you hire a Drupal developer? 1. Experience with Drupal websites Drupal development is not just about coding. It's also about having a deep understanding of the Drupal platform and its ecosystem. That's why you should always look for Drupal programmers with a lot of experience working with Drupal websites. 2. Communication skills To be successful, your dedicated Drupal developers will need to be able to communicate clearly with you and your team. This is especially true if they are working remotely. It's important to find someone who can express their ideas in an easily understandable way, but also be able to listen carefully when others speak as well. Read about the importance of communication between developers and designers to know more.3. Attention to detail Drupal development requires a lot of attention to detail because there are so many things that go into building a Drupal website. If your Drupal programmer isn't paying attention to those details, they won't have the best experience working with you and your team. 4. Problem-solving skills Your Drupal developers should also be able to solve problems quickly and effectively so that everything runs smoothly throughout the project's life cycle. Be sure to ask them about any problems they have encountered in past custom Drupal solutions and how they dealt with those issues. 5. Able to work as a team player One of the biggest mistakes that businesses make when they plan to hire Drupal developers is only looking for people who can do what's asked of them. But it's also important to hire someone who will be able to work well with the rest of your team. This means that they need to be able to take feedback and criticism, as well as give it.   If you're looking for a Drupal developer, we recommend checking out these resources: The Acquia Developer Center - This is a great place to start if you want to learn more about Drupal. Signs you've got the wrong Drupal programmer for your project 1. Doesn't know how to use Git or doesn't want to Git is a version control system that makes it easy for teams of Drupal developers to work on the same project without getting in each other's way. If your Drupal developer isn't familiar with Git, they'll probably end up causing problems down the road when multiple people are working on one site at once (which happens often). 2. Doesn't communicate well with team members and clients alike If they're not communicating effectively, then there will be problems later on during development because nobody knows what's going wrong until it's too late. And if someone else finds out about them before you do- well that could mean disaster! This means making sure everyone has a clear understanding of the project, its goals, and what is expected from everyone involved. 3. Lacks attention to detail If your Drupal developer can't be bothered with details then you'll likely run into a lot of problems down the line. Details may seem minor, but they can add up very quickly and cause big delays in the development process. 4. Requests for changes or new features after work has started This is usually a sign that either your developer doesn't understand your project requirements or they're trying to take advantage of you. In either case, it's not a good situation and will only lead to frustration on all sides. If this happens, be sure to document everything very carefully so there are no misunderstandings. 5. Works well on their own, but doesn't integrate well with the team This can be a huge issue down the road because it means that they're not interested in collaborating with others which is essential for any successful Drupal project. If this is the case, you may want to reconsider your Drupal developer. 6. Is always late delivering work or missing deadlines If your dedicated Drupal developers can't seem to get their act together and meet deadlines, then it's going to be a very long and frustrating project for everyone involved. This is definitely something you don't want happening when working on a Drupal website.  7. Cannot solve problems effectively If your Drupal developers are not able to fix things quickly when they go wrong, then the project will be delayed and everyone will be stressed out. This is definitely not ideal.   If you're looking for a Drupal developer, we recommend checking out these resources: Drupal Jobs - A website that's dedicated solely to listing jobs in the Drupal industry. You can filter your search by location, skills, type of position, and more. Comparison between freelance Drupal Developer vs Drupal agency  While hiring a Drupal developer or team of the best Drupal developers for your next Drupal project, it can be difficult to decide which option is best for you. In this section, we'll compare and contrast the benefits of hiring a freelance Drupal developer versus an agency.    First, let's take a look at some advantages of working with a freelance developer: They're usually cheaper than an agency, which means lower hourly rates. Plus, there are no overhead costs like office space rental payments, etc., so they can work from almost anywhere with access to the internet. Freelancers also don't have employees that need salaries and benefits either - which means less money spent on each month for payroll expenses that help in keeping prices less as well.  While working on a project together as opposed to individually, developers can collaborate more easily because communication channels are already established between them. This saves time and ensures everyone is aligned about what needs to be done next for progress towards completion goals such as deadlines or milestones set by clients. Read about how to find the right Drupal 9 development partner to know more. When should you hire an expert Drupal developer, and how much does it cost?  That depends on a lot of factors, such as the size and complexity of your project, your budget, and your level of Drupal expertise. Generally speaking, though, it's a good idea to start looking for someone early on in the development process - ideally when you first begin planning out your website.   Hiring an individual developer usually costs more than hiring an agency, but the advantage is that you have more control over the project and can work closely with them to ensure everything goes according to plan. Agencies are great for larger projects or if you don't have much experience working with Drupal, and they often have pre-made teams of developers who are familiar with specific aspects of Drupal development (like module building or theme design). So how much does Drupal development cost in the end? That depends on all of the factors mentioned above, but you can expect to pay anywhere from $50/hour to $200/hour for high-level expertise. No matter who you choose to work with, be sure to get a detailed estimate upfront so there are no surprises later on.  Learn more: Infinity stones of Drupal development Essential skills to be an ideal Drupal developer Right skills for decoupled Drupal project   How to assess their skills and experience to identify the best Drupal developers? While assessing a Drupal developer's skills, it's important to look at their experience with the following: 1. Drupal Theming - This is how you change the appearance of your Drupal site by modifying its templates. A good themer will be able to create a design that matches your vision and also meets all of the requirements for accessibility and responsive design. 2. Coding Standards - For modules and themes to be compatible with each other (and future updates to Drupal core), they need to be coded using the same standards. A developer who is familiar with best practices in coding will ensure that your website is as stable and secure as possible. 3. Drupal Module Development - Modules are small pieces of code that can be added to a Drupal.  The importance of communication in the development process  We have written this article because we believe that communication is a key aspect of the development process. Communication makes it possible for us to understand each other, and when there are misunderstandings on either side they can be resolved quickly without delays and frustrations.   Communication between remote Drupal developers is important. Drupal has many features that allow you to communicate with other members of your team - whether they're located at an office or working remotely from home. You could use email, phone calls, or instant messaging services like Slack (which offers free plans). These platforms make it easy for everyone involved with a project including designers/developers, content writers/editors, clients, and project managers to stay in touch with each other.  Tips for setting expectations and managing the Drupal development budget 1. Be realistic about what you want your website to do. If you're on a tight budget, consider focusing on the most important features and excluding the less essential ones. 2. Make a list of all the tasks that need to be completed and assign a priority level to each one. This will help you better understand how much work needs to be done and how much time it will take. 3. Create a timeline for your project and share it with everyone involved. This helps ensure that everyone is working towards the same goals and prevents any confusion or delays. 4. Get a detailed estimate from your chosen developer(s) or agency before starting the project. This will help avoid any unpleasant surprises down the road. Assess the experience in Drupal module development 1. What is their experience in Drupal theming? 2. Do they understand and follow the coding standards for Drupal? 3. Can they demonstrate a good understanding of the Drupal core functionality? 4. How do they communicate with other team members, especially clients? 5. Are they able to work within a budget and meet deadlines? These are some of the questions you should be asking when assessing a developer's skills. By considering these factors, you'll be better equipped to find the right person or team for your project. How to hire top Drupal developers?  Define your Drupal project requirements and goals  Before starting to look for Drupal developers, you need to have a good idea of what you want your website to do. The best way to start is by creating a requirement document. This document will outline the features and functionality that your website needs. It's important to be as specific as possible when creating your requirement document. This will help ensure that you find a development partner who can deliver the website that you need. 1. What kind of content will your website have? Examples include blog posts, podcasts, videos, and contact information. You'll also want to decide what type of navigation structure your website should use. This includes main navigation categories and sub-categories for each category. 2. What features and functionality do you need? Will your website require a shopping cart, registration form, or blog comments? Be sure to list all of the features that are important to you. 3. Who will be responsible for creating the content? If you're not able to create the content yourself, you'll need to find someone who can. You'll need to determine who will be responsible for uploading the content, as well as creating new pages and posts regularly. 4. How often do you plan on updating your website? While it's not necessary to update your website every day, you should have an idea of how often you want to make changes or add new content. This will help you determine whether or not a developer can meet your needs in terms of updating the website regularly and making changes to existing pages as needed. 5. What is your budget? Before beginning any kind of development process, you should have an idea of how much money you're willing to spend on developing your website. This will help you narrow down your search for a development partner. 6. Creating a requirement document is an important step in the process of hiring Drupal developers. By taking the time to create this document, you'll be able to ensure that you find Drupal web developers who can deliver the website that you need. Do your research - Compile a list of qualified Drupal developers Once you have a clear idea of what you want your website to do, it's time to start looking for qualified Drupal developers. The best way to find qualified developers is by doing your research. This includes researching different development agencies and compiling a list of qualified Drupal developers. While researching development agencies, be sure to look for companies that have a lot of experience in Drupal development. You'll also want to make sure that they're familiar with the latest version of Drupal (currently Drupal v. eight). Ask the agency how many years they've been working with Drupal and if they're up-to-date on the latest changes and updates. While compiling a list of qualified Drupal developers, be sure to ask for referrals from friends and family members. You can also ask the development agencies that you contact if they have any recommendations for qualified developers in your area. Once you've compiled a list of potential Drupal developers, it's time to begin contacting them and asking questions. Narrow down your options and schedule interviews Once you've found a few qualified Drupal developers, it's time for the next step i.e., interviewing them. Here are some questions you can ask during the interview process: 1. How long have you been working with Drupal? 2. What is your favorite thing about Drupal? 3. What are some of the most challenging aspects of developing with Drupal? 4. Can you share a project that you worked on that you're particularly proud of? Make a decision and sign a contract for Drupal web development Once you've interviewed a few prospective Drupal developers, it's time to make a decision. Choose the developer that best fits your needs and sign a contract with them for Drupal web development services. If you’re looking for a Drupal developer, we hope this guide has been helpful. But if you still have questions or need more assistance finding the perfect fit for your project, don’t hesitate to contact us by email. We would be happy to help you find the best Drupal developer for your needs and budget. Thanks for reading! Articles Off The case for communication between designer and developer How can you choose the right Drupal 9 development partner? Infinity Stones Of Drupal Development Roles Facilitating Successful Drupal Development Hiring The Right Skills for Your Decoupled Drupal Development [Less]

Accelerating Drupal Development with Drupal Console and Drush Manish Saharan 22 Feb, 2022 We’ve written extensively (we’re into this stuff) ... [More] about how Drupal 8 has not just modernized digital experiences for the user but also eased out development work for Drupal developers. In this article we’re going to discuss two such Drupal 8/9 utility tools that have massively simplified and improved the way you work with Drupal code, modules and installations - Drupal Console and Drush. What is Drupal Console Since the advancement of Drupal 8, it has become necessary to add a lot of boilerplate code to build a new module. Of course, you can simply copy and paste the code, but doing so repeatedly might open doors to a lot of errors. It’s ok. We’re human. Luckily, we have Drupal console - a suite of tools that you run on a CLI (Command Line Interface) that lets you automatically generate boilerplate code. It leverages Symfony Console and other third party components to generate most of the code needed to build a Drupal 8/9 module. What is Drush Drush (Drupal + Shell) is the original CLI tool for Drupal. It lets you spin up new Drupal websites easily and helps you streamline development and administrative tasks. Drush comes shipped with many easy-to-implement commands that lets you interact with your Drupal installations, themes, modules and more. Some of the other tasks that you can perform with Drush are exporting/importing configurations, caching, updating contrib modules, updating the database and much more.  Drush works well with Drupal 6/7/8/9 and offers advantages of modern development practices. It helps save development time, both during migration of existing Drupal modules and while creating new ones thereby increasing productivity. Learn how to create your own custom Drush commands in this article. Installing Drupal Console Drupal console can be installed through various methods like composer, curl, phar etc. Here is an example of installing it using composer: Install globally via composer composer global require drupal/console Site specific installation     1. Navigate to Drupal site in CLI:  cd /path/to/drupal_site     2. Execute composer require command: composer require drupal/console:~1.0 --prefer-dist --optimize-autoloader Installing Drush Drush can be installed through various methods as well like composer, curl or phar. Here is an example of installing it using composer: Install globally via composer composer global require drush/drush Site specific installation     1. Navigate to Drupal site in CLI: cd /path/to/drupal_site     2. Execute composer require command: composer require drush/drush Drupal Console Commands and Usage Check out some of the most popular and helpful Drupal Console commands and when they can be used. Drupal Debug Command To identify the breakpoints while working on themes: drupal debug:breakpoints {theme_name}           Example: drupal debug:breakpoints bartik To easily find the class and name of the service when working with services: drupal debug:config:settings To identify the fail point when you have painful broken blocks: drupal debug:plugin block broken Generate Custom Modules Create custom modules within a minute using this command: drupal generate:module  \   --module="modulename"  \   --machine-name="modulename"  \   --module-path="/modules/custom"  \   --description="My Awesome Module"  \   --core="8.x"  \   --package="Custom"  \   --module-file  \   --composer  \   --test  \   --twigtemplate Generate Custom Form Custom forms requirements are very common across projects. Creating custom form easily with this command: drupal generate:form  \   --module="modulename"  \   --class="DefaultForm"  \   --form-id="default_form"  \   --config-file  \   --path="/modulename/form/default" Generate Config Form As like custom forms, we require administrator configured forms as well. With this command you can create them easily: drupal generate:form:config  \   --module="modulename"  \   --class="DefaultForm"  \   --form-id="default_form"  \   --config-file  \   --path="/modulename/form/default" Generate Controller With custom forms you will need controllers. You can easily create custom controllers with this command: drupal generate:controller  \   --module="modulename"  \   --class="DefaultController"  \   --routes='"title":"ControllerMethod",  "name":"modulename.default_controller_hello",  "method":"hello", "path":"/modulename/hello/{name}"'  \   --test Generate Custom Entity Creating a custom entity does not have to be time consuming, With this command you can create it quickly and easily: drupal generate:entity:content  \   --module="modulename"  \   --entity-class="DefaultEntity"  \   --entity-name="default_entity"  \   --base-path="/admin/structure"  \   --label="Default entity"  \   --is-translatable  \   --revisionable   --has-forms Generate Custom Service This command helps you to create custom services: drupal generate:service  \   --module="modulename"  \   --name="modulename.default"  \   --class="DefaultService"  \   --interface  \   --interface-name="InterfaceName"  \   --path-service="/modules/custom/modulename/src/" Create Content like user:create To create a user from the back-end you don’t need to open the browser and login with admin and then create an account. Simply use this command to create a user in a jiffy: drupal user:create  username password  \   --roles='authenticated'  \   --email="[email protected]"  \   --status="1" Generate Plugin like block Drupal Console is also capable of generating many plugins like blocks. Here is an example of creating a custom block: drupal generate:plugin:block  \   --module="modulename"  \   --class="DefaultBlock"  \   --label="Default block"  \   --plugin-id="default_block"  \   --theme-region="header"  \   --inputs='"name":"inputtext", "type":"text_format", "label":"InputText", "options":"", "description":"Just an input text", "maxlength":"", "size":"", "default_value":"", "weight":"0", "fieldset":""' For more Drupal console commands and usage check these Available commands. Most Popular Drush Commands  drush cr  To rebuild Drupal cache  drush cim  To import all the configuration files  drush cex  To export configuration files  drush uli  To login using one-time login url  drush en  {module_name}  Enables any module either custom or contrib or core  drush pmu  {module_name}  Disables and uninstalls any module  drush pm:list  Lists all modules with the package, module name, version and status  drush updb  To update the database after upgrade  drush watchdog:list(ws)  Lists all the watchdog messages  drush watchdog:tail(wt)  Continuous tail watchdog messages  drush watchdog:tail --type=php  Continuous tail watchdog messages with particular severity type A Few More Cool Drush Commands  drush status  Provides an overview of the current Drupal installation  drush generate  As like Drupal Console, the drush generate command helps to   generate entities, plugins and more  drush pm:security  To check Drupal composer package for security updates  drush migrate:status  Lists all migrations with current status  drush user:password {username}   {password}  Sets user password  drush user:block  Helps block the user  drush user:role:add  Helps add user roles  drush sql-dump  Exports the Drupal database as SQL using mysqldump or equivalent. The two command line tools in focus today - Drupal Console and Drush - are quickly becoming every Drupal developers’ favorite gear because they are great time-savers and improve productivity. Both of them are highly extensible, in that you can create custom commands catered to your requirements. If you found this article helpful, you might want to subscribe to our newsletter where you get fresh and interesting articles on Drupal, Open-Source and Technology delivered to your inbox every week! Drupal Development Drupal 9 Drupal 8 Drupal Planet Drupal Tutorial Leave us a Comment   Recent Blogs Image Accelerating Drupal Development with Drupal Console and Drush Image Everything you need to know about Website Accessibility Image Getting Started with Lando and Drupal 9 Want to extract the maximum out of Drupal? TALK TO US Featured Success Stories Upgrading the web presence of IEEE Information Theory Society, the most trusted voice for advanced technology Great Southern Homes, one of the fastest growing home builders in the United States, sees greater results with Drupal 9 Upgrading and consolidating multiple web properties to offer a coherent digital experience for Physicians Insurance View all Case Studies [Less]

This past weekend was at Florida Drupal Camp, and I gave a talk about using PHPStan to tighten up your Drupal codebase. For the past two years, the Drupal community has been leveraging PHPStan indirectly through drupal-check and Upgrade Status to ... [More] find usages of deprecated code as we journeyed from Drupal 8 to Drupal 9. This is barely the tip of the iceberg of what value PHPStan provides, but it had an immense impact. [Less]