| Klixo2 CMS Development Starts |  |
Klixo2 CMS Development Starts
I wrote about the redevelopment of the Klixo content management system a few weeks ago, and we've already made a start. It isn't quite K2 (Klixo Content Management System V2) as the web services are still using the current Klixo database. The database shall be redesigned to more easily incorporate many of the features we want to add and simultaneously make the developments we've already added to Klixo1 more generic. However, these web services have been written in .NET using Visual Studio and C# with a good framework already developed for the database and generic web services that we shall use in K2.
Currently, the Klixo CMS has a single interface which our clients access to change or update their website. The new API provides services that can be consumed by our clients' applications. For some of our customers, the standard Klixo interface won't be optimal for data input. For example, one of our customers, Tramping Tracks provides a website that has comprehensive information on walks throughout New Zealand. Because of the extensive information they provide for each page we determined it would be significantly faster to write a custom interface for them. As a consequence, the Klixo API arose.
This API adds another string to Klixo's bow because it allows for as much customisation as required. Of course the current system is dynamic, responding appropriately as the website demands, but in highly complex content entry such as this, there are significant gains to be made. A further benefit to our customers is that they can outsource the interface development if they so desire. Another benefit is that with a custom interface the content may be updated automatically. Imagine a company (such as I was talking to the other day) that sells books and gets many more books each week. If the book data can be extracted in any way, this API and a custom interface would allow all their books to be automatically updated on their website.
 |
