Hi Scott!

You will have the following problems, I think:


-          The split between author/public systems will make your use case 
(everything editable by the community) a bit of a pain to implement. Which 
parts do you handle using "authoring features", and which parts do you write 
your own forms for? Do you cluster all content and forget about publishing, or 
do you publish some things one way and some things the other? Sounds like a 
headache.

-          Learning magnolia and creating 3 sites sounds like a lot for one 
person alone. Could be done, esp. if that person has Java and CMS experience, 
but IMHO magnolia is better suited to small to medium teams rather than 'lone 
wolves'.

-          If you're planning to run 2-3 sites, you'll have to deal with the 
fact that the community edition doesn't support multi-site (or pay for 
enterprise). Not really a big problem, there are solutions, but another thing 
to deal with...

My take, without knowing what you are doing exactly:

If your requirements are such that you can leverage magnolia's strengths (for 
example: very flexible templating and data-definition support, very natural GUI 
for editors, java extensibility) then go with magnolia.
If your requirements are more oriented towards community features (forum, 
commenting, user-supplied content, every user of the site is also an editor, 
etc...), then there may be better packages for you, which focus more on this 
type of thing and less on web content management.

Regards from Vienna,

Richard


Von: [email protected] [mailto:[email protected]] 
Im Auftrag von Scott Finnie
Gesendet: Samstag, 20. November 2010 22:10
An: Magnolia User-List
Betreff: [magnolia-user] How well does magnolia scale down?

Hello all,

I'm looking for a CMS to host a few small-scale community sites.  Magnolia 
looks very impressive, but I'm wondering if it might be overkill for my needs - 
so would appreciate any advice.  By "small scale", I mean 2-3 sites, each with 
10-20 pages and hit rates in the 10s per day range.  All 3 will be hosted on a 
single virtual server (0.5GB RAM).

So: is Magnolia appropriate or a bit of a hammer to crack a nut?  In 
particular, I'm interested in any experience with the dual instance 
architecture.  My sites all need to support editing by the community (hence cms 
not flat pages).  Any problems/considerations with general community members 
editing & publishing content?

Many thanks,
Scott.


________________________________
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: 
<[email protected]<mailto:[email protected]>>
----------------------------------------------------------------


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to