Replication and deployment are managed strictly by meta-data rather than by directory structures. This facilitates the deployment of a complete project without errors. There is automated control over live and development records, which minimizes the need for database mirroring. The system also supports user uploads of content from within a browser. One of the key features of StoryServer 3 is its ability to deliver personalized content.
Content varies depending on the client's operating system.
Collaborative filtering or any other third-party personalization engine, such as FireFly or NetPerceptions, can be used. Browser and user environment personalization are integrated into a single property-sheet panel that is accessible from the page template editor. StoryServer 3 supports native access to databases rather than ODBC connectivity for increased performance. StoryServer can be further customized via API calls. StoryServer 3 for Solaris is currently available, and a Windows NT version is due by the end of 1997.