I think you’re partially correct by saying:[quote=“s3w47m88, post:9, topic:9328”]
in their own words - it was complicated. So I think I represent a demographic.
But that’s kind of the beauty of it. I’d like to consider myself one of dumbest people that has managed to learn Roots, and it’s definitely challenging sometimes. It takes a lot of self-research, reading through this discourse constantly, and spinning up new projects over and over until it’s basically muscle memory. By doing this I’ve also learned that 99% of the time the issue was on my end, not Root’s end.
Even then, it’s a stretch to say I’ve “learned” roots. Not one person will ever know everything about it.
I think the important thing to keep in mind is to just help the team help you as much as possible, so try to be very detailed without being overwhelming.
And when all else fails, hire them for support. Or even just when you want to understand something very thoroughly. It’s a small price to pay for all the free support and work they put towards this amazing open source tool. If you’re managing a large team running Roots I’d recommend even doing something like weekly consults and sometimes they may be cool with you recording it (so you can turn it into content, or share it with your team and new hires). It’s a very worthy investment if your want your team to run a tight ship.
Also, I keep a public cheatsheet for myself, but I must warn that I’ve too busy to keep it updated lately. So I can’t say if it’s accurate or note. I also have a quick setup tutorial. I had my friend shadow me during it who was just learning Roots so that we could do troubleshooting. Roots updates so fast that it makes it hard to keep these things updated, but you don’t have to use the most updated version. I state my exact versions I’m using so you can use older versions of everything.
Point being, this community is some of the best coders I can think of in the world (therefore very busy), so it’s only understandable things don’t work sometimes, and you have to pay for help sometimes. But if you stick with it, your Dev company will save so much money down the road, and be able to charge much higher prices. You will also become a much better developer having pushed through it.