Thanks for reading!

I mostly share the sentiment from the other article that I quoted and linked. It's not about missing documentation but rather its approach that could add to the confusion.

It's like if two senior devs where writing this:

1: does this look good?
2: I understand it
1: perfect!

This wouldn't be an issue if there were a lot of other resources available - which is the case in other ecosystems - but a lot of articles I've found were old and outdated or there were barely any relevant results so I had no other choices but look at the source code of Rails to try and figure out what was going on.

I believe this is far from ideal if you are a new dev jumping into a framework and hence a negative point for me: a new dev jumping into RoR. And something that might discourage others from learning Rails.

Additionally I've found the guides fairly useful (and they are very good) but you have to invest time into going through them. I think more shorter guides/tutorials about core concepts, what could go wrong, common mistakes and so on can help revitalize the community or at least make it more inviting to junior devs.

Also any playgrounds are a bonus, if you check the Golang page, Laravel, React beta docs and Svelte they all make the first contact fairly accessible as well as inviting.