FrankBoard Plugin Compatibility and Integration Guide
FrankBoard Plugin Compatibility and Integration Guide
Understand how FrankBoard leverages the Kanboard engine while providing a modernized user interface. This guide clarifies the relationship between the core backend and frontend extensions.
Is FrankBoard compatible with Kanboard plugins?
FrankBoard is built on the Kanboard engine, meaning it retains the core backend logic of Kanboard. However, because FrankBoard implements a completely redesigned modern UI, plugins that modify the visual interface or add frontend elements will not appear or function correctly.
Will backend-only Kanboard plugins work with FrankBoard?
Plugins that operate exclusively on the server side—such as those handling API integrations, automated task movements, or database triggers—generally remain compatible. If a plugin does not require a custom UI component to function, it will likely operate as intended.
Why don't UI-based Kanboard plugins show up in FrankBoard?
FrankBoard replaces the legacy Kanboard frontend with a polished, modern interface. Since UI plugins are designed to inject code into the original Kanboard templates, they cannot find the necessary hooks to render within the FrankBoard environment.
Can I install Kanboard plugins via the FrankBoard dashboard?
Since FrankBoard utilizes the Kanboard core, you can manage plugins through the standard administrative channels. However, users should verify if the plugin is a backend utility or a frontend enhancement before installation to ensure it provides actual value.
Does FrankBoard offer its own set of native plugins?
FrankBoard focuses on providing a streamlined, bloat-free experience out of the box. Rather than a fragmented plugin ecosystem, it integrates essential productivity features directly into the core UI to maintain stability and performance.
How does the relationship between FrankBoard and Kanboard affect updates?
FrankBoard acts as a modern layer over the Kanboard engine. While it benefits from the stability of the underlying project management logic, updates to the Kanboard core are vetted to ensure they do not break the custom frontend experience.
What happens if a plugin conflicts with the FrankBoard UI?
In most cases, a conflicting UI plugin will simply fail to render, leaving the FrankBoard interface untouched. If a plugin causes a critical backend error, it can be disabled via the file system or the administrative plugin manager.
Is it possible to use FrankBoard and still have a 'minimalist' setup without plugins?
Yes. FrankBoard is specifically designed for teams who want a polished Kanban experience without the need to hunt for third-party plugins to make the software usable or visually appealing.
Are there any risks to installing legacy Kanboard plugins on a FrankBoard instance?
The primary risk is functional redundancy or unexpected backend behavior. While they rarely 'break' the modern UI, installing unnecessary plugins can increase the resource footprint of your Docker container.
Can I migrate my Kanboard plugins when moving to FrankBoard?
You can migrate your data and backend configurations, but you should audit your plugin list. Only migrate plugins that provide backend automation or API connectivity, as visual plugins will be obsolete.