We've only been using magnolia for a short time, but some comments:

On Dec 26, 2005, at 3:06 AM, (Alexey Lapusta) wrote:




Some features, which were found in OpenCms, that I want in Magnolia.

1) Templates:
- it can't be edited from backend =(
I'm not sure, at least in our company, that this would be a good idea. As developers, we're responsible for the template, not the end user. We'd never let end users create or manage the actual template, and in any case, how would you? For a simple page template maybe there could be an HTML editor, but for complex scripts it wouldn't make sense.



- some other problems:
"Once you've created a new template in the admin UI, you have to
create the template on your file system - inside the web application.
This may make it difficult to upgrade if you're deploying Magnolia as
a WAR.
How else do you expect to do complex tasks? Besides, its not hard to extract the war, put the templates in the right place, and then compress it again for distribution.


The worst part is after creating the template, you have to
restart the server. WTF? That seems a bit ridiculous to me. Granted
you'll likely be designing your master template in a development
environment - but good luck installing Magnolia for a client and
having them create a new template."
I've never had to reboot the server to install or create a template. Is that in the documentation somewhere? Again, for us we won't have clients creating new templates - thats pretty counter to the whole purpose of a cms.



2)Modules:
- i haven't found any modules for Magnolia - like polls, forums and so on =(
- for example, I need an area, where some documents will be stored and
I want people to register on my site to get an acess to this
download-area.
We'd might like this too, but we use magnolia as the baseline for our project, not because its a java clone of phpbb. If we wanted a forum and didn't want to write it, there are plenty of solutions out there already. Personally, I think I would be less happy if magnolia had closely-knit modules like that. However, if modules are easy to disable and remove, then I think that would be ok :)




As my trainer said, I think you're thinking about this all wrong - templates should be made by you, with easy to use and understand dialogs so that the client (the author) can enter in their content with minimal knowledge needed.


-Branden Root


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to