I love this idea of “scratch notebooks” that you just write in and it doesn’t get saved unless you decide it’s useful. It’s why I stay in colab for so long.
If I were to write out how I’d imagine it going in a cell, something like:
# topic python {potential_specific_page_thingy}
# export_carbon {configA} {configB}
import importlib
def is_mylib_available():
return importlib.util.find_spec('mylib') is not None
You could then surround any documentation etc you want in markdown (maybe add another special tag in there to use), and then it gets converted, shoving it into a .py (with the markdown comments in the code!) + a documentation page, and finally a new clean notebook from your result.
Afterwards the “sandbox” notebook gets wiped for you to use again.
export_carbon in this case would make use of the carbon-now-cli to turn the snippet into a pretty picture for you to upload to twitter.
The key bits that are important for me to be able to use it:
It has to be quick, from both starting and finishing
Ideally it should have the concept of the scratchpad. This removes our “UntitledNotebook24.ipynb”
If the topic is the same/subtopic then merge them together into a single notebook, organized by date.
Those are my immediate thoughts, open to any opinions on it but that’s how I’d probably want to use such a framework