To just get a functional website, the backend frameworks are just way more productive than having to mess around with a frontend/backend solution, so rails, django, elixir, etc all excel, are cohesive, have tons of support and libraries to cover different needs, etc, and generally not too difficult to learn.
Though personally I found rails' magical 'convention over config' to be an abysmal hindrance to learning how things actually work - for example many examples show code, without showing where in the filesystem the code should go - you're expected to know the convention already, and things like i18n translation 'paths' can be confusing, and fail silently.
To just get a functional website, the backend frameworks are just way more productive than having to mess around with a frontend/backend solution, so rails, django, elixir, etc all excel, are cohesive, have tons of support and libraries to cover different needs, etc, and generally not too difficult to learn.
Though personally I found rails' magical 'convention over config' to be an abysmal hindrance to learning how things actually work - for example many examples show code, without showing where in the filesystem the code should go - you're expected to know the convention already, and things like i18n translation 'paths' can be confusing, and fail silently.