I understand all that. I just thought that maybe such resources existed which I didn't know.
While as you say the approaches differ it would be nice to have like a FAQ "how do you do what LaTeX package X does in ConTeXt?" I guess that that is what I'm after. Something like a LaTeX <--> ConTeXt Rosetta stone. Knowing that rather than importing a package I should modify some command using some options is basic; what one really needs to know is which specific command to modify using which specific options with which specific values to do what package X does in LaTeX. If/since it doesn't exist maybe it would be a good thing if users make it exist. It would certainly help drawing more proselytes. I'm basically still using only LaTeX because I know which packages to use to do the things I want. Perhaps that *is* as good a reason as any to stay with LaTeX but it shouldn't be a barrier to learning ConTeXt which IME it is.
To take but one example: when wearing my linguist hat I deal with obscure scripts and languages, mostly dead languages, which no standard LaTeX index processor can handle (at least not out of the box) so I have my pile of Perl hacks which generate indices using Perl's excellent Unicode capabilities and some excellent modules written by other people. (I use the same LaTeX packages as everyone else, I just have a homemade way of going from idx to ind.) The first hurdle to know if/how ConTeXt might offer a better solution (which it doesn't AFAIK but my own tool can easily generate ConTeXt markup as well as LaTeX markup should it come to that) was to find out that indices are called "registers" in ConTeXt (not too surprising since it is _register_ in Swedish) for searching for "index" on the ConTeXt wiki finds an error page!
Admittedly it might be just me: I have a hard time knowing where to look in the likewise excellent Vim documentation too: what search terms to use. Finding a LaTeX solution to a problem with Google OTOH usually is pretty fast done — if you can describe your problem in prose you usually don't hit a wall.
With knowledge of TeX basics I did not mean a working knowledge of plain TeX but the actual basics: reserved characters, syntax, space after a command is ignored, a blank line makes a paragraph, that sort of things which are common to all flavors.
--
Better --help|less than helpless