Tagteam is a mvc-patterned web application framework that features a built-in cms. The cms is cool, and the interface is alright. The framework will never be anything close to as good as Ruby on Rails.
Arriving at the same conclusion.
Conceived in response to the number of sites I was building that required basic cms functionality (editable pages, links, news, etc.) with a usable interface, Tagteam features an easy-to-use cms interface free of frightening mazes of input boxes, cryptic configuration directives, and advanced options.
Similar to Basecamp in its interface widget design, Tagteam’s cms is lightweight, snappy, and intuitive. For editing content, it can use either Textile, or Markdown and it always produces valid markup. Full standards-compliance is one of Tagteam’s mantras.
Integration is as simple as a few lines of php code. I designed Tagteam so that I could let my partner (a designer with no programming skills) easily add cms functionality to an otherwise static design.
Because Tagteam’s code is object-oriented, getting (for example) the 10 most recent news posts from the built-in cms is as easy as adding
<?= $news->getPosts(10) ?> to any page.
Midway through my journey, with all the buzz surrounding 37signals’ Basecamp, I found my way over to Ruby on Rails and promptly registered for the second Building of Basecamp workshop in Chicago (that’s right—I was there before RoR was so cool. I’ve also been listening to nirvana since 1979) where I learned more in one day than I typically learn in a month. It was, and I blush as I say this, a near life-changing experience. I got completely into Ruby (and Rails) and left php (and Tagteam) in the dust.
Which brings us to the present. Here’s Tagteam, dusted off.
Sites using Tagteam:
Tagteam is open source and licensed under the terms of the GPL.
Browse source (anon : anon) http://smg.textdriven.com/svn/tagteam/trunk/
$ svn co smg.textdriven.com/svn/tagteam/trunk --username anon --password anon