halo-plugin-dev

To develop a Halo plugin, you scaffold backend Java code and frontend Vue components, then connect them using YAML manifests like plugin.yaml. This provides an end-to-end structure for building and updating Halo CMS plugins.

Creating custom extensions in a Halo plugin involves defining the GVK (Group, Version, Kind) structures. The plugin framework handles registration, allowing you to manage custom data models and apply RBAC templates for access control.

The best way to integrate a custom UI into the Halo Console is by building Vue frontend components that interact with the backend through an OpenAPI-backed UI client, ensuring alignment with Halo's project-structure conventions.

Yes, configuring RBAC templates is required when building a Halo CMS plugin if your plugin introduces custom resources or APIs. Defining these templates ensures proper role-based access control for your extensions.

Managing lifecycle hooks for a Halo plugin requires implementing specific logic within the backend Java code that responds to the plugin's start, stop, and installation events defined by the Halo plugin framework.

The plugin.yaml manifest for a Halo plugin must include metadata, extension definitions, and references to backend and frontend assets. This configuration ensures the plugin framework correctly loads and executes your components.