VonCMS - CMS custom buatan sendiri (React + PHP + SQL) – progress & review

[lenarshakira]

Yes, this is already part of the plan.

For VonCMS 1.27, I’m starting with a clean/blank theme intended as a proper base for theme development, so developers won’t need to strip down an existing production theme just to get started.

The plugin/module side will come next. The goal is to introduce a documented extension API together with an SDK, hooks/events, lifecycle methods, and development guidelines so third-party extensions can work without modifying core files.

Extension database migrations are also planned to be versioned separately from core migrations, allowing each plugin/module to manage its own schema changes during install and updates.

I want to build this in stages rather than expose an API too early and then break contributors every time the core evolves.

One thing that could help later is explicit extension compatibility metadata — for example, minimum/maximum supported core version and required dependencies in a manifest. That would make upgrades easier to validate before an extension is enabled.

Looking forward to seeing how the SDK/hooks model evolves.

 

[Vondereich]

One thing that could help later is explicit extension compatibility metadata — for example, minimum/maximum supported core version and required dependencies in a manifest. That would make upgrades easier to validate before an extension is enabled.

Looking forward to seeing how the SDK/hooks model evolves.

Yes, this is already part of the direction toward VonCMS 2.0.

The compatibility metadata, extension isolation, SDK/hooks model, and dependency handling are planned as part of the broader plugin/theme marketplace system.

The goal is to make third-party extensions safer to install, update and maintain without modifying core files.

By the way, how did you find out about VonCMS?