Using SPA in Tiki

Vue was introduced in Tiki quite some years ago (I don't remember how many exactly, excuse my rush :-)), and its introduction has played a crucial role in modernizing Tiki (from old technologies to the newest and more popular ones). However, since Tiki wasn't originally designed to integrate a fully separate frontend application that interacts with a separate backend through APIs or any other mechanism (which seems to be the trend nowadays), and this is because what Tiki does now used to be the trend back in the days at its birth.

Going back to the point, it made it hard for Tiki to leverage Vue's mot attractive and fundamental feature of frontend frameworks: "SPA" (Single Page Application). Tiki managed though to put in place a mechanism that allows itself to consume components built with Vue.

Why am I bringing this up?

Well, my point is not only for Tiki to follow the trend, but also to consider where Tiki could be in terms of UI/UX if it decides to follow the trend. Because, bear with me, most of modern UI libraries are now built with these frontend tools, which, if used strategically and mindfully, result in interfaces that promote better UX.

What do I have in mind really

First of all, I'm not a Vue expert, but I've done few contributions in Tiki involving Vue, and I enjoyed the journey so much that it led me to the idea of Tiki eventually using Vue's fundamental feature, "SPA". I have to admit that this isn't something easy to be brought in Tiki at all, but it can be achieved through progressive migrations.

If and only if this a point of interest for Tiki, I think one part in Tiki, i.e., Wiki (listing pages, creating pages, viewing, etc.), could be tackled and have it fully built in Vue. And of course, I would be willing to help make that happen.