Future development

Many plans and ideas exist for the future of Taesk, get to know some of them here. 

The future development is in no way fixed, most often it is driven by several factors - on one side there is the market demand and on the other side the project demands for restructuring. Usually this ends up in a mix that provides value for all parties.

The items mentioned here are some of the major areas that the (main) developers would like to see worked on in the future - In other words the following features are somewhere in the pipeline, when they are going to be implemented is unknown.

Better documentation A lot of documentation exists for Taesk CMS, however it is located in internal systems/documents at need to be "found", "cleaned" and finally published - this is a high prioity.

CMS Redesign It would be great to have the entire CMS interface redesigned into a more AJAX oriented interface. Check the image on the right which shows one possible concept for that development.

Content revision system
Currently Taesk only operates with one version of the content - the "actual" version. We would very much like to implement a content revision system, they would potentially enable various features such as: content-rollback, change-highlights, improved audit-trail.

Workflow
Based on a conten revision system it would be possible to implement a complete workflow system - this would have to be very very carefully implemented so that it would not add an extra layer of complexity for those administrators/setups where it would be not needed yet still be able to be used on some.
Also such a workflow should include a workflow editor enabling administrators to define individual workflows (potential down to each content set).

Finegrained content types
The content types could be broken up into smaller items, and then combined for each project (with a given default set of combinations available), this would make it much more easy to create new content types for a given installation - e.g. if you for some reason needed a content type with 1x flash, 1x image, 1, headline, and 1x bodytext.
This would make content managing even more flexable.

Details details
And much more ;-)
The internal document with proposed changes/improvements currently has around 1000 lines in it - some which never will be implemented, some which are obsolete, and some that are still very relevant - in short there is plenty of development work to do on Taesk still.