Document better how users can import JSON from clients

[m-mohr]

Document better how users can import JSON from clients, see feedback below:

In the editor, once you have generated a process, you can export the code in three programming languages (Javascript, Python and R), however, you cannot import processes from other languages, because it only allows you to import json files, which are javascript files, but not even the one you have exported previously.

It is actually possible to generate the JSON from the client libraries so you can go in circles here: Editor -> R -> Editor -> Python -> Editor would work. Each client can generate the corresponding JSON output so that you can import it into the Web Editor again. This doesn't work directly with the Python and R code as they don't run in the Browser so this small workaround is needed to go via JSON. See the details here: https://openeo.org/documentation/1.0/cookbook/#output-process-as-json

[m-mohr]

I started with an overview that users get on "startup" when the model builder is empty. Once you start intreracting with the canvas, e.g. by dragging something, it disappears.

What do you think? Does this help? Is this confusing? What can we improve? Do the explanations for Python/R work?

cc'ing @dthiex (due to the demo today), @soxofaan (Python client), and @flahn (R client)

[m-mohr]

Also add the code to the import modal.

[soxofaan]

I somehow missed this ticket. I'd like to point to this cookbook page from python client docs which discusses:

• https://open-eo.github.io/openeo-python-client/cookbook/tricks.html#export-a-process-graph how to export to JSON
• https://open-eo.github.io/openeo-python-client/cookbook/tricks.html#execute-a-process-graph-directly-from-raw-json how to directly execute a process graph given as "raw" JSON

[m-mohr]

Thanks, the first link is actually already included in PR #273 :-)

The second link is a good addition although I'd hope it's not required so often as we also have the Python code export itself.