Jan 13, 2006
The perfect CMS
My quest for the perfect development CMS continues. Drupal seemed like a good choice before, but it has issues.
It's fairly easy to create a full-featured multi-user website, but the
background application is fairly unstable, and the security sub-system
is ridiculously complex. Complexity in a security module, bad.
So I lined up a few more to try. E107, which has almost the right features. Not quite. Geeklog turned out to be a nice option. Security is its strong point. However not so easily extensible, and it still doesn't have everything I'm looking for. I tried about ten other CMS packages that aren't memorable at all. Then I tried out the king of the hill. Typo3. It's extremely well done. The code is impeccably clean. Written for professional content developers. Consequently, it's very difficult to use.
Maybe I'll haveta' write my own...
So I lined up a few more to try. E107, which has almost the right features. Not quite. Geeklog turned out to be a nice option. Security is its strong point. However not so easily extensible, and it still doesn't have everything I'm looking for. I tried about ten other CMS packages that aren't memorable at all. Then I tried out the king of the hill. Typo3. It's extremely well done. The code is impeccably clean. Written for professional content developers. Consequently, it's very difficult to use.
Maybe I'll haveta' write my own...
No votes
But maybe we don't really need that...
-- Larry Wall in <199709011851.LAA07101@wall.org>
-- Larry Wall in <199709011851.LAA07101@wall.org>

Digg
Delicious
Netscape
Technorati