-
Notifications
You must be signed in to change notification settings - Fork 259
Wishlist
A place for simple ideas/wishlist items. Use Proposals if you have a more complex or detailed idea.
A quick list of ideas for features in future versions.
- Update the UI to allow for more modular expansion (It should be easier for devs to add new elements/menus)
- Treat Blocks like Pages (allow blocks to have paths and templates without needing to be manually embedded into pages)
- Allow Template Assets (css, js, images) to be managed via the CMS (with WebDav)
- Use Paperclip for file management (Must handle versioning of uploaded files that core attachments does)
- Database Backup & Restore
- File Caching – Allow publically accessable files to be written out to page cache (to be served by Web Server
- Use standard Authentication tools (We are using an implementation of Restful_Authentication)
- Create/build module for CKEditor to allow linking to pages
- Provide a UI to allow modules to be configured
It is possible to write portlets that are not safe to use with the page caching mechanism (i.e. personalization). You can place these portlets, but you have to manually remember to turn off the page caching. Should add a flag to portlets that can be used to mark them as ‘do not cache’. This portlet flag would allow the containing page to automatically turn off its caching behavior when it holds a portlet that is marked this way.
This would likely lead to less frustrating for developers trying to use portlets from other modules, where they don’t quite know the details of how they work.
- Setup/define locales
- Have one content element in different langs [en, fr, de, it] …
- Easy routing like /en/home
- Have translated routes
Basically a hit list of code changes to make:
- Remove the need for a separate group_type table?
- Improve the DSL for creating new instances of groups
# Something like:
group = Group.create!(:name=>"Marketing", :can_view=>:all) # or :noneWordPress has a plugin for allowing staff to login as a particular user (http://wordpress.org/extend/plugins/skeleton-key/). This concept might be useful to allow a web developer who is supporting multiple client installations. This might be a central authentication system which would allow the developer to log in with a single user account, rather than having to explicitly create multiple accounts in each CMS installation.
A CMS might usefully provide some automatic way to support integration with URL shorteners. See issues outlined here: http://joshua.schachter.org/2009/04/on-url-shorteners.html.%3C/p