atomic-framework-plugins

Plugin lifecycle management in the Atomic Framework controls the register, boot, activate, and deactivate flows for first-party and custom plugins. It uses dependency-aware bootstrap behavior to ensure core and user plugins load safely in the correct order.

To create an Atomic Framework plugin, you register it with the PluginManager, define its boot order, and add routes and migrations. You then connect it to existing Atomic hooks and services using safe extension patterns for production development.

Yes, the Atomic Framework supports built-in integrations with WooCommerce and WordPress, alongside Monopay, RSS Reader, GlobusStudio, Google, and GoogleAnalytics, allowing plugins to connect directly to these external services.

The best way to handle boot order is using PluginManager helper functions, which manage dependency-aware bootstrap behavior to load core and user plugins safely without guessing the lifecycle or integration points.

User plugins fail to load during the Atomic Framework bootstrap phase when their dependency-aware boot order is incorrect. You must use PluginManager workflows to ensure helper functions register and activate plugins in the proper sequence.

Yes, you can use PluginManager helper APIs to safely extend production plugins in the Atomic Framework. They provide safe extension patterns that govern plugin registration, lifecycle flows, and dependency-aware bootstrap behavior.