Erik, Radiant may not necessarily be a good fit for your needs. Radiant is very focused on textual content that is essentially static (i.e. not customized-per-visitor) and has a very simple administration scheme. Take into consideration whether your content editors are familiar with HTML, CSS, etc, as Radiant exposes this almost directly to the editor. Also consider the size of the editing team and whether they will often step on each others' toes when working, as Radiant has no versioning yet (optimistic locking prevents basic overwrites, but doesn't save older versions).
If you're still considering Radiant, let's look at your needs. ACL - There are two "groups/permissions/roles" in Radiant, "developer" and "admin". Only admins can view/edit which extensions are installed and active. Your extension controllers can easily specify who can access what actions and who can see what tabs. Users may also be "plain" users, or rather, have neither of the above roles. Extensions - Please describe in more detail what you mean by portlets. When I read that word, I think of content "components" that can be selected and arranged in a page by the visitor. If this is what you're looking for, Radiant is NOT portal software, and I suggest you look at other available options. If you just need to integrate with some proprietary data services, Radiant extensions can handle the job, but won't deliver the "portlet" idea necessarily. You cannot have multiple versions of an extension installed at the same time. Why would you want this? Please describe what you mean by "Maintenance", "Disabled", etc. Does this refer to "portlets"? i18n - There are already some efforts at internationalizing Radiant. Search the mailing list for discussions of the "Language Redirect" extension and other strategies for serving content in multiple languages. Regarding translating the administration interface, there is some work done in the "jargon" branch that you may find useful. Web Service - You could easily create or consume a SOAP API using ActionWebService. However, the design and implementation of this is out of my scope of knowledge. Version 1.0 - We have a rough schedule, yes. However, Radiant is already successfully being used on many sites (see the RadiantUsers wiki page), and the core is relatively stable. There is no stigma to using it pre-1.0. And honestly, I don't see 1.0 arriving in less than a year. We have many more hurdles to overcome before then. If you want 1.0 to arrive faster, I suggest you consider contributing well-tested improvements to the core. While the core team contributes their own fixes and enhancements, much of the code has also come from the community. We cannot predict the architectural impact of 1.0 because it's not even on the radar. I can assure you there will be many changes between now and then, but we will likely have near-complete backward compatibility or at least a sensible upgrade path. Hope this helps! Sean Cribbs (Radiant core team) Erik Nijkamp wrote: > Hello Developers, > > We are planning to use Radiant as groundwork for a commercial project > and decided to ditch j2ee + jsr portlets in favor of rails + radiant. > > Would you please inform us about the current status of: > > * ACL > - User/Group/Role management > - Authentication > - Assigning roles to extensions > > * Extensions > - 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", ... > > * i18n > - Localized content > - Detecting the currently used language (browser) > > * Web-Services > - Replacing the rails model with a web-service > - e.g. extension -> controller -> soap/rest web-service -> backend > > * Version 1.0 > - Do you have a schedule? > - Architectural impact? > > Thanks for your time and help! > > Best regards > Erik Nijkamp > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
