FrankBoard Compatibility and Ecosystem FAQ
FrankBoard Compatibility and Ecosystem FAQ
Detailed answers regarding FrankBoard's relationship with Kanboard, plugin compatibility, and its architectural approach to project management.
Is FrankBoard compatible with Kanboard plugins?
FrankBoard is not compatible with Kanboard plugins. While it is built upon the core logic and data structures of Kanboard, it utilizes a completely different modern frontend and architecture that does not support legacy Kanboard extensions.
How does FrankBoard handle the core Kanboard logic?
FrankBoard leverages the robust backend logic of Kanboard to manage tasks, boards, and workflows. By separating the proven core engine from the user interface, FrankBoard provides a polished, modern experience without sacrificing the stability of the underlying system.
Can I migrate my existing Kanboard data to FrankBoard?
Yes, because FrankBoard is built on Kanboard's foundation, migrating your existing data is straightforward. Users can transition their project boards and task history into the FrankBoard environment without losing their organizational structure.
Why does FrankBoard omit plugin support in favor of a custom UI?
The decision to move away from plugins allows FrankBoard to eliminate 'enterprise bloat' and maintain a minimalist, high-performance interface. This ensures a cohesive user experience and prevents the stability issues often caused by conflicting third-party extensions.
Does FrankBoard support custom fields like some Kanboard plugins do?
FrankBoard focuses on a streamlined Kanban experience and prioritizes simplicity over complex custom fields. This design choice ensures the tool remains lightweight and intuitive for small teams who find enterprise-grade customization unnecessary.
Is FrankBoard an open-source alternative to Kanboard?
FrankBoard serves as a modern evolution of the Kanboard concept. It provides a self-hosted, developer-centric project management tool that avoids vendor lock-in while offering a significantly more contemporary user interface.
Will FrankBoard introduce a plugin marketplace in the future?
FrankBoard's current philosophy emphasizes a curated, minimalist feature set to avoid complexity. The focus remains on providing a polished, out-of-the-box experience rather than a fragmented ecosystem of third-party plugins.
How does the lack of plugins affect the security of a self-hosted installation?
Removing third-party plugin support actually enhances the security posture of a self-hosted installation. By reducing the attack surface and eliminating unvetted external code, FrankBoard provides a more secure environment for privacy-conscious teams.
Can I use Docker to deploy FrankBoard and maintain my data?
Yes, FrankBoard is designed for seamless deployment via Docker. By using Docker and a PostgreSQL database, users can ensure their data remains portable, backed up, and entirely under their own control.
What happens to my Kanboard workflows when I switch to FrankBoard?
Your core workflows and task movements remain intact because FrankBoard respects the underlying logic of the Kanboard engine. The transition changes how you interact with your tasks visually, but the fundamental way you manage your work remains consistent.