Have you thought about a headless, or decoupled forum? What this means is that the backend & frontend are separated. You could for example expose XenForo via REST API and then connect to the backend from a React app, etc. The idea of headless is to allow 1 backend to power multiple frontends, or to make it easier to think about replacing something in the future. It also provides a bit more security and is a nice way to separate the codebases from a dev perspective.
This is something that hasn't really been too popular, but I really would love the chance to integrate a headless forum w/ a client sometime in the future... just need to convince a client their business needs a community forum!
Anyways, just wondering what you all think about this concept and if it's viable? I think it is because with forums "on the decline", a headless forum offers a new opportunity to create a completely new frontend experience (obviously theming can be done too on non-headless) while maintaining the core software. For example, if MyBB spun off into a headless approach, they could offer their robust software as something that can power not just forums, but helpdesks / tickets, social media, and more because of how profiles, posts, and more function.
This is something that hasn't really been too popular, but I really would love the chance to integrate a headless forum w/ a client sometime in the future... just need to convince a client their business needs a community forum!
Anyways, just wondering what you all think about this concept and if it's viable? I think it is because with forums "on the decline", a headless forum offers a new opportunity to create a completely new frontend experience (obviously theming can be done too on non-headless) while maintaining the core software. For example, if MyBB spun off into a headless approach, they could offer their robust software as something that can power not just forums, but helpdesks / tickets, social media, and more because of how profiles, posts, and more function.
