CMS Requirements
I mentioned just a little while ago that "I really need to post my Feature/Function Requirements for what a CMS should be able to do." So, here it is, my list of requirements for a CMS:
- Editing any of the templates and pages should be able to be performed through a web interface that supports plain/text HTML editing and a WYSIWYG editor of some sort.
- In addition to the web interface, one should be able to directly edit any templates or pages through the editor of his or her choice. Do not dictate to users.
- "Work flow," "revision control," "hordes of metadata," — these things are all nice, but 95% of the activity using a CMS is for the following:
- Creating a new static page.
- Posting a news story, highlight, event listing or other small piece of new text to an existing page
- Making a small change to a "themed template" that automatically changes an entire umbrella site e.g. changing a banner logo in one place to change it everywhere.
- Entire system automatically does validation checks and tries to lure users into using X?HTML and CSS positioning.
- Clean URLs.
- RSS and Atom support right out of the box.
- Integrates with a directory server for accounts, identity, and grouping information.
- Uses HTTP codes correctly, especially:
- This space reserved for more requirements as needed.
Post a comment