24. <a href="<r:url />"><r:title /></a> and
<a href="<r:url />" class="foo">To another page</a>
could be written as
<r:link /> and
<r:link class="foo">To another page</r:link>
26. <ul><r:children:each><r:unless_url matches="foo">
...
</r:unless_url></r:children:each></ul>
could be written as
<ul><r:children:each:unless_url matches="foo">
...
</r:children:each:unless_url></ul>
27. <r:parent>
<r:assets:each limit="1">
<r:link />
</r:assets:each>
</r:parent>
could be written as
<r:parent:assets:first:link />
31. If you do need to
write an extension
• Use shared_layouts extension railsyou don’t
have to use (and maintain) a
so
layout
• Freeze radiant (so that you can see)what
you are doing
• Let your backend controllerfor free from
Admin::ResourceController
inherit
CRUD actions and flash messages
• Upload to github to receive free updates
33. Radiant extensions can
now be gems!
• Gems have a nice dependency system
• One ‘gem up to date bring several Radiant
instances
update’ can
34. Radiant 0.9 coming up!
• Brand new interface with reworked tabs
• Internationalisation (for the backend)
• On Rails 2.3.5, working on Rails 3
35. Radiant extensions may
soon be engines!
• Spree (e-commerce platform) hasofan
extension system based on that Radiant
• Radiant andeffort tocommunities are looking
into a joint
Spree
bring extensions to the
next level (engines or something like it)
36. some Github profiles
to keep an eye on
• github.com/radiant
• github.com/saturnflyer
• github.com/kbingman
• github.com/spanner
• github.com/jgarber
• github.com/johnmuhl