# Understanding Radiant application layout

**URL:** <https://www.ruby-forum.com/t/understanding-radiant-application-layout/192420>\
**Category:** Radiant CMS\
**Created:** [July 30, 2010, 1:03am UTC](https://www.ruby-forum.com/t/understanding-radiant-application-layout/192420 "2010-07-30T01:03:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![weyus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/w/7ab992/32.png) [@weyus](https://www.ruby-forum.com/u/weyus)\
**Post date:** [July 30, 2010, 1:03am UTC](https://www.ruby-forum.com/t/understanding-radiant-application-layout/192420/1 "2010-07-30T01:03:34Z")

</div>

Generally speaking, since Radiant effectively runs out of  
RAILS\_ROOT/vendor/radiant, when, if ever, is it appropriate/correct to  
add assets to RAILS\_ROOT directly?

Does it ever make sense to install a controller in  
RAILS\_ROOT/app/controllers, or custom routes in  
RAILS\_ROOT/config/routes.rb, for example?

If so, when would that make sense?

It doesn’t even appear that Radiant adds these standard locations to the  
load path when Rails starts up.

Thanks,  
Wes