Comments on: You should use Symphony CMS, right now.

By: Jonas

Jonas — Sun, 25 Dec 2011 02:32:03 +0000

Glad to hear it, Dave! Best of luck getting started.

By: Dave

Dave — Sat, 24 Dec 2011 18:35:54 +0000

Thanks Jonas, you’ve confirmed my suspicion. I think I’ll be falling in love with Symphony.

I’ve download, installed and just started to dig in to the concepts. It was through the the Symphony site that I ended up here!

I knew there was a reason I bought this giant O’Reilly book, XSLT by Doug Tidwell a few years ago.

Kind regards.

By: Oliver

Oliver — Sun, 18 Sep 2011 02:19:00 +0000

I am glad others feel the sa,e about Symphony as I do, just getting started with it and the template system using XML is new to me.

However Thats one negative, on the positive side, including all the things said above, its the only system I have found that can (really) easily and quickly import affiliate data feeds

By: Jonas

Jonas — Thu, 02 Sep 2010 18:10:42 +0000

Agreed — my experience is that Drupal and Joomla provide the opposite approach — systems that give you everything plus the kitchen sink, and your job is to take out the parts you don’t want. This can be great for big sites that need all those features, but for the rest of us, not so much.

Out of the four you mentioned, Textpattern is definitely the closest in philosophy to Symphony, and it’s somewhat easier to learn for novices. But it doesn’t have nearly the raw architectural power of Symphony. I’ve also found the TXP plugin scene to be rather confusing and fragmented.

By: Guille

Guille — Thu, 02 Sep 2010 17:57:42 +0000

Well,… you’ve convince me

Like many others, I’ve also try “the Big three” (Drupal, Joomla & WP) and ended with fourth – Textpattern. The most elegant and minimal of them all, + perfect for designer (non-developer) like me.

I remember some time ago I’ve try Symphony and was impressed with customization of sections as core feature. But, in that time there was very little extensions even for some simple things, terrible documentation, small community… plus Txp was more than enought for me.

Don’t know why, but few days ago I’ve decide to give it a try once more.. I explore different solutions from time to time. I’m sure I’ll keep with Txp on many sites, but I think I’ve found replacement for Drupal, which I’m using when Txp simply isn’t enought.

The “big three” have became real junkyard of confusing code, bugs and crappy plugins, and with time they’ll be even worst. On the other side, Symphony seems really clean’n'simple.
In next few months, if I get time, i’ll make some comparison.

By: Building a site with Symphony CMS, Part 1 | RocketFoo

Building a site with Symphony CMS, Part 1 | RocketFoo — Sat, 10 Jul 2010 19:41:52 +0000

[...] As promised, I’m going to take you on a walkthrough of building a new site with Symphony CMS. I’ll be referring to my new personal site to demonstrate some functional examples. If you’re not sure why you should use Symphony, have a look at my previous post and then check out the Symphony beginner’s guide. [...]

By: Robert Stanford

Robert Stanford — Tue, 06 Jul 2010 09:56:06 +0000

Good post. I’m very fond of Symphony’s minimalist approach – nothing is predefined or preconfigured, instead it makes it very easy to define your own data models, define queries to get at that data (or external feeds, as you mentioned) and use standards-based templates to transform it to HTML (or indeed any other language). It’s almost more like a GUI to a simple web-application framework than a CMS. All of which makes it really flexible. Bonus.