Documentation as notebooks and vice versa

Interesting observation from Google Earth Engine community docs:
e.g. https://developers.google.com/earth-engine/tutorials/community/intro-to-python-api-guiattard is written as a notebook (https://github.com/google/earthengine-community/blob/master/tutorials/intro-to-python-api-guiattard/index.ipynb), but seamlessly integrated in their documentation tree

It could be useful to adapt that approach as well for a part of the openEO python lib documentation (e.g. quick start or tutorials):

• makes it easy to check that snippets are valid (could be even part of integration test suite)
• allows user to start experimenting directly from docs downloaded as notebook

Start by reviewing the linked Google Earth Engine documentation and its tutorials/intro-to-python-api-guiattard/index.ipynb example. Then inspect the openEO Python client’s quick-start and tutorial documentation to determine a workable notebook-to-docs approach and how snippet validation or integration tests could fit; done means a concrete, tested workflow is defined.