nocobase-plugin-development

Developing a NocoBase plugin involves scaffolding a template, implementing server-side collections and APIs, adding client-side blocks and fields, configuring i18n, and verifying enablement. A strict plan confirmation is enforced before coding begins to ensure reference-driven implementation.

NocoBase plugins support both server-side extension points like collections, APIs, ACL, and migrations, alongside client-side UI components including blocks, fields, actions, and routes. Internationalization setup is also supported across these extension points.

Yes, you can scaffold a NocoBase plugin using official commands that generate a template codebase. This scaffolding step is the starting point for integrating server-side resources and client-side UI components before enabling the plugin.

The NocoBase plugin workflow enforces a hard gating plan before coding: you must confirm an implementation plan, scaffold the template, implement features using references, set up internationalization, and verify enablement in a running instance.

Yes, NocoBase plugin development includes internationalization setup as a core feature. You configure i18n during the implementation phase to ensure your client-side UI components and server-side resources support multiple languages.

A plan confirmation is required before coding your NocoBase plugin to enforce governance and reduce boilerplate. This gating step ensures reference-driven implementation of collections, APIs, ACL, and blocks before you proceed to enablement verification.