How do I set up a listing with ipynb files?

[minnerbe]

Description

I'm trying to set up a custom listing with a bunch of notebooks. The notebooks are stored as py:percent files, but because execution is expensive (and the notebooks with final state are interesting to me on their own) I've converted them to .ipynb files using

quarto render scripts/notebook.py -t ipynb

I've also set up a custom listing that should take all the .ipynb files as content (specified by a _quarto.yaml and an index.qmd to orchestrate everything), but wasn't able to get the result I want: If I do quarto render . I get WARN: File scripts/notebook.ipynb in the listing 'listing' contains no metadata.. The file shows up in the listing, but seems broken (not clickable).

I was suspecting that I either messed up the listing orchestration, or the notebook metadata. However, the following works:

• If I replace scripts/*.ipynb with scripts/*.py in the render and contents attributes of the orchestration files, the listing works as expected (but execution is triggered), suggesting that the listing orchestration is ok.
• If I render a single notebook with quarto render scripts/notebook.ipynb, the output also looks as expected, suggesting that the notebook metadata is ok.

I've reduced the problem to three ~10 line files and I'm attaching the .ipynb for convenience (click here):

├── _quarto.yml
├── index.qmd
└── scripts
    ├── notebook.ipynb
    └── notebook.py

I already checked other discussions here about missing metadata in .ipynb files, but the solutions there didn't seem to apply to my situation. I'm happy for any pointers about what I might be doing wrong. Thank you!

(Quarto 1.7.31 on MacOS 15.4.1)

[mcanouil]

Your Jupyter Notebooks are not valid for Quarto as stated by the error message: they do not have any metadata.

quarto render does not convert. It renders. There are discussion output using ipynb as a target format and keeping the metadata.
Here is one of them:

• format: ipynb but keep yaml header #11644

quarto convert can convert (keeping everything including metadata) from Quarto plain text document to/from Jupyter Notebooks (json).

The listing feature works the same way for qmd/ipynb as long as they have the proper metadata such as title, author, date, etc. that the listing requires.
So you need to ensure the field/metadata requirements from your custom listing (or default) are met by your ipynb.