Radiant Development Site

Reporting Bugs or Requesting Features

The best way to report a bug or request a feature is to write the fix or enhancement and then send a pull request. If you’re not that familiar with git or the Radiant codebase, you can also file a ticket.

Documentation

Looking for documentation? Visit the documentation wiki.

Mailing List

The mailing list is a great place to ask questions about Radiant. Search the archives:

IRC

Having trouble using or installing Radiant? Want to share a success story? You can chat with members of the user and developer community in real time in the #radiantcms channel on irc.freenode.net. You’ll need an IRC Client. There’s a nice list of them over on the Ruby on Rails wiki.

Contributions

Tickets are fine, but patches are better. If you want to change something in Radiant or fix a bug you’ve run across, there’s no faster way to make it happen than to do it yourself. When developing your patch, keep in mind the Radiant Ethic.

1. Before you start:
   • Subscribe to the Radiant-Dev mailing list and discuss your proposed feature/patch there
2. Get Radiant ready for patching:
   • git clone git://github.com/radiant/radiant.git
   • Setup your environment in a way to be able to run the test suite
3. Make a test-driven change:
   • Add or change specifications that would prove that your change worked.
   • Make the change to the source
   • Verify that all existing specs still work as well as all the new ones you added by running rake
4. Share your well-tested change:
   • Send a pull-request or create a patch with your changes: git format-patch --stdout > my_properly_named_patch.diff
   • If you don’t send a pull-request, create a new ticket with [PATCH] as the first word in the summary and upload (not paste) your diff.
   • Announce your change on the Radiant-Dev mailing list.
   • Keep an eye on your patch in case there are any reservations raised before it can be applied.