I'm creating Yet Another Web-CMS (really as a learning experience). I've rewritten it five times now, and I'm pretty happy with how I'm doing right now. I think I have a pretty standard set-up for it, but it's by no means complete (read: I don't want to code modules until this weekend). I'm just wondering what you could suggest (backend functionality only) to add to this.
The project is online at http://z0.ca/~zallus/current/ . The server is a 120MHz box running Slack 9.0, so don't assume it's my coding causing the latency.
CMS Design Ideas
Moderator: General Moderators
It is hard to make suggestions since you didn't tell us about the backend architecture.
One thing that is always cool and usefull in a CMS is group permissions.
You may want to have an editorial process to allow some content to have to be approved by members of a certain group.
Also, you might want to think twice about calling your project "parrot". That is a pretty major project already:
http://www.parrotcode.org/
-Jackson
One thing that is always cool and usefull in a CMS is group permissions.
You may want to have an editorial process to allow some content to have to be approved by members of a certain group.
Also, you might want to think twice about calling your project "parrot". That is a pretty major project already:
http://www.parrotcode.org/
-Jackson