| |
Daniel asked me to put together a list of Content Management System (CMS) wishes that I would have for any system. I recently read that CMS will be a $7 billion industry next year. WOW. I guess that makes sense since so much information is created these days.
So here they are:
- Multiuser - allow multiple editors to submit content
- Simple - People don't understand web publishing, HTML or file structures. Most tools don't hide this very well. People do associate buttons and links on a page with other pages. Somehow, creating a link or a button on a page should create the target for it automatically
- No framework or server required - There are many open source CMSs out there, but most rely on an underlying framework to run. I want to download an installer, install it and go. Not download PHP, secure it properly, then try and get the CMS working. Radio is a great example of this.
- File Upload - The browser based upload functionality is garbage. No status, breaks often and you can't cancel an upload. Also, once the file is uploaded, a user needs to know how to create a link to it. I'd prefer a UI which has a file library that I can drag and drop a link from the library to the document I'm in and the link is created.
- Full text search - I neeed to find the content I enter. I have google configured to allow users to search my site. Something this simple is great, however, I had to create a button and search form to make it work. Joe & Jane user can't do this.
More later I have to go do some chores :)
1:59:19 PM 
In order to manage my increasing software development workload, I am building a requirements management tool. My goals are to:
- Make it simple
- Make it cheap
- Automate Document Generation for client review
- Track and Audit changes
- Manage Projects
Like any appliction, this tool needs to store information in some format. I have chosed to go with XML for obvious reasons. The .NET Object Serialization functions are great and make life simple, but they cause problems when the fields of the object change. As a result, I will need to create an XML format to store my requirements. I looked around the web for a while to see if anyone was defining a standard way to store software requirements, but my searches to find anything have failed. As a result I will creating a format and will be looking for developers to share their input. If you have any ideas, please share. I will post more soon.
1:49:16 PM
|
