Plugin or theme

Plugin or theme?

The split is simple. Look is the theme’s job, and anything you must keep is a plugin’s job.

Goes in the theme

How the site looks and is laid out: templates, colors, and block layouts.

Goes in a plugin

What the site must keep after a redesign: custom content types, integrations, and bookings.

That split is why my themes keep listings and bookings in a companion plugin. You can change the look later without losing the content. I build custom themes too.

Approach

How I build them.

  • Small and focused. One plugin does one job.
  • Documented, so the next developer can follow it.
  • Input is sanitized and output is escaped. Every form and admin action checks a nonce and a capability.
  • Server-rendered by default, with front-end JavaScript only when the plugin needs interaction.
  • A clean uninstall path.

Proof

TOCguide, a plugin I shipped.

TOCguide builds a table of contents from the headings in a post. It is a Gutenberg block, with a shortcode for classic content.

Server-rendered

The outline is in the first HTML, so search engines and screen readers see it.

Free and private

GPLv2 or later, with no tracking.

Opt-in extras

The Reading Guide and study tools stay off until you turn them on.

See the TOCguide project, or read how I published my first WordPress.org plugin and why I built a table of contents block.

Questions

Common questions.

Who owns the plugin code?

You do. The domain, hosting, database, and code are all yours. After handoff, I don’t have access unless you invite me back.

Can another developer take over the plugin later?

Yes. I keep each plugin small and documented, so the next developer can follow it.

Do you build blocks for the editor?

Yes. TOCguide is a Gutenberg block with a shortcode for classic content. Tell me what your block needs to do.

Get in touch

Need a custom WordPress plugin?

Tell me what WordPress can’t do for you yet. Looking for something else? See all services.

Remote · within one business day (ET)