nba-monte-carlo VS notebook

We have support for duckdb (and CSVs and Parquet through duckdb). We don't support python, but some people have also told us they have used evidence as the front-end for a python project - used python to do data transformation and calculations, then dumped the results into a duckdb file in an evidence project and built the visuals and narrative in evidence.

"Containerized" approaches with evidence are also quite interesting - lets you combine several tools and use evidence as the last mile. Here's a great example: https://github.com/matsonj/nba-monte-carlo

How about something like [`input`](magic-link)? I came up with this for https://codeberg.org/macchiato ( though it's not yet implemented in the new project, just in the predecessor, https://github.com/ResourcesCo/notebook ). The backquotes differentiate from non-magic links. (I tried badges, but they aligned weirdly.)

You could use [`data.mrr`](https://evidence.dev/md/value) or any other internal DSL you can come up with.

Another thing you could do is just decide against MDX the format and keep the style and transform inline codeblocks that match.

That you said Markdown to me says you aren't on board with using an incompatible syntax.

Markdown can literally be code. RMarkdown is this. Before I learned of RMarkdown I had written something to extract code blocks with filenames that are visible in the rendered page (since hiding it at the end of the first triple backquote codefence isn't great for visibility). I'm currently working on a notebook tool. https://github.com/ResourcesCo/macchiato/blob/main/scripts/m... https://github.com/ResourcesCo/notebook