Moqui is a content-aware framework which is really good. It really helps in
separating out the framework from cms functionality. However, in my
experience, most of the "applications" would generally require adhoc "content-
ids" that are nothing but "html-fragments" with probably "little-bits" of
dynamic content embedded in them. I have used Ofbiz and was modelling these
bits of data as Contents backed by freemarker template. This helped give the
control to the administrator in managing the html fragments displayed across
the application.
Attempting a similar approach using moqui is landing me into a problem -
"Creating the html fragments". Default Jackrabbit installation is more of a
repository (and a little bit of repository browser) than an editor. I have
tried looking for "simple" JCR clients which just "enable" me to create nodes
with html content. I was unsuccessful at this. I was able to find "very heavy"
implementations of complete cms (like hippo etc.) rather than a simple node
editor to manage html content.
Wouldn't it be a good idea to provide this OOTB in moqui (mantle?).
I would really like to hear if there are any simple JCR clients that I have
missed. Or if the same functionality can be achieved in the current version of
moqui real fast.
-Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Because other editors exist this is not a high priority for development for
Moqui Framework itself (that was part of the point of using a standard like
JCR).
If someone wanted to develop such a thing for Moqui I'd be happy to list it on
the Crust (add-ons) page, and perhaps consider reviewing it for inclusion in
the Tools component that is included with Moqui. The Crust page is here:
One option you might consider is using the WebDav interface. With this you can
mount it as a drive and create/edit content as if it was in a file system.
BTW, I haven't tested the content stuff much (it hasn't been a high priority
yet for things I've build with Moqui), so any feedback on how this works...
and/or bugs with the current implementation, would be welcome.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Moqui is a content-aware framework which is really good. It really helps in
separating out the framework from cms functionality. However, in my
experience, most of the "applications" would generally require adhoc "content-
ids" that are nothing but "html-fragments" with probably "little-bits" of
dynamic content embedded in them. I have used Ofbiz and was modelling these
bits of data as Contents backed by freemarker template. This helped give the
control to the administrator in managing the html fragments displayed across
the application.
Attempting a similar approach using moqui is landing me into a problem -
"Creating the html fragments". Default Jackrabbit installation is more of a
repository (and a little bit of repository browser) than an editor. I have
tried looking for "simple" JCR clients which just "enable" me to create nodes
with html content. I was unsuccessful at this. I was able to find "very heavy"
implementations of complete cms (like hippo etc.) rather than a simple node
editor to manage html content.
Wouldn't it be a good idea to provide this OOTB in moqui (mantle?).
I would really like to hear if there are any simple JCR clients that I have
missed. Or if the same functionality can be achieved in the current version of
moqui real fast.
-Thanks
Because other editors exist this is not a high priority for development for
Moqui Framework itself (that was part of the point of using a standard like
JCR).
If someone wanted to develop such a thing for Moqui I'd be happy to list it on
the Crust (add-ons) page, and perhaps consider reviewing it for inclusion in
the Tools component that is included with Moqui. The Crust page is here:
http://www.moqui.org/crust.html
One option you might consider is using the WebDav interface. With this you can
mount it as a drive and create/edit content as if it was in a file system.
BTW, I haven't tested the content stuff much (it hasn't been a high priority
yet for things I've build with Moqui), so any feedback on how this works...
and/or bugs with the current implementation, would be welcome.