Comments on: Symphony

By: Rowan Lewis

Rowan Lewis — Sat, 24 Jul 2010 12:44:50 +0000

Strengths: As a developer, and part time designer, Symphony has been a wonderful platform, capable of building anything from a blog to an esoteric digital asset management system.

In the past I’ve slaved away using other content management solutions, only to have them fall short of the projects goals time and time again, nothing that I’ve seen gives you the flexibility to develop what you want, with your own markup, and with your own data structures.

Symphony gives me those things by the truckload, there really isn’t anything that can come close.

Weaknesses: The one problem with having power is that you need to know how to use it, sadly Symphony has been lacking a little in this regard until quite recently.

By: Neil Albrock

Neil Albrock — Fri, 08 May 2009 08:42:25 +0000

Strengths: Flexibility. For the programmer, used to developing solutions from scratch, Symphony offers the most friendly environment, particularly as it doesn’t impose too much of it’s own structure on you.

Templating. The use of XML and XSLT is inspired. It took me a while to get into XSLT, as it’s quite different to other languages. However, once you have unlocked it’s power you really can do anything with it.

Debug. Symphony includes a debug mode which shows you a wealth of information about the XML data being produced, variables available, templates being invoked and so on. Invaluable to the serious developer.

Extensions. There a lots of really excellent extensions available for Symphony, so if it doesn’t do it out of the box, you can usually find an extension to handle it.

Community. A vibrant community and very active forum are a fantastic resource for new and seasoned developers alike.

Weaknesses: Documentation. There is a lack of really deep documentation for Symphony. This is being addressed and the forum is really great. It can however be a little frustrating for the new developer.

By: Ruth

Ruth — Fri, 27 Mar 2009 17:02:33 +0000

Strengths: The simplicity of setting up a fully customised content management system. Perfect for any clients needs. Also extremely easy for clients to get to grips with.

Its templating ability is unmatch in my opinion, the use of XML means its completely flexible. A massive plus.

Support and the community is also amazing, always on hand to help with anything from problems with installing it, to making extensions and customised data-sources.

Weaknesses: There is a lack of documentation but I think the community and overture21 forum make up for that.

Its can be quite database intensive, which I’ve seen cause problems, but because of the amazing support in place, there’s already a shiny new caching feature.

By: David

David — Fri, 27 Mar 2009 16:58:46 +0000

Strengths: It’s very quick to build stuff

Weaknesses: XSLT is a whole new language to learn.

By: Nick Dunn

Nick Dunn — Tue, 17 Mar 2009 15:04:18 +0000

Strengths: * XSLT is the most structured and powerful templating language you could ever wish for
* Viewing your content as XML makes sense. Instantly obvious to a front-end developer mad on clean, semantic markup
* Content can be output as any format — HTML, XHTML, XML (native, RSS, Atom), JSON, CSV, PDF (anything that XSLT can do!)
* No more building content-entry forms for clients — define your own data models and the forms and validation are done for you
* Good performance under high load
* Growing collection of extensions to handle extra requirements (data types, caching, data migration, user management, forums, sending emails etc.)
* Have used it to build many types of site — one pagers, portfolios, forums, blogs, video/audio sharing communities, events and community voting, and even a JSON server for Google Maps

Weaknesses: * Lack of official documentation makes Extension development tricky, but more blogs are appearing and sharing experiences
* Not immediately obvious to beginners how Symphony works, but it “clicks” after a while