WordPress Coding Standards exist for PHP, HTML, CSS and Javascript. By the time we’re done you’ll wonder how you ever lived without them! What can we Lint? The purpose of this post is to walk you through the process of configuring your development environment with a wicked smart, WordPress optimized, set of Linters. When we configure our linters to enforce the WordPress Coding Standards, we end up with an extremely powerful automated QA ally sitting on our shoulder as we go about our work. But even if you’ve studied the standards inside and out, it’s very easy to lose sight of them in the heat of the hunt.Īnd that’s why our linters are so important. If you’ve spent time contributing to WordPress or making your own themes and plugins you’ll most likely be familiar with many of these standards simply through seeing them time and time again. For the most part, WordPress it helps to ensure that the core of WordPress looks like it was written by a single person. These coding standards allow the community to collaborate in a consistent manner. That’s where the WordPress Coding Standards come in. If we let every developer apply their personality to the WordPress project we’d end up with an inconsistent, unreadable Frankenstein’s monster. The wider WordPress ecosystem including plugin authors, theme designers and power users stretches out even further.Ĭan you imagine how many different coding styles there must be across that ecosystem? WordPress now powers over 31% of the web and has thousands of people contributing code from every corner of the planet. Introduction to the WordPress Coding Standards (But particularly useful on large development teams). This is really important whether you’re a one man band or a 50 strong development team.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |