Wheels Plugin Generator

Creating a CFWheels plugin generates a complete scaffold with index.cfm, box.json, and optional config/, controllers/, models/, views/, events/, db/, and tests/ directories following Wheels conventions. This standardized structure ensures your plugin is organized, maintainable, and ready for distribution.

Yes. The plugin generator includes a box.json template configured for ForgeBox integration, enabling you to publish your plugin as a discoverable, installable package. This automates the metadata setup so your plugin can be easily shared with the Wheels community.

The plugin scaffold provides entry points and examples for registering event handlers and global, model, controller, or view helper methods using mixins. This lets you extend Wheels functionality and inject reusable logic across your application.

A plugin entry point (index.cfm) is the initialization file that loads your plugin's configuration, registers events, and applies mixins when the plugin is loaded. It serves as the single control point for your plugin's activation within a Wheels application.

No. The plugin generator automates boilerplate creation, including directory layout, configuration files, event handling templates, test structure, and documentation stubs. This lets you focus on your plugin's core functionality instead of setup.

Yes. The generator is designed for packaging reusable Wheels components with ForgeBox metadata, making it ideal for creating distributable plugins that extend Wheels functionality or add domain-specific features for broader use.