Plans For Keeping Plug-ins Current?

[bobrocke]

Grav's plug-in architecture is pretty handy for expanding what Grav does from it's core. But it brings the need to manage those plug-ins, which may be from the Grav team, the website designer, or third parties. And a site may end up with more than several.

Will the future update capability handle that?

[rhukster]

We're already working on a basic installer and updater to get the latest versions of plugins and themes. We will probably start of with a simple solution for now and then improve this over time to better support dependencies and such, perhaps built on top of composer.

Eventually we plan to have this integrated into the admin to allow for simple one-click install and updates.

[bobrocke]

That makes sense.

It will be fun to watch Grav develop to a v1 release and then begin the work to expand its capabilities to compete with Statamic (in the NoDB world) and even Perch (in the smaller DB world).

Just how much being open source will help Grav will be a good test. Statamic is a more traditional, paid product with good support and reasonable features. Perch is also traditional software but with even more features and even better support. Can open source, in this case, meet or exceed paid?

[rhukster]

There's no reason why Grav can't have as good as, or even better documentation and support than even these commercial options. Most of these are developed were developed by small one-man shops, whereas Grav was developed by RocketTheme, a company with experience working with and supporting users.

[rhukster]

We are working on something :) I'll close this for now. Open it again if you need to.