What’s the limit for inline comments, and how can you minimize them? Let’s look at a bad and a good example of inline comments, and how they’re chances to improve your code.
By default, a custom taxonomy panel is not added to the Gutenberg editor. That means by default authors are not able to select terms in the editor. Tonya shows you how to turn on the feature.
Adding gifs to your pull requests (PRs) can get them approved faster. Gifs can also help your tickets or issues get accepted. It works as you are showing the code or issue in action. Ryan Kienstra will show you how.
By default, a WordPress custom post type does not use the Gutenberg editor. Why? In this quick tip, Tonya walks you through the why and shows you how to enable the Gutenberg editor for your custom post types. Don’t worry. It’s literally one configuration parameter.
When you’re developing, the solution to your problem might already exist. Many problems in code aren’t new, whether in debugging or creating new features. Ryan Kienstra, WordPress Engineer, shares his insights of borrowing from existing solutions and making your job easier.
I’m thrilled to announce that WP Engine has named Know the Code as a Top WordPress Education Provider. I’m incredibly honored to be listed as a recommended solutions provider in their Solution Center. Let me share why.
Does it matter if a hook’s callback function comes before or after its add_action? My answer might surprise you. No, it does not matter to PHP or WordPress. Yes, it does matter for code readability. I’ll explain why in this article.
A common problem in WordPress is removing a hooked action (via remove_action) too soon, i.e. before the original action is added via add_action. The Beans framework solves this problem through its Actions API. It’s a major enhancement to the WordPress Plugin API. Let me show you.
Part 2 of a series on differentiating content. We need a way to provide contextual information about the content and give readers additional mechanisms to explore and discover content. WordPress provides us with taxonomies and their terms.
As developers, it can be confusing to understand the intent and role of the mechanisms in WordPress to differentiate content. What are post types, taxonomies and terms, and custom fields? Why do they exist? When do you use the built-in ones? When do you build a custom one? We need a definitive guide that provides structure and best practices for differentiating content. We need a Developer’s Guide. In this first part of the series, we’ll discuss the why, what, and when of the WordPress post type from both a technical and practical perspectives.