Content handling - Backend?

[jakobfdev]

Hi, I'm very pleased with how everything in grav looks so far. Since you guys already said, that the backend might take a while and content management might take even longer or will not be included in the first version of the backend (did I get that right?), I was thinking about writing a preliminary plugin for at least elementary editing with aloha editor or sth similar.
So I'd like to know what the approximate roadmap looks like regarding authentication and authorization? Is the base for user management already set? Will I find everything in the development branch? As far as I can see, the learn docs don't cover that yet...
Best regards and thanks for this project!
J

[jakobfdev]

Just thought about it again and maybe this issue is a little early to discuss, since you guys have the content handling in process. But I'd still like to know if there will be any class/API available for updating content or header fields of a page, that I might use in a plugin to implement frontend editing, aside from page creation etc

[mahagr]

Authorization and authentication are both already done, but I do need to separate them into own plugin as well as session handling (classes for all of those are already in Grav).

Admin allows currently creating new and editing existin pages & change configuration, plugin and template options. I just got the backend to work again, but I've not tested it through and I have no idea if everything works yet. Frontend editing doesn't really differ from admin at all as admin isn't much else than a plugin which hooks into /admin and uses its own template and pages.

[jakobfdev]

Thanks for that info. I'm interested to see how the admin plugin will interact with the auth/ACL system, since I guess they necessarily need each other.

So if I'd write a frontend editing plugin, would I have to write my own file handling for the .md files or could I use any of the classes from the admin plugin? I'm asking since that would mean having a dependency on another plugin which would not necessarily be mandatory. I guess that's not how plugins are meant to be...

But I somehow think persisting files would be a core function to the structure of grav itself and I would find it unnecessary to reimplement that in a plugin. What would you suggest? Will the admin plugin be part of every bundle?

[rhukster]

There is already a "save()" method on the page object.

https://github.com/getgrav/grav/blob/develop/system/src/Grav/Common/Page/Page.php#L415

Regarding the admin plugin. We are envisioning two versions:

1. A simple plugin for editing and creating content that will be part of the core-Grav bundle
2. A more all-powerful "pro" or "premium" plugin that provides much more control that will be a commercial plugin.

[jakobfdev]

Perfect, I think that answers all my questions. Thanks for your help and keep up the great work!

[schurb]

@rhukster Do you have an estimate when the admin plugin will be released? I would really like to use grav for our website but creating content for a n00b is hard.
Or do you simply refer to the Valve Time? ;)

[rhukster]

I think the simplified plugin will be ready in a month, maximum two. This will focus primarily on content creation but let you set/change a few config options also. I'm reworking the UI design now.