We have our own integrations, each built for one specific external plugin. There are not many of them, and that is a decision rather than an oversight.
#What we integrate with, and why those
One criterion: how fundamental the tool is. A page builder, multilingual plugins, forms, newsletter, cookie consent. Few sites avoid all of those, and none of them is going to disappear in a year.
What is not on the list and will not be: niche utilities, widget packs, content extensions. The reason is worth saying out loud: most of what they do is already in the theme.
#Everything else is yours
A plugin outside that list is yours to choose and yours to own.
How it behaves, what it does to your speed, your layout and your site is outside our control, so we do not take tickets about a third party plugin's behaviour and do not build custom integrations for one. What we do want to know is when a third party plugin breaks the theme, because the fix may belong on our side: fixing somebody else's plugin is the part we cannot do.
#What is worth not installing
Signs rather than names, because names change and signs do not.
All in one collections. Hundreds of widgets and features in a single plugin, of which you will use three. All of it loads, and any of it can break.
Plugins with no updates for years, low ratings, few installs, or bought from questionable marketplaces. That last one separately: cracked copies of paid plugins are the most common way malicious code arrives on a WordPress site.
Plugins that duplicate what you already have. A second caching plugin, a second SEO plugin, a third block pack. Two plugins doing one job conflict rather than reinforce.
The positive version: in current WordPress, most needs are covered by the block editor and by what already ships with the theme. Install a plugin when you know specifically what is missing, rather than in advance.
#Practical checks
Before installing: when was it last updated, how many active installs does it have, and does the author answer on its support forum. All three are visible on its page in the plugin directory.
After installing: check page speed and walk the site. A plugin that costs you a second is worth knowing about on the day you added it, not three months later.
At any strange behavior: deactivate third party plugins first and check. That single step separates a theme problem from a conflict faster than anything else.
Fewer plugins is faster, safer and simpler to maintain. Three reasons, one decision.
#Common questions
Can I ask you to add an integration for a plugin I use?
Send it as a feature request, since it is a product decision judged on whether it would serve everybody using the theme.
A plugin I need conflicts with the theme
Tell us, because if the fix belongs on our side we want to make it, and if it belongs in the plugin then its author is the only person who can.
How many plugins is too many?
There is no number, only a question: can you say what each one is for, and if you cannot then that is your answer.
Do your integrations count toward that?
They are plugins too, built for this theme and tested with it, so install the ones whose features you actually use and leave the rest.
I am unsure about one specific plugin
Install it on a staging copy and compare, because ten minutes there answers the question completely, which is more than any recommendation can do.
#Still stuck
Open a support ticket naming the plugin and what happens with it active and deactivated.
Last updated
