Open rowanc1 opened 4 days ago
@rowanc1 this is already covered here: https://mystmd.org/guide/notebooks-with-markdown#kernel-specification
Do you think it's not discoverable enough?
Ah, just seen some discussion on Discord.
@rowanc1 @choldgraf I actually think our existing content is somewhat well partitioned between the different docs pages, but their titles / organisation is not clear.
I took a moment to re-name things a little:
I think this is a lot clearer already. At a discursive level, we have:
{code-cell}
and {eval}
)ipynb
or .md
files can be executed with --execute
)These files are all distinct with clear distinct purposes. I wonder if there is a way to better separate the three core concepts here:
But this would already be an improvement.
This definitely feels like an improvement in clarity to me!
We likely need something like this in the frontmatter.
Previous docs page is here: https://jupyterbook.org/en/stable/file-types/myst-notebooks.html
Portions are here: https://mystmd.org/guide/notebooks-with-markdown
Suggested actions
Define two pages under the
Executable Content
section. These are the two titles/topics:Notebooks written in markdown
. How to define markdown files in a way that they will be treated as notebooks and executed (e.g. front-matter etc). Mention code-cell but don't go into much detail.Cell and in-line execution with Markdown
. How to define block- and inline-level execution with Markdown.