[michael_j_ward]

Having suffered through learning highly configurable software tools independently enough times, I agree completely with "digesting one or few commands" at a time works better for me too.

Spitballing:

We could probably make a general solution for organically producing "learning guide" if power users 1) share their custom configurations and share the frequencies of commands they use.

Start with the general configuration, knowing nothing about the commands the tool offers. The learning guide is just a queue of "here's the most common config edit that you don't have" and "here's the most common command that you don't know about."

We are already share configs with eachother via the dotfiles pattern. We somewhat share command patterns via coding streams. Seems doable.

(In general, making it easier to learn new tech and for devs to share / refresh the learning material for a new tech seem underdeveloped.)