# Jupyter Book Collaboration Cafe

Thank you for joining Jupyter Book's Collaboration Café! We are delighted to have you here. No sign-ups needed! :coffee: :sparkles: :cake:

:::info
- **Video link:** https://meet.jit.si/jupyter-book-collab-cafe
- **Calendar for future meetings/events:** https://compass.jupyterbook.org/contribute#where-to-talk
- **Tracking work**: [Team Priorities](https://github.com/orgs/jupyter-book/projects/1/views/7) | [Team Roadmap](https://github.com/orgs/jupyter-book/projects/1/views/1)
- **Facilitator checklist**: [Team Compass link]().
:::

## Code of Conduct

**By participating in this meeting, you are agreeing to abide by and uphold the [Code of Conduct](https://jupyter.org/conduct). Please take a second to read through it! :pray:**

## August 2025
### Attendees

- Angus Hollands
- Chris Holdgraf
- Brigitta Sipőcz
- Robert Lanzafame

### Meeting Notes
- Robert introduces himself and the TeachBooks project, currently on JB1.
- https://teachbooks.io/about/
- Other participants follow suit to introduce one another.
- Angus speaks to the philosophy of extensions whereby core shared functionality should be something we build in, but anything bespoke should be supported by a strong extension API
- Chris talks about the extension API pain points with an analogy between nb6 and nb7
- Robert is encouraged to share issues that help us track missing functionality
- Chris shares example of a tracking issue that shows an example of this: https://github.com/jupyter-book/mystmd/issues/1336
- Robert talks about the TeachBooks focus
- Target users are non-GitHub natives
- Chris talks about how we triage issues, and that whilst we do have a technical backlog of things that need to be done, we also have non-engineering needs too (e.g. docs, etc.)
- Issue to check here: https://github.com/jupyter-book/team-compass/issues/46
- Angus shares execution initiative: https://github.com/jupyter-book/mystmd/issues/2019
- Angus mentions link check initiative

### Next actions

## Jupyter Book Collaboration Cafe | June 2025

### Attendees

- Angus Hollands
- Steve Purves
- Franklin Koch
- Chris Holdgraf
- Stéfan van der Walt
- Freek

### Agenda

- Jupyter Book talk @ SciPy
- Angus and Franklin splitting talk
- [Talk Abstract & Schedule Entry](https://cfp.scipy.org/scipy2025/talk/NYPUVH/)
- Franklin's bio needs update
- [Proceedings submission](https://github.com/scipy-conference/scipy_proceedings/pull/1096) - reviews and suggestions there are open to the entire JB2 team
- Rowan's suggestion
- MyST overview
- Success stories
- Jupyter Book 2 releases
- What is "beta"?
- Suggestion that we think about this through the lens of safety.
- We can also query existing users (@agoose77) but I'm not advocating that we actually do this.
- What is needed for beta?
- [In-browser execution allow readers to edit cell content](https://github.com/jupyter-book/mystmd/issues/443)
- Why not Binder? Might not be GDPR compliant. Students don't know lab/notebook interfaces. Jupyter Book helps it remain as simple as possible.
- Generate and show markdown with cell outputs` (see below for more links)
- Showing "unsupported" outputs from code-cells, e.g. Markdown
- Other items:
- [remove-input PR](https://github.com/jupyter-book/mystmd/pull/1937)
- Franklin will try to take a look at this one this week - I think this is very small.
- [Lightweight team practices](https://github.com/jupyter-book/team-compass/issues/28) -> team priority buckets
- Stefan shared his ideas around a "side quests" column
- Refined issues that we'd like somebody to tackle, but may not be roadmap priorities.
- A way to encourage others to pick them up w/ more confidence that the issue is well-scoped and of interest to maintainers. ([see description here](https://github.com/jupyter-book/team-compass/issues/28#issuecomment-2960806850))

## Meeting Notes

## Decisions

- We want to release a beta version of Jupyter Book 2 before SciPy.

## Next actions

- [ ] Create a source of truth for the markdown outputs issue
- [ ] Merge the "SciPy" and the "Beta" columns in the project board.
- [ ] Make it clear that the two items in this meeting are the blockers for beta
- [ ] Signal-boost the need for a Jupyter Book 2 gallery.

## Alpha vs. beta

- Decision: We need to decide when to call Jupyter Book 2 and MyST "Beta" rather than "alpha".

- Freek: user onboarding is difficult because of a lack of examples to work from. More like https://executablebooks.org/en/latest/gallery/ where there are complete examples, and you can pick up more than you can from the small examples on the docs alone. Has already prepped [a cheetsheet](https://tud-seed.github.io/IVO/features) pulling things together as a start point for students.

## More details on the "Outputs" work:

* [User stories](https://hackmd.io/H7ERZTycQlKy52JIlEWhDw)
* [myst-theme Outputs AST change prep](https://github.com/jupyter-book/myst-theme/pull/571)
* [mystmd Outputs AST](https://github.com/jupyter-book/mystmd/pull/1903)
* [mystmd Markdown 7 Latex changes](https://github.com/jupyter-book/mystmd/pull/1961)
* [long-running issue mystmd#1026](https://github.com/jupyter-book/mystmd/issues/1026)

## SciPy Talks - Feedback from Reviewers

Might be helpful when preparing the content

> I think this session will be very useful for the SciPy community. I'm looking forward to seeing Jupyter Book 2.0 in action.

> Adding specific, relatable examples or comprehensive case studies would significantly improve the demonstration of how these concepts can be effectively utilized in everyday activities.

> This is such a foundational work that clearly will generate significant interest among SciPy participants. I also find useful for authors to plan for in-depth tutorial in the upcoming events. I am personally very interested to learn details on new interactivity experience I can get with Book 2.0 and other game-changing features. I will love to learn more about MyST Markdown. It will be hard to cover these in depths during a 30-minute talk. I highly recommend complementing the talk with respective tutorial, if possible. 5 min demo isn't enough.

> I'm excited to see the improvements and updates to the JupyterBook software+ecosystem. This sounds like it would make an excellent workshop in future SciPy sessions.