## Why the integration list differs between themes
URL: https://hub.jkdevstudio.com/knowledge-base/jkd-toolkit/integration-list-per-theme
Updated: 2026-09-06
Summary: Why an integration available in one jkdevstudio theme is missing in another, and why translation integrations are included by default.
The Integrations tab lists the integrations available for the theme you are running. Open a different jkdevstudio theme and the list is different. That is intended, and this page explains the rule behind it.
## Each integration names its themes
Every integration carries its own list of products it supports. Your theme shows only the ones that genuinely work with it.
So the scenario people ask about, seeing integration A in one of our themes and not in another, is the system working. The other theme has B instead.
The reason is fit rather than restriction. An integration built around a magazine layout has nowhere to render in a portfolio theme, and shipping it there would create a setting that does nothing.
## Translation is the default
The one integration category present in any of our themes is translation. Two of them are: [WPML](/knowledge-base/integration/wpml-language-switcher) and [Polylang](https://wordpress.org/plugins/polylang/), which are the two plugins that translate a WordPress admin string rather than a page of content. Everything else is opt in.
The reason is narrow and worth being precise about: those two are what allow **our own admin strings** to be translated on a multilingual site. The theme panel, Theme Options and everything else we render into the dashboard. Both read the text domains our products register, which is how a Ukrainian or German administrator sees our settings screens in their language.
**This is about translating the interface, and it does nothing for your front end.**
Nothing here translates a post, a page or a menu label your visitors read. Front end multilingual is a separate job done by the translation plugin itself, and the visible part of it in the theme is the language switcher, which is its own integration per provider.
Translating your site and setting up RTL
## How the list is ordered
Self contained integrations come first, then the ones that sit on top of a third party plugin.
That order is more useful than alphabetical, because the first thing you want to know about an integration is whether using it means installing something else as well.
## What each integration page tells you
The format is the same throughout, so you can skim it:
- what it adds
- where it is switched on
- what it requires
It is a reference rather than a showcase. If an integration needs a third party plugin, that is stated on its row and on its page.
## Common questions
Why do WPML and Polylang appear even though my site is in one language?
Because they are the interface translation layer rather than a multilingual feature, so they are listed for every theme, and on a single language site you simply leave them off.
Can I request an integration for my theme?
Yes, and it goes in as a [feature request](/knowledge-base/customer-hub/sending-a-feature-request) rather than a support ticket, because it is a roadmap question rather than a fault.
Will the list grow?
It does over time, and new integrations appear in the tab on their own with nothing to reinstall.
I use a service you do not have an integration for
Its own plugin will usually work perfectly well, and what you lose is the theme level styling and placement that an integration provides.
Does an integration work on the free edition?
The registry and the screen are visible on a free edition, while the catalog they install from comes with an active licence, so the list is browsable and the install is not.
I expected an integration and it is not listed
Check that the theme and the Pro plugin are both up to date first, since the list is served against the current pair, and if it is still absent then it is not supported for this theme and a feature request is the right channel rather than a ticket.