Shipped features vs community plugins

Phials comes with several features that are built directly into the application. While these internal features use the same underlying plugin architecture, they are compiled into the main application. They do not run as separate JavaScript bundles, nor do they require manifest files or permission approvals.

As a developer, you will build and distribute community plugins. You can develop community plugins using the phials-plugin-example template. Once built, you can load and test your plugin by going to Settings > Plugins > Community plugins in Phials. For detailed setup instructions, see Getting started and Community plugins.

When publishing your plugin, you only need to distribute the following files:

• dist/manifest.json
• dist/main.js
• dist/styles.css (optional)

You cannot build or publish features directly into the core Phials application bundle.

See also

• Plugin types overview
• Plugin API and lifecycle