There is a function "resources" in the class "SingletonResource" that
provides 7 routes for an indicated resource, like this:
GET /photos
GET /photos/:id
etc.

Also, there are some gems(as "friendly_id") that give a possibility to
store an arbitrary string in :id parameter, what helps to have frendlier
links like /photos/big-ben.

But for several reasons this approach makes me feel odd. The fact that in
the :id is stored, for example, a name of a model is not quite elegant. And
also it leads to such code in controller:

@photo = Photo.find_by_name(params[:id])

Which can be hardy called beautiful. "params[:name]" should fit much
better. To avoid this, the gem mentioned above redefines the "find" method
in choosen model, but I do not like it too. It can easily provoke gem
conflicts, because there is a lot of gems that do it too. E.g., commonly a
gem which adds "soft delete" also redefines this method that makes
impossible to use them together or can break functionality somehow later.

So, my suggestion is to add a :param_name option to "resources" method so
we can have the behavior like this:

resources :photos, :param_name => 'name'

GET /photos/:name

Could it be useful if I add such feature? In addition, there is a whole
bunch of questions on stackoveflow with the same desire.