diff --git a/docs/talks/assets/20260402 - Open code/slides.pdf b/docs/talks/assets/20260402 - Open code/slides.pdf
new file mode 100644
index 0000000..ec98fe1
Binary files /dev/null and b/docs/talks/assets/20260402 - Open code/slides.pdf differ
diff --git a/docs/talks/index.md b/docs/talks/index.md
index 673511e..70875c2 100644
--- a/docs/talks/index.md
+++ b/docs/talks/index.md
@@ -26,8 +26,6 @@ Abstract: ...
 
 _Titles are placeholder._
 
-- 2026-04-02\* | "Open code from a journal submissions perspective" by Erik van Sebille ([:material-github: Discussion](https://github.com/UU-IMAU/python-for-lunch/issues/18))
-    - Abstract: Many academic journals require research code to be available when you submit a manuscript to them. But how do you organise that? Where do you put the code in such a way that you can still make changes to it, and that it is also archived for the future? In this talk, I will show how you can combine GitHub with a Zenodo workflow to create a DOI on every Release of your code. We will also have time for a more general discussion on the opportunities and difficulties of publishing code with manuscripts.
 - 2026-04-16\* | "Data processing with CDO" by Oliver Mehling ([:material-github: Discussion](https://github.com/UU-IMAU/python-for-lunch/issues/38))
 - 2026-04-30\* | TBD
 - 2026-05-14 | _None (Public holiday)_
@@ -124,6 +122,14 @@ _Titles are placeholder._
 
 **Abstract:** Many research projects depend on a specific computational environment. Over time, changes in dependencies, Python versions, or operating systems can make scripts harder to run or share, especially when working across different machines or with collaborators. In this talk, I will introduce Pixi, a drop-in replacement for Conda which provides much better workflows for managing project environments and dependencies. Whether you work alone or in a team, Pixi helps you see exactly what your project depends on, collaborate without environment headaches, and reproduce other researchers’ work.
 
+### 2026-04-02 | "Open code from a journal submissions perspective" by Erik van Sebille
+
+[:octicons-video-16: Recording](https://youtu.be/CccrDjNn3IU),
+[:material-presentation-play: Slideshow](./assets/20260402%20-%20Open%20code/slides.pdf),
+[:material-github: Discussion](https://github.com/UU-IMAU/python-for-lunch/issues/18)
+
+**Abstract:** Many academic journals require research code to be available when you submit a manuscript to them. But how do you organise that? Where do you put the code in such a way that you can still make changes to it, and that it is also archived for the future? In this talk, I will show how you can combine GitHub with a Zenodo workflow to create a DOI on every Release of your code. We will also have time for a more general discussion on the opportunities and difficulties of publishing code with manuscripts.
+
 ### Archived talks
 
 [Archived talks](https://github.com/UU-IMAU/Python-for-lunch-Notebooks/blob/main/archived)