On Dec 3, 2007, at 11:08 AM, Erik Nijkamp wrote:
Would you please inform us about the current status of:
Radiant is really focused on a much smaller domain than what you are
describing below. It’s a content management system designed for small
teams. Extensions are intended to give you that extra 20% of what
Radiant doesn’t provide out of the box, but if Radiant doesn’t do 80%
of what you want already it’s probably not a good fit for your
project. With that in mind I’ll do my best to answer your questions
about the features below.
- User/Group/Role management
- Assigning roles to extensions
Right now the ACL is very primitive and will probably stay that way.
I’m open to suggestions about a way to make it pluggable so that
extensions can swap in their own variation, but it’s probably pretty
difficult to do that right now.
It shouldn’t be that hard to create new roles for the current system.
I’m not sure if anyone has ever done it, but you should be able to add
a question mark method to the User model for the particular role that
you want to use. For example. To add an editor role:
The easiest way to do this is just use Rails’ support for boolean
attributes in a migration:
add_column “user”, “editor”, :boolean, :default => false, :null =>
Then in your views you can use:
- Portlets: Using extensions as “Portlet” replacement e.g. associating
extensions with roles
- Versioning: Using different versions of an extension at the time
- State: “Maintainence”, “Disabled”, …
Associating an extension with a role is up to the extension author.
You cannot use multiple versions of an extension at the same time.
There is no support for putting the site into a maintenance or
- Localized content
- Detecting the currently used language (browser)
If you need a localized admin interface, the jargon branch might be
worth looking into. Otherwise the standard Radiant solution for
localized content is the language_redirect extension.
- Replacing the rails model with a web-service
- e.g. extension -> controller -> soap/rest web-service -> backend
I’m really not sure what you mean by this.
Nothing definite. Right now we are trying to get 0.6.5 out the door.
Here’s the tentative roadmap that the core developers are presently
working off of:
0.6.5 - Rspec Refactoring
- Support for RSpec in extensions (?)
0.6.6 - Restful Refactoring
0.6.7 - Updated Extension System
- additional support for customizing the UI
0.7 - Full Featured Blogging Engine
- commenting system for every page
- additional helps for RSS?
- tagging for pages
- import scripts for other major blogging engines?
- support for MarsEdit and other APIs?
0.8 - Assets and Attachments
0.9 - Drag and Drop
- drag and drop sortable page view
- <r:next /> and <r:previous /> tags for siblings
1.0 rc1 - Workflow: Version Control and Permissions
- simple version control
- additional roles: publisher, ?writer?, ?editor?
- true multi-lingual support?
We often make changes that break existing extensions. This is
primarily because monkey patching is the current method for making
core changes to the way Radiant works. If your extension requires that
you fiddle with Radiant internals then it is naturally more brittle
and may break when we update the code base. I’m not sure that there is
much that we can do to fix this problem. We are working to standardize
ways of extending radiant with the extension system, but that is a
work in progress.