Getting nice looking error messages isn't easy. It's easy to use the Rails default ("error_messages_for") but for the type of errors you'd ideally want you'll still have to do a little leg work. One nice part it that any form fields that are being output using the Rails form helpers will be wrapped in a div with the "fieldWithErrors" class. This makes adding a red border to problem fields extremely simple. Also, with the help of the recent post about multiple selects over on railscasts, I was able to add in my country/select fields in a very streamlined way. I'm using the same "address" partial for users and arcades at the moment as well, with that partial including the javascript in the header. Pretty slick just including a partial and having all the javascript just fall into place. For now adding a single arcade is working fine all around, although i'm a little concerned with how my nested resources are starting to become cluttered. Nested resources are just what they sound like. For instance if you wanted to get a users address, you might go to the url http://localhost:3000/users/:user_id/address/1. That's a very useful looking URL that you can find a lot from. The downside is that the controller/action this will hit is (by default) address_controller.show. This is the exact same controller/action that is hit when you go to http://localhost:3000/address/1 though! The only difference is that there will be a "user_id" variable passed in. After that though you might handle little things differently like the title, the edit link for that resource, and maybe even the entire page. Aparently you can make this resource go to another controller, like "user_address_controller" for example and not have to worry about this. I'm starting to think this is the way to go for a lot of this.