Rails based DB, Google Maps user API, avoid layouts?

I'm hoping for a little design guidance here. I've got a Rails based DB application with lots of 'admin' screens written in the usual Rails ways including using a Rails layout.

But now I'm writing an 'end user' screen that is effectively some of the data represented on a full screen Google Maps map. It does want a few knobs and settings so I will want I18n support but apart from that it seems like there is nothing to be gained from a Rails layout, or in fact most Rails infrastructure beyond the routes - or is there?

Anyone already stumbled down this path and able to share some thoughts on how best to approach this? I've got a prototype working but still having nagging suspicions that my lack of experience in this arena means I might be missing some Rails goodness.