5. Radiant CMS
“Radiant is a no-fluff, open source
content management system
designed for small teams.”
John W. Long Sean Cribbs Jim Gay
@johnwlong @seancribbs @saturnflyer
6.
7. Rails 2.3.11
February 2011
...please don’t hold it against them. Rails 3 is next
(promise)
16. Extensions
• “Radiant fulfills an 80% window of need.
Extensions fill out the remaining 20%.”
• Example “needs”:
• Integration with some back-end data service
• Management of a complex data structure that doesn’t fit into
the Radiant page-layout-snippet structure (or fits poorly)
• Receiving and processing input from the website visitor through
forms or other means
• Complex manipulation of content information that would be
impossible or too cumbersome using Radius
18. Go-To Extensions
• Filesystem Resources
• Page Factory & Page Parts
• Navigation Tags (markup) & Tags (taxonomy)
• Reorder Children
• Vapor
• WYM Editor - “What You Mean Editor”
• Mailer extension
• “My Own”
19. When NOT to
Use Radiant CMS
• You want Rails 3.
• You’re looking for a “portal”
experience
• You want “1-click” install symplicity
• Need integration into existing app
• Other Peoples’ Extensions
20. When TO
Use Radiant CMS
• You want to write all of your own
markup.
• You want 1-N parts of a page.
• Want an admin interface your client
can understand.
• Want a robust extension interface,
build with Ruby, in Rails, using best
