Pro / Studio roadmap

Community remains the generic, stable and publishable foundation. Commercial or business features must be delivered through separate extensions and must not be hidden in the frontend behind a simple license check.

Current Community status

The following are no longer Pro targets; they are already included in Community 0.1.33:

• advanced Theme Builder;
• recursive conditions;
• advanced validation and sync/async registry;
• form templates;
• visible history;
• advanced tree editing;
• versioned import/export and migrations;
• keyboard/axe accessibility;
• custom catalog and configuration panels.

Open-core principle

@vevedh/qform-builder-layer
= current Community Nuxt Layer

@vevedh/nuxt-form-builder
= recommended future Community Nuxt module

@vevedh/nuxt-form-builder-pro
= separate commercial extensions

@vevedh/nfz-form-studio
= possible NFZ business edition

Future names must still be checked on npm and for trademark conflicts.

Priority Pro / Studio features

Priority	Feature	Value
1	Zod / JSON Schema to QForm adapter	developer integration
2	NFZ/Feathers service to form	strong differentiation
3	Form to NFZ CRUD service/page	business generation
4	Versioned business packs	productivity and vertical products
5	Vue/TypeScript/Nuxt page export	Studio value
6	Workflows, webhooks and business actions	automation
7	Server RBAC, publication, audit and versions	enterprise governance
8	Multi-user collaboration	team usage
9	Headless/embedded canvas	advanced integration
10	Form generation from business descriptions	controlled acceleration

Mandatory server boundary

The following must not rely on frontend-only enforcement:

• licensing;
• RBAC;
• immutable audit;
• secrets;
• file storage;
• antivirus;
• webhooks;
• approvals;
• sensitive business rules;
• third-party connectors.

NFZ differentiator

The strongest NFZ path is:

nuxt-feathers-zod service
  → QForm Builder schema
  → Nuxt/Quasar form or CRUD page
  → secure Zod validation and Feathers hooks

Recommended order

1. publish and stabilize the Community module;
2. extract a reusable pure core;
3. add the Zod/NFZ adapter in a separate package;
4. ship business packs;
5. add code generation and workflows;
6. finish with guided generation, strict validation and human confirmation.