Why post 'pages',to 'pages#create' and why not post 'pages/new',to 'pages#create'

Hiya there! Rails is a very opinionated MVC Framework and it follows CoC (convention over configuration) and DRY very well. As in every MVC framework, Routes pretty much routes the request to the controller. And the controller in turn read the request and gets the appropriate information from the model and sends it to the view to render. To check all the routes , you can just simply type rails routes in your terminal.

Now, In Rails, a single controller class might contain eight actions(as per convention): new , show, create, index, edit, update, destroy, delete. And these actions have their own views and routes. So every request for index gets routed to "pages#index" ( which most of the times is the root route). One thing to notice here is that its a GET request , right? Similarly, request pages#new is a GET request and will be available as new_pages_path, which will route the user to a some kinda form, right? So when the current_user will fill out this form, he'll get routed to pages#create controller 'coz create action processes the user's request , which will be POST request. And is available as /pages or pages_path just like our index action.

I hope it helped!

~ Ari