Symphony.

Craig announces a change of direction in his ongoing efforts to write about Symphony.

Symphony didn't start its life as open source software. It took more than two years for us to transition from a closed source to the open MIT license we use today. And even since then, the platform has still always been officially managed by a company. Its leadership, the Symphony Team, have always been employees—first of Twenty-one Degrees, then of Symphony CMS Ltd.

Allen, co-creator and chief architect of Symphony takes a journey all the way back to his misspent youth as a ninja assassin in training, slashing his way through both turmoil and triumph in the content management scene. He recounts his story with detail and historical accuracy; the comrades he fought battles with, some to their eventual departure. The gripping story will make you laugh and cry; it'll leave you perplexed and maybe even aroused.

Read Allen's story now to enrich your brain with Symphony's backstory.

Call it a spring cleaning—the first maintenance update for Symphony 2.2 features dozens of bug fixes and improvements.

On behalf of the Symphony team and the working groups, I'm pleased to announce the immediate availability of Symphony 2.2.

Email sending functionalities can vary from server to server. Symphony 2.2 introduces a new email API that allows the use of different “gateways” for sending email.

Symphony's support for localization continues to mature in version 2.2. This post details the most recent changes.

Working with the back-end UI has never been easier than it is in Symphony 2.2. Find out why.