Comparing version 11 and version 10
I'd like to see this turn into a compendium of information about Radiant "features". Including those features that have been implemented, those that have been partially implemented and those that are just ideas. *Extension Authors* -- Rather than simply listing your extension here try to think of the broader "feature" that your extension provides. (Perhaps it's multiple features.) For each feature your extension implements, create a wiki page or add a link to information about your extension. There may be multiple extensions that implement a single feature, and we'd like to be able to browse-by-feature. *New to Radiant?* -- Think Radiant should be able to do something but you don't know how to make it do that something? Look at the list for features that you think might help you implement your something. Add your 2 cents about how you would use (or even implement) a particular feature. *The goals of this page are:* # To provide a list of ideas for extensions for Extension developers # To provide links to pages that discuss a particular feature in greater detail and offer links to existing implementations of that feature # To provide a set of ideas for the Core Team to consider (both in supporting them directly via changes to the core, and in supporting Extension authors with appropriate hooks and API) To help decide whether something should be part of the core or should be provided as an extension. h2. Page Types * File Not Found * ... h2. Page Editors * TinyMce * FckEditor * Textile * Maruku * Kupu * ... h2. Per-Page Extensions * *Page Attachments* -- Ability to "attach" images on a per-page basis * *[[Extension Idea - Page Attributes|Page Attributes]]* -- Page attributes are attributes you attach to a given page to define additional data * *Commentable Page* -- If a certain page were "commentable" public website users could add comment to it. (like to a blog post). What might the admin interface to this look like? How would you like to be able to define which pages are commentable? * *Page Edit Conflicts* -- How to resolve conflicts when 2 people edit the same page at the same time. * *Calendar Page* -- a simple admin interface for adding calendar events and then a set of radius tags to be able to allow a page to display a calendar * *[[Extension Idea - Flickr Tags|Flickr Tags]]* -- a set of radius tags to display all of the photosets for a specific user and a set of radius tags for the pictures of each photoset. * ... h2. User Extensions * *User Roles* -- Content editor, publisher, etc * User Workflow * *Group-based Page Permissions* -- The concept is simple. Add the ability to add users to a group. When a user for a certain group creates a page, that page is then editable by users only in that group. Maybe give the page owner the option of locking the page from being edited by others in their group. But this would only be valuable in a situation where your content admins weren't Administrators or Developers, but just content publishers. h2. Application Extensions * *Asset Manager* -- A place to manage images and other uploaded documents. * *Page Versioning* -- History and diffs. * *[[Extension Idea - Automated Publishing|Automated Publishing]]* -- By adding effective and expiration date fields to pages it would be easy to automate the release and expiration of content. Pages falling outside of the publication window would not be displayed. This differs from "How To Write Time-sensitive or Expiring Content":http://radiantcms.org/blog/archives/2006/11/24/how-to-write-time-sensitive-or-expiring-content/ in some significant ways. * *Site Editioning* -- Beyond simply versioning page edits, the idea of Editions is that when you want to start adding a new content to your site, you mark the entire site as "current edition", and then create a new edition (with some descriptive title). Then all the work you do in creating and editing new pages applies to this new edition. (which can you preview at some URL, but isn't live yet) You should always be able to go back and make edits to the currently live edition while a new edition is under construction. When you are ready, you make this new edition the 'live' edition, and the current edition remains available (to the admin only) for historical purposes. * *Smart Status Tab* -- Tab in the admin area, which let's you display a list of pages based on their status (published, draft, reviewed, hidden) and has check boxes to quickly switch their status. Could have a drop down box on the top stating: Display pages with status:. * *Podcasting* -- Create different podcasts and upload different episodes to each podcasts which can then be served as a feed. * *"Partial Caching":http://www.ruby-forum.com/topic/138391#new* -- Utilize a hybrid of caching and on-the-fly dynamic content. * *OpenID* sign-in * ... h2. API * *View Modularization* -- Ability when writing an extension to override only part of a particular piece of the admin interface, instead of having to override (and duplicate the code of) a whole view. (Also known as the "Facet branch":http://dev.radiantcms.org/radiant/browser/branches/facets/radiant/lib/radiant/admin_ui.rb) * *Page Editors* -- Ability to design an extension following the model of a "Page Editor". Where your extension provides an alternative and/or enhanced page editing interface. * *Page Editor Tabs* -- As an extension author, I'd like to be able to define my per-page extension in a single view, and then tell Radiant to include the contents of that view for all pages edits as an extra tab (next to the page parts tabs). * *Blog API Support* -- Enable support for "Metaweblog API":en.wikipedia.org/wiki/MetaWeblog or Blogger API to be able to use third party and client tools to modify content. This might be part of a more holistic 'blog behavior' that integrates the blog tags extension and some of the other concepts floating around. IMO: having better blog behavior for portions of radiant sites is such a common use case, it is clear it should be integrated into core or consolidated into a supported extension.
