[Idea]: Notebook structure

I was wondering if it's useful for learners to split up our main notebook into self contained parts for each of our image processing algorithms. Particularly if we want to go more in depth on any algorithm with visual examples this might be more digestible than one bigger file. For example we could have multiple notebooks (just copying what you have in the pipeline):
-synthetic_test_images.ipynb
-threseholding.ipynb
-distance_transform.ipynb
-local_minima_detection.ipynb
-watershed.ipynb
-analysing_segmented_objects.ipynb
-full_pipeline,ipynb

Then you can just set up your full_pipeline,ipynb for the user to run with a customisable example without explaining all the steps.

Would be good to hear your thoughts @davidbuech @jianlianggao

Start by reviewing the existing main notebook and the proposed structure: synthetic_test_images.ipynb, thre(se)holding.ipynb, distance_transform.ipynb, local_minima_detection.ipynb, watershed.ipynb, analysing_segmented_objects.ipynb, and full_pipeline.ipynb. Done means agreeing on the split and producing self-contained algorithm notebooks while keeping a customizable full-pipeline example.