Overall Satisfaction with Cascade Server
We use Cascade Server as a content management tool for managing the websites for the Purdue University College of Science. There are several departments within this reach (Math, Stats, Biology, Physics, Chemistry, Earth & Atmospheric Sciences, Computer Sc.), plus the College of Science itself. We manage their websites according to their requests of new information, new design of their websites, or delete old information. Furthermore, we also look for broken links and errors by making use of another software called InSite, and try to fix them. Mostly, we manipulate the individual web pages to include new information by using their HTML scripts. There are only around 5-7 of use in charge of using this system for the College of Science, three of them being full-time, and the others including me being part-time since we are students.
- Content addition including pictures, text, video
- Template creation common across various pages, thereby greatly reducing time
- Making header and footer blocks
- Managing the left and right panes
- Individual pages need to load faster
- Publish message sometimes takes a long time to be pushed across all machines, perhaps increase the speed of the publish message
- There is a problem with the hierarchy of the publish message pages, in other words, we have to publish the individual pages before publishing the page that calls them. This is a little confusing. Perhaps this could be addressed.
This is my first foray into web-content management, and I am using it simply because my supervisor required me to.
Because Cascade Server is easy to use and understand. Also managing websites is not that difficult.