= Feature requests = This is a usergenerated list of features we would like to see in future Escenic versions. The features are separated into the main components of the Escenic system. Feel free to add whatever you like to this page. == Escenic Content Studio == * The user should be able to store his own article templates. A way to implement this is to let the user fill out an article, and the press 'save as template'. Then he could open a new article based on the template from the file->new->article from template->my template menu. (Added by Jakob) * Dynamic height on elementGroup's. If you have a gridLayout with a lot of elementGroups containing a lot of gridElements, then the section view in Studio will be very long. It would be a great idea if all the elementGroups had the height of n + 1 articles. Where n is the number of articles places in an elementGroup. This would reduce the length of a section page in studio a lot. * Group membership-based access rights on certain article elements. For instance, a reporter might just see the article title, preamble and text-body, but an editor should be able to add extra features to the same article. == Escenic Web Studio == * document on plugin integration == Escenic Administrators Web Interface == * automatic plugin installation web interface == Core == * [native pagination support|nativePagination], not pagination on collection object * Revision support for all articles, and maybe sections. The number of revisions must be configurable. * Improved handling of [wiki:Inline inline] objects == Plugins == === Blog Plug-in === What is missing from our Forum plug-in to make it work like a blog? __Trygve ads what springs to mind in the first place:__ * Support for XML-RPC: MetaWeblog API [http://www.xmlrpc.com/metaWeblogApi] / Blogger API so external clients like w.bloggar [http://wbloggar.com/] can be used. Would be very nice in ECE all over. No need for Studio anymore / or as a light weight replacement of Studio.\\ * Support for [http://en.wikipedia.org/wiki/Trackbacks Trackbacks] * Support for [http://en.wikipedia.org/wiki/Pingback Pingbacks] * Support for Syndication (RSS, ATOM og OPML feeds) * Support for Permalinks (Permalinks can look like the "read more" (access to article level (deep linking)) in ECE link, but has more functionality such as support for versioning of content ++ * Main articles must be categorized and not structured in sections. * Support for user profiles so that a form has an 'owner' so that only I can write entries in my own blog, though anyone may comment my entries --[wiki:PeopleMogsie Mogsie] * Make a nice clean CSS-based, semantic template set which allows skinning via CSS or DOM scripting. --[wiki:PeopleMogsie Mogsie] * There are some suggestions here, although not very blog-related: [http://www.escenic.com/forum/plug-ins/article1374.ece] ([wiki:ChristianL ChristianL]) === Tagging Plug-in === Please elaborate --[Seberget] I would think it has to do with del.icio.us and similar tagging. Either that we have a tagging engine, or that we can ask tagging servers which tags are popular for a specific page, or simply make it easier for people to tag our content. --[wiki:Mogsie Mogsie] === Colud generation plugin === ??? === Wiki Plug-in === A plug-in that supports wiki syntax in its content. * Each Wiki page would be a separate article, the title would be the name of the page (you would not be allowed to change the title -- enforce this via a TransactionFilter or something) * The title (or the WikiName of a page) would be checked for uniqueness when saving (somehow), and the field would be indexed using the ArticleFieldIndexer. * Wiki names would be made hot-linkable by searching the articlefieldindex which is pretty fast. * A section would be a wiki namespace. The home page of the section would just find the Front Page or Main Page of that section. * Inter-wiki linking could be achieved by using for example :-) --[wiki:PeopleMogsie mogsie] * Use a wiki-neutral source format with a decorator or similar to transform to / from wiki-syntax and xhtml (but still use Wiki syntax in the editor!) --[wiki:Seberget]