(Untitled)

[grimreaperkitty]

This post is about Terrouge Firebird. If you don't know what that is and want to: it's a e-zine, by and for a bunch of book-readers who, mostly, are united by a past or present affection for the Redwall series by Brian Jacques. Contains fan-fiction, reviews (of well-known works and the more-obscure), art and the occasional bit of poetry. It lives

Comments

[zianchoy]

Woohoo! Another person randomly obsessing about CMS stuff :D

Here's the result of discussions with Kinsen and Philip:
For us to go all the way and make our own CMS, we'd need more webdevs. We can't possibly do this on our own.

Now, I'm not sure we even need a CMS despite what Philip thinks.

It sounds like what you're proposing is effectively using the wiki as the place to post the articles and edits. Except that no wiki on earth comes close to Word in terms of handling track/review and comments.
In addition, we'd have to keep running between your new system and the forums.

On the other hand, you didn't realy explain why you think we need a CMS so I'd like to hear the reasons. *waits* :D

P.S. I actually said you could do website articles a very long time ago back on the T F Staff Backup forums but it's OK. When in doubt, ask me!

[zianchoy]

Oh, and as for Philip's idea that CMS = no more encoders .... that's garbage. CMS can't pick meaningful tags. :D

[grimreaperkitty]

I wouldn't sub wiki for Word -- the wiki'd hold uploads of new versions of Word documents

[grimreaperkitty]

Well, NYT has a CMS, but they're huge. Still seems their stuff's got more human work in it than automated, though. Anyway! In short: I agree with you.