# Roadmap? **URL:** \ **Category:** Radiant CMS\ **Created:** [August 29, 2006, 8:48pm UTC](https://www.ruby-forum.com/t/roadmap/66853 "2006-08-29T20:48:18Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [August 29, 2006, 8:48pm UTC](https://www.ruby-forum.com/t/roadmap/66853/1 "2006-08-29T20:48:18Z")
I’m putting together a presentation on Radiant for Denver’s local ruby/rails user group, and I’d like to know if there is a more current feature roadmap than the one posted a few months ago. If anyone knows it would be greatly appreciated ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [August 29, 2006, 9:14pm UTC](https://www.ruby-forum.com/t/roadmap/66853/2 "2006-08-29T21:14:24Z")
Nathan W. wrote: > I’m putting together a presentation on Radiant for Denver’s local > ruby/rails user group, and I’d like to know if there is a more current > feature roadmap than the one posted a few months ago. The one posted a few months ago is still current, with the following exceptions: 1. I’m leaning away from implementing a fine-grained permissions system. Mainly I don’t think it is very consistent with Radiant’s focus to be a CMS for small teams. 2. I have recently begun to question whether version control is needed or not. I can see the benefits, but am not sure that the complexity is worth it. The roadmap is only a tentative declaration of where this project is headed. I’m learning things as I go along and adjusting accordingly. You might also have a look the slides from my presentation to the Chicago Area Ruby Group: [http://radiantcms.org/blog/2006/07/07/slides-from-chirb/](http://radiantcms.org/blog/2006/07/07/slides-from-chirb/) There’s a section at the end which outlines how I would present Radiant’s future. – John L. [http://wiseheartdesign.com](http://wiseheartdesign.com) ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [August 29, 2006, 9:18pm UTC](https://www.ruby-forum.com/t/roadmap/66853/3 "2006-08-29T21:18:25Z")
On 29/08/06, John W. Long [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > 1. I’m leaning away from implementing a fine-grained permissions > system. Mainly I don’t think it is very consistent with Radiant’s > focus to be a CMS for small teams. I agree > 1. I have recently begun to question whether version control is needed > or not. I can see the benefits, but am not sure that the complexity > is worth it. I think Version Control can be done in a simple way - [www.infogami.com](http://www.infogami.com) has a nice implementation for example. ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [August 29, 2006, 9:42pm UTC](https://www.ruby-forum.com/t/roadmap/66853/4 "2006-08-29T21:42:30Z")
Dave C. wrote: > I think Version Control can be done in a simple way - [www.infogami.com](http://www.infogami.com) > has a nice implementation for example. Even the simplest way adds complexity. I haven’t ruled it out (infact I have a nice implementation in mind if it is implemented), but I’m not sure it’s worth it (at this point). – John L. [http://wiseheartdesign.com](http://wiseheartdesign.com) ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [August 29, 2006, 9:58pm UTC](https://www.ruby-forum.com/t/roadmap/66853/5 "2006-08-29T21:58:33Z")
John, Thanks for the link and for the roadmap … nothing better than getting it straight from the horse’s mouth, so to speak. ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [August 30, 2006, 1:27am UTC](https://www.ruby-forum.com/t/roadmap/66853/6 "2006-08-30T01:27:04Z")
On 29/08/06, John W. Long [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Even the simplest way adds complexity. I haven’t ruled it out (infact I > have a nice implementation in mind if it is implemented), but I’m not > sure it’s worth it (at this point). Just my 2c but I think version control in a CMS for [small] teams is essential 🙂 ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [August 30, 2006, 5:35pm UTC](https://www.ruby-forum.com/t/roadmap/66853/7 "2006-08-30T17:35:27Z")
My 2c opinion: 1. Search. Haven’t tried the plugin/behavior but I believe this _really_ should be there out of the box. 2. Tagging. I know we can patch it but the last patch does not go without a hitch against the latest release. It would be really nice to have that out of the box. 3. ACL. I can see how this can be too much for the small teams target. Maybe this needs to be implemented by a plugin/patch combo? 4. Versioning. I can see small teams using this although I have build CMSs with verisoning to have users _never_ use it in the end so I can’t really push for it. Nice to have, though. Just my lowly priced opinion. AEM ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [August 30, 2006, 9:28am UTC](https://www.ruby-forum.com/t/roadmap/66853/8 "2006-08-30T09:28:16Z")
Mi opinion is: 1. permission system: essential is to give a customer the ability to update only part of the web site (in principol inherit page editing permission, which could be set for each page) in addition to not being able to delete/edit snippets/layouts etc. (N.B. This feature requests comes from a need in the field, from real usage business cases). 2. vcs: may be useful, less urgent than point 1) above; costs/benefits analysis is left to John and the other contributors to the code. –M ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [August 30, 2006, 5:49pm UTC](https://www.ruby-forum.com/t/roadmap/66853/9 "2006-08-30T17:49:29Z")
Adrian M. wrote: > 1. Search. Haven’t tried the plugin/behavior but I believe this _really_ > should be there out of the box. It’s coming, but harder than it looks. Alex Horn is doing a great job on the plugin. > 1. Tagging. I know we can patch it but the last patch does not go without a > hitch against the latest release. It would be really nice to have that out > of the box. Something like this is on the Roadmap for blogging. > 1. ACL. I can see how this can be too much for the small teams target. > Maybe > this needs to be implemented by a plugin/patch combo? I’m in favor of this. And will probably build whatever hooks in that are necessary for a plugin to implement it’s own ACL. > 1. Versioning. I can see small teams using this although I have build CMSs > with verisoning to have users _never_ use it in the end so I can’t really > push for it. Nice to have, though. Agreed. – John L. [http://wiseheartdesign.com](http://wiseheartdesign.com) ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [August 30, 2006, 7:15pm UTC](https://www.ruby-forum.com/t/roadmap/66853/10 "2006-08-30T19:15:44Z")
> Adrian M. wrote: > > > 1. Search. Haven’t tried the plugin/behavior but I believe this _really_ > > should be there out of the box. > > It’s coming, but harder than it looks. Alex Horn is doing a great job on > the plugin. The plugin is available for developers. The official version is not going to be released until the new behavior architecture design has been finalized (see Radiant-Core List). Beta\* (Search Behavior Plugin): [http://dev.radiantcms.org/radiant/browser/trunk/plugins/search](http://dev.radiantcms.org/radiant/browser/trunk/plugins/search) Please note that this component is still a _beta_ version. Needless to say, please report any bugs or any other quirks you find. Contrary to the README, you need the “bleeding edge” version of Acts as Ferret (/trunk r84 or higher). Otherwise the README should be fairly accurate with the installation instructions. Alex ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [August 31, 2006, 2:20am UTC](https://www.ruby-forum.com/t/roadmap/66853/11 "2006-08-31T02:20:39Z")
Alex, I will give it a shot between tonight and tomorrow night and see if I can help in any way. I have been using Ferret in another project (straight Rails) and I really like it. The only blemish is that I get random segfaults but that should be fixed soon (according to the ferret dev). Sincerely, Adrian M. ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [August 31, 2006, 2:18am UTC](https://www.ruby-forum.com/t/roadmap/66853/12 "2006-08-31T02:18:39Z")
On 8/30/06, John W. Long [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Adrian M. wrote: > > > 1. Search. Haven’t tried the plugin/behavior but I believe this _really_ > > should be there out of the box. > > It’s coming, but harder than it looks. Alex Horn is doing a great job on > the plugin. I will try that plugin. > 1. Tagging. I know we can patch it but the last patch does not go without > a > > > hitch against the latest release. It would be really nice to have that > > out > > of the box. > > Something like this is on the Roadmap for blogging. The patch is OK. I have made changes to support multiple-worded tags but it is still a patch. Don’t know how bad it’s going to get once the new version rolls out. I can share what I have if it helps someone. > 1. ACL. I can see how this can be too much for the small teams target. > > > Maybe > > this needs to be implemented by a plugin/patch combo? > > I’m in favor of this. And will probably build whatever hooks in that are > necessary for a plugin to implement it’s own ACL. I don’t have a need for that right now so I can commit helping there. > 1. Versioning. I can see small teams using this although I have build CMSs > > > with verisoning to have users _never_ use it in the end so I can’t > > really > > push for it. Nice to have, though. > > Agreed. Also how would you do it? At the parts level or page level? Probably at the page level since the alternative would be really complex to implement interface wise. – > John L. > [http://wiseheartdesign.com](http://wiseheartdesign.com) > > * * * > > Radiant mailing list > removed\_email\_address@domain.invalid > [http://lists.radiantcms.org/mailman/listinfo/radiant](http://lists.radiantcms.org/mailman/listinfo/radiant) Sincerely, ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [August 31, 2006, 12:13pm UTC](https://www.ruby-forum.com/t/roadmap/66853/13 "2006-08-31T12:13:25Z")
Rather than a javascript plug-in, could html access keys be used instead? Then you wouldn’t have to worry about testing the javascript or maintaining someone else’s code, and it would work whether javascript was enabled or not. (I know JS is required for radiant at the moment, but the long term goal would have the admin interface degrading gracefully?) Just a thought. Jake. ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [August 31, 2006, 10:43am UTC](https://www.ruby-forum.com/t/roadmap/66853/14 "2006-08-31T10:43:17Z")
Hotkeys for functions like saving a page would be nice. And relatively easy to add I think. [http://codefluency.com/articles/2006/08/22/hotkey-plugin/](http://codefluency.com/articles/2006/08/22/hotkey-plugin/) ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [September 4, 2006, 2:44pm UTC](https://www.ruby-forum.com/t/roadmap/66853/15 "2006-09-04T14:44:02Z")
Guido, Thanks for the info. I will try that and see if I fare better. Most of my segfaults seemt o come when searching using “~” or plain simple searches. I too hope it does get fixed soon. Sincerely, Adrian M. ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [September 4, 2006, 2:43pm UTC](https://www.ruby-forum.com/t/roadmap/66853/16 "2006-09-04T14:43:36Z")
On 8/31/06, Adrian M. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > I will give it a shot between tonight and tomorrow night and see if I can > help in any way. I have been using Ferret in another project (straight > Rails) and I really like it. The only blemish is that I get random segfaults > but that should be fixed soon (according to the ferret dev). I also got random ferret segfaults especially when adding / removing fields from a document that is already in the index. Try compiling it with -Os instead of -O2 and the segfaults reduce … let’s hope they update soon. – G. ---
**Author:** ![laserwhit](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@laserwhit](https://www.ruby-forum.com/u/laserwhit)\ **Post date:** [September 4, 2006, 2:44pm UTC](https://www.ruby-forum.com/t/roadmap/66853/17 "2006-09-04T14:44:02Z")
> Most of my segfaults seemt o come when searching > using “~” or plain simple searches. Have you reported the bug(s) to the developers ( [http://ferret.davebalmain.com](http://ferret.davebalmain.com) )?