Getting started part2!

rubyonrails-docs
1

Hi,

Im quite new to ruby on rails. I find the guide lines are good but they only take you so far. What I miss is a part 2 of the getting started blog, and if you think about it many of the other guidelines goes to much more more detail on individual topics.

What I would like to see and I am sure many others (google around for nested resource, routes etc) is an example that continues where the getting started blog finishes. This guide can for instance add full crud for nested models. In the blog example comments are only viewed within the posts view. The controller only has create and destroy actions. In many apps I have found you want more on the second and maybe even third level. For instance, Customers, Orders, Products, you would want index, show, new, create, edit, update and destroy actions on all levels yet you would want the resources nested. I know you shall not nest further than 2 levels. But then show how that is accomplished and yet keep a intelligent url structure. I think many newbies like myself would benefit enormously from being show such an example. Also when it comes to urls I think many selects either the fully RESTful way, and many apps work better UNRESTful. In the example mention you could show both ways. http://localhost:3000/customers/1/orders/42/products/97 and http://localhost:3000/foobar-inc/42/mars-bars.

One might think that one of the many books out their would cover this pretty common situation. But I have found surprisingly few, can’t think of any actually.

Naturally there are many ways to do these. There is nothing stopping an author from saying so in such a guideline.

I would right this myself if I new how to. But I am far from good enough at rails yet. However I am one of you contributors can do this in a blink of the eye. It would really benefit the whole community.

Just a suggestion!

BR

Nancy

2

Hi Nancy,

Expanding upon the Getting Started guide and building a fully-fledge application like you suggest is something that is better covered by a book like The Rails Tutorial (http://railstutorial.org) or my own book, Rails 3 in Action (Rails 4 in Action).

To cover absolutely everything you need to know when building a Rails application puts a huge “technical debt” on the guides team, as they will need to first make the content and then keep it relevant throughout time. The guides are supposed to be an initial overview of Rails to cater to the masses, rather than a very select few.

I would recommend reading a book written for Rails if you want to learn more about what Rails can do.