Frontend Foundation

This guide explains the core architectural role of Zova in the Cabloy monorepo.

What Zova is in Cabloy

Zova is the frontend half of the Cabloy fullstack architecture.

It is an intuitive frontend framework that combines strengths associated with Vue3 reactivity, React-style TSX rendering, and Angular-style IOC.

The point of this combination is not branding. The point is to make large business systems feel more natural to write and maintain.

Three enduring ideas define this design:

One point still matters throughout the monorepo docs:

Zova is not tied to one UI library.

That flexibility matters directly for Cabloy’s edition model:

Shared frontend engineering layer: both editions follow the same Zova-centered frontend direction, with Vue, Vite, Quasar tooling, and related libraries
Cabloy Basic UI layer: current public docs and examples align with DaisyUI + Tailwind CSS
Cabloy Start UI layer: the private commercial edition aligns with Vuetify-oriented frontend modules, workflows, and SSR site baselines

So docs and skills must separate shared Zova principles from edition-specific UI assumptions.

The highest-value Zova capabilities to preserve in the unified docs are:

For the deeper architectural concepts behind IoC, module boundaries, and scope-based resources, see IoC and Beans, Modules and Suites, and Module Scope. For the runtime-variant and startup model, see Environment and Config Guide, App Startup Guide, and System Startup Guide.

AI systems should not treat Zova as generic Vue with a few utilities.

Instead, they should:

preserve Zova’s model, IOC, and AOP conventions
detect the active edition before assuming a UI-library workflow
prefer the Zova CLI for scaffolding and refactor work
verify that the generated or edited code still matches Zova’s actual architecture