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
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:
-
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 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/
There’s a section at the end which outlines how I would present
Radiant’s future.
–
John L.
http://wiseheartdesign.com
On 29/08/06, John W. Long [email protected] wrote:
- 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
- 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
has a nice implementation for example.
Dave C. wrote:
I think Version Control can be done in a simple way - 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
John,
Thanks for the link and for the roadmap … nothing better than
getting it straight from the horse’s mouth, so to speak.
On 29/08/06, John W. Long [email protected] 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 
My 2c opinion:
-
Search. Haven’t tried the plugin/behavior but I believe this really
should be there out of the box. -
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. -
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? -
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
Mi opinion is:
-
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). -
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
Adrian M. wrote:
- 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.
- 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.
- 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.
- 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
Adrian M. wrote:
- 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
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
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.
On 8/30/06, John W. Long [email protected] wrote:
Adrian M. wrote:
- 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.
- Tagging. I know we can patch it but the last patch does not go without
ahitch 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.
- 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.
- 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
Radiant mailing list
[email protected]
http://lists.radiantcms.org/mailman/listinfo/radiant
Sincerely,
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.
Hotkeys for functions like saving a page would be nice. And
relatively easy to add I think.
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.
On 8/31/06, Adrian M. [email protected] 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.
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 )?