There is also The Odin Project, but I haven't tried it myself. https://www.theodinproject.com/paths/full-stack-ruby-on-rail...
A few channels I would also recommend is: Deanin, SuperRails & DriftingRuby. https://www.youtube.com/@Deanin https://www.youtube.com/@SupeRails https://www.youtube.com/@DriftingRuby
Some would also recommend GoRails, but I had a hard time following his guides because most of is videos are just cut-outs from his paid courses. So it was hard to follow with him without the whole context of the project.
I am sure this question has been asked multiple times here on HN so you can search for them and see what others have previously said.
The rails.org guide is looking like a good start.
Found your comment on the topic from two years ago, funny enough.
For example, built-in capabilities for authentication are limited: https://github.com/rails/rails/issues/50446
So then do you go with has_secure_password/etc., Devise, rodauth, authentication-zero, or something else? These are big decisions that then might affect other things like authorization, OAuth, PassKey, etc.
And that's authentication & authorization which are a relatively well-understood and maintained area, but other areas might have totally unmaintained gems that might have issues with recent versions of Rails, or native module compilation issues with more recent versions of operating systems, etc.
A lot of Rails guidance on blog posts and StackOverflow might be outdated.
This problem is not unique to Rails. I still think Rails is great and relatively vibrant. Nevertheless, I suggest being very wary of Rails guides, blog posts, and StackOverflow answers that are more than 1 year old and doing a careful study and inventory of gems before deciding to use them and reviewing their relative recent usage and activity.
The latest stuff in Rails 7 (hotwire/stimulus aka turbo-drive, turbo-frames and turbo-streams) might mean you need very little front-end JS if you don't want to learn a bunch about that. Something worth diving into once you learn basics of Rails.
A lot of the opinionated parts of Rails (convention over configuration) are bike shed discussions with other languages/frameworks. I remember countless debates with co-workers on file structure layout for web apps in the 2000's using Java. So many hours wasted, I'd rather be building something, kinda was the lure that got me to transition to Rails.
I remember being completely new to Rails and spinning up a licensing server for a project, which would eventually become Keygen, within a couple weeks. But this was also after writing an internal CLI tool in Ruby, so I already felt quite proficient in Ruby at the time having spent ~6 months with it prior to Rails.