Plugin Development

What a Contensio plugin is, how it's discovered, and the two install paths users can take.

The file layout every Contensio plugin follows, the namespace convention, and what each file does.

Every field in the plugin manifest, with examples.

Your plugin's entry point - the $ns property, registering routes, views, migrations, hooks, and lifecycle callbacks.

Actions, Filters, and UI render hooks - extend Contensio from your plugin without touching core files.

A side-by-side comparison for WordPress developers — same mental model, same function names, with a few deliberate improvements.

Place your plugin's admin links in the sidebar — Root, Tools, or Appearance, with one or many entries.

Register routes and Blade views under your plugin's namespace without clashing with core or other plugins.

Ship database tables with your plugin. They run automatically when a user enables it.

Four storage mechanisms for plugin data - choosing the right one avoids unnecessary migrations and keeps your plugin lean.

Make your plugin installable via Composer, discoverable on Packagist, and releasable on GitHub.

Common questions about building plugins — answered.

Common plugin development issues and how to fix them.