The REST adapter supports a wide variety of functionality and options, but all these options appear on a single page, and there is no guidance on the order of steps needed to make it work. For example, it can be very confusing to figure out exactly what has to be done in order to enable the Design-By-Example button. Another example: It is very difficult to figure out which data name to choose for output because the names do not appear in the hierarchical order of the document. Other examples: it can be confusing to figure out how to define multiple operations, how to work with json vs xml, how to pipeline operations, etc. A step-by-step wizard-guided approach would solve these issues.
XSLT transforms of REST sources are SO PAINFUL. I have to hand edit definitions files, then the XSLT. It is 10x as much work as connecting to a table in a database.