4. Anatomy of a WordPress Plugin

If you want to become a WordPress developer, learning how plugins are structured is essential.
A plugin can be very small or very complex, but the basic building blocks remain the same.
In this article, we’ll break down the structure of a clean, modern plugin so that even a fresher can understand how everything fits together.

---

What Exactly Is a Plugin?

A WordPress plugin is simply a folder that contains one or more PHP files.
WordPress reads these files and runs your code at the right time using hooks.

That’s all. A plugin is not something magical — it’s just organized PHP code that extends WordPress.

---

The Main Plugin File

Every plugin must have one required file (usually named after the plugin), for example:

my-plugin.php

This file contains:

• The plugin header (required by WordPress)
• Basic setup code
• Loading other files or classes

Here’s a very simple plugin header:

<?php
/**
 * Plugin Name: My First Plugin
 * Description: A simple example plugin.
 * Version: 1.0
 * Author: Your Name
 */

Without this header, WordPress will not detect your plugin.

---

A Clean Folder Structure

Beginners often put everything inside one big file.
This works for small projects, but becomes messy very quickly.

A better structure looks like this:

my-plugin/
  my-plugin.php
  inc/
  assets/
  templates/

Here’s what each folder is for:

• inc/
  All PHP logic, classes, and helper functions.
• assets/
  CSS, JS, images.
• templates/
  Any frontend UI or HTML that you want to separate from logic.

This simple structure keeps things clean and easy to manage.

---

Loading Code Using Hooks

Plugins depend heavily on WordPress hooks.
A hook tells WordPress: “When you reach this point, run my code.”

Example:

add_action('init', function () {
    // Your code runs when WordPress is initialized
});

You will use hooks for almost everything:

• Adding menus
• Registering scripts
• Creating custom post types
• Handling form submissions
• Running scheduled tasks

Understanding hooks will make plugin development straightforward.

---

Using Classes for Better Organization

In modern WordPress development, we avoid writing all code in a single file or using many global functions.
Instead, we use classes with namespaces.

Example:

inc/
  Admin.php
  Frontend.php

Each file can contain a class that handles a specific responsibility.

This keeps your code readable, testable, and easy to maintain.

A simple class example:

namespace MyPlugin;

class Admin {
    public function __construct() {
        add_action('admin_menu', [$this, 'registerMenu']);
    }

    public function registerMenu() {
        add_menu_page('My Plugin', 'My Plugin', 'manage_options', 'my-plugin', [$this, 'renderPage']);
    }

    public function renderPage() {
        echo "Hello from admin page!";
    }
}

Then you load it in your main file:

new MyPlugin\Admin();

You don’t need to master classes immediately, but start using them early to build good habits.

---

Using an Autoloader (Optional but Recommended)

As your plugin grows, you will have multiple classes.
Composer’s autoloading makes loading these classes automatic.

You simply set up a composer.json file, define your namespace, and Composer handles the rest.

This step is optional for beginners but becomes very useful in real-world projects.

---

Activation and Deactivation Hooks

Some plugins need setup tasks when they are activated, such as creating custom database tables or setting default options.

Example:

register_activation_hook(__FILE__, function () {
    // Code that runs on plugin activation
});

You can also run cleanup code on deactivation or uninstall.

---

What You Should Remember

You don’t have to become an expert immediately.
For now, just keep these points in mind:

• A plugin is a structured folder containing PHP files
• The main plugin file tells WordPress about your plugin
• Use folders to stay organized
• Use hooks to run code at the right time
• Use classes when your plugin gets bigger
• Autoloading helps manage large plugins

This understanding alone puts you ahead of many beginners.

---

What’s Next

In the next article, we’ll focus on Custom Post Types and Taxonomies, which are used everywhere in WordPress projects.

You’ll learn:

• What they are
• When to use them
• How to register them
• How to structure data properly