Magnolia, That Great Unknown

At the user level, it is a rewarding and intuitive experience when it comes to creating websites, components, and content within content applications. Although, [in my opinion,] there is [a] slowness when it comes to going through the workflow when publishing. To add permissions at the administrator level (going through a PM role) is not very intuitive and a bit messy to give permissions to [other] roles and users.

I put this score, since most of the time, loading content with large images takes a long time [in my experience]. In addition, [I feel that] the content loading of nodes in Magnolia is very slow when there are [a lot] of these nodes. [In my opinion,] the same [can be said] for assets, [as] there are times when loading images takes a long time to render.

Magnolia is put to good use [when] creating a basic website with limited content. It is very easy for both the developer and the customer to contribute content. [In my opinion,] the part [that needs improvement] is in the documentation. Content and examples are missing [when trying to] develop certain properties. [In my opinion, the] Magnolia modules should be explained better in the documentation. In the interface, [I find that] it is difficult to move elements and nodes sometimes. [I also believe that] content loading is sometimes very slow when there are more nodes on the account.

Magnolia is a powerful cms on a par with the big ones, which is expressly focused on the needs of the client and is easy to use. However, special care must be taken to handle large numbers of nodes to avoid possible slowdowns in the environment. We also have an extensive menu of extensions from both Magnolia and external ones (although it would always be nice to have more).