Extend Nexum through packages identified, installed and tracked by the Core. Each Extension must respect its contract and compatibility.
Package lifecycle
The Repository supplies a remote administration catalogue. The Core checks package identity, dependencies and version constraints, then manages installation and lifecycle. Modules, Plugins, Templates and language packs have different responsibilities and do not replace generic CMS services.
Install after verification
Before installation, check type, code, version, requirements and origin. Back up the database and files, then use Core tools. After activation, check permissions, public destinations and any declared Blocks. A Module update must follow its declared migrations.