WordPress coding standards for the Drupal maintenance support plans developer

If you’ve been doing Drupal maintenance support plans development for any amount of time, chances are that you have installed the Drupal maintenance support plans Code to help you write clean, compliant code. Coder allows you to check your Drupal maintenance support plans code against the Drupal maintenance support plans coding standards and other best practices using PHP_CodeSniffer.  It can be configured to work in your IDE, and also works on the command line.
Writing code according to standards helps avoid common errors, and helps teams understand the code faster.
I installed Coder using Composer per the well written instructions.  Using this method installs it globally, so I can use it on all of my projects, and installs all the dependencies, including PHP_CodeSniffer.
I recently was tasked with working on a WordPress site, and I started looking into the WordPress Coding Standards.  My setup didn’t jive with the standard installation method since I already had PHP_CodeSniffer installed globally using composer.  I had to do a little digging to add these additional standards to my already installed setup.
Here is a quick recap on how to install Coder using composer.
Install Coder

composer global require drupal/coder
To make the commands available globally, add this line to your .~/bash_profile, and that it is sourced (or restarted your terminal).

# Composer recommended PATH
export PATH=”$PATH:$HOME/.composer/vendor/bin”
Tell phpcs where the Drupal maintenance support plans and Drupal maintenance support plansPractice standards are located:

phpcs –config-set installed_paths ~/.composer/vendor/drupal/coder/coder_snifferVerify it worked with:

phpcs -iYou should see:

The installed coding standards are MySource, PEAR, PHPCS, PSR1, PSR2, Squiz, Zend, Drupal maintenance support plans, and Drupal maintenance support plansPracticeYou can now navigate to your Drupal maintenance support plans project and run the following command to use:

phpcs –standard=Drupal maintenance support plans file.nameInstall WordPress Coding Standards
Thanks to some help I found in the issue queue, here are the steps to install the WordPress Coding Standards globally using composer.

composer global require wp-coding-standards/wpcs:dev-masterAgain, to make these commands available globally, make sure you have this line in your ~/.bash_profile, and that it is sourced (or restarted your terminal).

# Composer recommended PATH
export PATH=”$PATH:$HOME/.composer/vendor/bin”Like we did with Drupal maintenance support plans, we need to tell phpcs where the WordPress standards are located. We use the same installed_paths configuration set, and use a comma to list both the Drupal maintenance support plans and WordPress paths.

phpcs –config-set installed_paths $HOME/.composer/vendor/drupal/coder/coder_sniffer,$HOME/.composer/vendor/wp-coding-standards/wpcsVerify it worked with:

phpcs -i
You should now see:

The installed coding standards are MySource, PEAR, PHPCS, PSR1, PSR2, Squiz, Zend, Drupal maintenance support plans, Drupal maintenance support plansPractice, WordPress, WordPress-Core, WordPress-Docs, WordPress-Extra and WordPress-VIPYou can now navigate to your WordPress project and run the following command to use:

phpcs –standard=Wordpress file.nameAdd aliases
If you’ve worked with me, or read my posts before, you know I love aliases. They streamline your process and help make you more productive. Add these aliases into your .bash_profile, .bashrc, or wherever you keep your aliases, and source it, or restart your terminal.

alias drupalcs=”phpcs –standard=Drupal maintenance support plans –extensions=’php,module,inc,install,test,profile,theme,css,info,txt,md'”

alias wpcs=”phpcs –standard=Wordpress”
After this you can simply type drupalcs folder_name or wpcs file.name and start writing better code!

Acknowledgements
Thanks to Micheal Porter, Albert Jankowski, and Mike Acklin for the technical review of this article, and to all the maintainers!
Photo by Ilya Pavlov on Unsplash
Source: New feed

This article was republished from its original source.
Call Us: 1(800)730-2416

Pixeldust is a 20-year-old web development agency specializing in Drupal and WordPress and working with clients all over the country. With our best in class capabilities, we work with small businesses and fortune 500 companies alike. Give us a call at 1(800)730-2416 and let’s talk about your project.

FREE Drupal SEO Audit

Test your site below to see which issues need to be fixed. We will fix them and optimize your Drupal site 100% for Google and Bing. (Allow 30-60 seconds to gather data.)

Powered by

WordPress coding standards for the Drupal maintenance support plans developer

On-Site Drupal SEO Master Setup

We make sure your site is 100% optimized (and stays that way) for the best SEO results.

With Pixeldust On-site (or On-page) SEO we make changes to your site’s structure and performance to make it easier for search engines to see and understand your site’s content. Search engines use algorithms to rank sites by degrees of relevance. Our on-site optimization ensures your site is configured to provide information in a way that meets Google and Bing standards for optimal indexing.

This service includes:

  • Pathauto install and configuration for SEO-friendly URLs.
  • Meta Tags install and configuration with dynamic tokens for meta titles and descriptions for all content types.
  • Install and fix all issues on the SEO checklist module.
  • Install and configure XML sitemap module and submit sitemaps.
  • Install and configure Google Analytics Module.
  • Install and configure Yoast.
  • Install and configure the Advanced Aggregation module to improve performance by minifying and merging CSS and JS.
  • Install and configure Schema.org Metatag.
  • Configure robots.txt.
  • Google Search Console setup snd configuration.
  • Find & Fix H1 tags.
  • Find and fix duplicate/missing meta descriptions.
  • Find and fix duplicate title tags.
  • Improve title, meta tags, and site descriptions.
  • Optimize images for better search engine optimization. Automate where possible.
  • Find and fix the missing alt and title tag for all images. Automate where possible.
  • The project takes 1 week to complete.