Syndication - versioning - workspaces
Since the addition of SVN for Ariadne templates, the request for data versioning and syndication has been popping up everywhere. The idea is to allow a site administrator to make changes to a site in a new workspace. Changes will be kept as a sort of 'overlay', allowing the rest of the site to be managed as usual. When the changes are reviewed and ready for publishing, the editor can apply all of the changes to a site at the touch of a button.
This system could also allow data syndication between different Ariadne installations. This would make it easier to have seperate environments for development, staging, etc - or even create a load-balanced cluster of Ariadnes to serve a major site in.
Extended image scripting and templating
Ariadne has integrated support for image resizing, based on Image Magick, but that has been limited to 'basic' image operations such as generating thumbnails or adding watermarks. Image Magick boasts lots and lots more functions that could be integrated. Unleashing this potential would lead to some very interesting image manipulation options.
Cross-browser inline editor
Ariadne boasts a nice WYSIWYG editor (actually, 2 of them) to edit and update the sites you build. One is a slightly modified version of TinyMCE, the other is an inline editor that works under Internet Explorer. Recent feature additions have made it a possibilty to rebuild this editor so it works cross-browser (Internet Explorer, Firefox, Safari and Google chrome). As far as website editing goes, inline WYSIWYG is one of the best options there is.
Rewrite the Ariadne installer, make it (a lot) more user friendly.
One of the main complaints we get about Ariadne is that the installation isn't very friendly. We totally agree, and are hoping to create an installation that a Regular Joe will be able do. The current installation method requires a lot of 'manual' work on the commandline. The whole installation procedure could be wrapped into a nice webbased installation package, which will appeal a whole lot more to new users.
Add dashboard-like functionality in the Ariadne backend.
Usually, sites built in Ariadne are managed using the inline editing environment. However, sometimes another way of managing and presenting data is better suited for specific roles. For instance, a system administrator would be a lot more interested in what kind of network traffic a given site is generating. This kind of information could be presented in a dashboard-like fashion, with different 'blocks' for different functions. A dashboard could be configured to suit the role of the user (sysadmin, story editor etc) or the goal of a site.
Automatic AJAX-driven sites.
Ariadne is based on templates. This means objects can have different views on them to display them in different ways. Usually a page already has a different template for the 'content' set up - if this can be linked to the menu of a size, it should be possible to automatically present a website built in Ariadne as an Ajax driven site.