Here at Ubikorp we’ve used Radiant as the basis for a number of client projects who needed core CMS-like functionality. As anyone who’s played with it knows, Radiant is very barebones; this is intentional and a welcome change from most packages, which attempt to throw the kitchen sink of clutter at each and every problem. Fortunately, it’s easy to build on top of the basics by using a well thought-out extensions system — there are a large number of stock extensions available (and it’s also really easy to roll your own for custom app logic).
One of the more interesting extensions is the multi-site extension. To be honest, multi-site capability is something I really feel should be a core feature, but since it’s not, this approach works surprisingly well (at least until you start adding other extensions that would ideally be multi-site-aware). Radiant school headmaster Sean Cribbs wrote an initial version of the extension back in November, but it didn’t quite work for us on a particular project — we needed to be able to scope individual user-level access to particular sites. So we extended it, and thus the scoped multi-site extension was born.
Well, actually, it’s just a fork of the multi-site plugin. For now.
- scopes user level access to individual sites (admins and developers still have access to all sites)
- regular users can’t see, edit, or access other user sites that they don’t own
- optionally scopes layouts to sites
- snippets usable everywhere, but display and editing of snippets limited to admins/developers
Anyway, if you’re interested in seeing our changes you can check it out on github in my fork of Sean’s Radiant repo. Is this a candidate for integration into the existing extension, or should we spin it out as a separate extension? Let me know what you think.
UPDATED 6/24: The URL is out of date. See this blog post for more details and updates (the latest version requires Radiant 0.6.7 or later).