autopublish Powered Websites and Web Applications

Our autopublish content management system provides a foundation for not only providing a stand-alone interface for editing of content, but provides an API for integrating content management functionality inside an existing application.  This allows a great deal of customisation as to how the system works from the end-user's point of view.  For example, we can easily create a task-based environment where website users are guided through a series of steps to update content.  By customising the interface, we can focus users on the tasks they wish to perform, rather than have them learn about a 'Content Management System'.  Advanced users may still edit content using the standard interface if they wish.

We believe this is a unique approach to content management, and produces a greatly reduced learning curve.  By allowing this type of integration, it is possible to cater for any unique requirements of an application.  It also allows other elements to be combined together in the same application. For example in a portal environment, autopublish can provide editing facilities for some content types, while a third-party forum application can be integrated elsewhere in the same page.  This obviates the need to customise autopublish, instead allowing it to be used in an application to the client's specification.

This flexibility is achieved by a combination of Java APIs and custom JSP Tag-libraries.  While development of applications is geared towards the Java language, we have libraries written in PHP and Perl to allow access to autopublish content.

Java by its nature is not restricted to a single operating system, and autopublish is designed to allow most popular databases to be used as the backend store.

autopublish functionality can be restricted to specific areas of an application.  For example if there is an existing database, autopublish can provide the front-end forms to display and edit that content, while relying on the existing system for storage.

Managing content is as much about re-using and re-purposing existing content and resources as it is about creating new ones.  It is important that our systems can interact with any existing systems, not just in terms of the user interface, but in the back-end as well.  A particular case in point is User Authentication.  autopublish maintains its own comprehensive user management system, but is able to connect to any LDAP-compatible data-store to retrieve user details as well.  This extends to the use of Microsoft Active Directory, and any other system which presents a similar interface.