#jupytext — Public Fediverse posts

We’re rethinking the conference #Hackathon format by launching a HaCLAthon (C=Collaborative, L=Long-term, A=Asynchronous) [1] for the #IOER 2026 conference. [2]

The goal is a living #JupyterBook that becomes a citable publication with a DOI. Here is the stack I built to make it actually work:

1. The Problem: Jupyter Notebooks are great for #DataScience, but a difficult for collaborative #Git diffs and non-technical domain experts. Solution: We use #Jupytext to maintain a bidirectional sync between .ipynb (for code) and .md (for text stories).

2. The Problem: Inviting external contributions usually means a security/privacy black box if you use 3rd-party CMS brokers to link into Github/Gitlabs. Solution: I deployed a self-hosted #Golang OAuth broker to handle the GitHub handshake on our servers as a microsservice. 100% #DSGVO compliant and sovereign. [3]

3. The Problem: We want domain experts to write, but we don't want to force them to learn Git. Solution: Integrated a browser-based visual editor (#DecapCMS/#SveltiaCMS). Edits enter a Kanban-style editorial workflow as PRs. We review/merge on Github, and our #GitLab CI/CD builds the book.

4. The Result: Developers get #Jupyter4NFDI or local #Docker environments. Writers get a WYSIWYG browser editor. Everyone gets listed as an author on a persistent scientific artifact.

Documentation is also about building inclusive pipelines!

Want to contribute a "hack" or spatial data story?
We are looking for contributions on urban resilience, circularity, and land-use change. 🌍

Github: https://github.com/ioer-dresden/ioer-conference-2026-haclathon
Book: https://hack.conference.ioer.info/
Background: https://ad.vgiscience.org/links/posts/2026-05-07-haclathon/
Slides: https://slides.ad.ioer.info/haclathon/

#OpenScience #OpenData #Sustainability #Jupyter #DevOps #GIS #Infrastructure #HaCLAthon

@ioer @diegorybski.bsky.social

[1]: https://hack.conference.ioer.info/
[2]: https://conference.ioer.info/
[3]: https://gitlab.hrz.tu-chemnitz.de/ioer/fdz/tools/cms-auth
[4]: https://slides.ad.ioer.info/haclathon/

We’re rethinking the conference #Hackathon format by launching a HaCLAthon (C=Collaborative, L=Long-term, A=Asynchronous) [1] for the #IOER 2026 conference. [2]

The goal is a living #JupyterBook that becomes a citable publication with a DOI. Here is the stack I built to make it actually work:

1. The Problem: Jupyter Notebooks are great for #DataScience, but a difficult for collaborative #Git diffs and non-technical domain experts. Solution: We use #Jupytext to maintain a bidirectional sync between .ipynb (for code) and .md (for text stories).

2. The Problem: Inviting external contributions usually means a security/privacy black box if you use 3rd-party CMS brokers to link into Github/Gitlabs. Solution: I deployed a self-hosted #Golang OAuth broker to handle the GitHub handshake on our servers as a microsservice. 100% #DSGVO compliant and sovereign. [3]

3. The Problem: We want domain experts to write, but we don't want to force them to learn Git. Solution: Integrated a browser-based visual editor (#DecapCMS/#SveltiaCMS). Edits enter a Kanban-style editorial workflow as PRs. We review/merge on Github, and our #GitLab CI/CD builds the book.

4. The Result: Developers get #Jupyter4NFDI or local #Docker environments. Writers get a WYSIWYG browser editor. Everyone gets listed as an author on a persistent scientific artifact.

Documentation is also about building inclusive pipelines!

Want to contribute a "hack" or spatial data story?
We are looking for contributions on urban resilience, circularity, and land-use change. 🌍

Github: https://github.com/ioer-dresden/ioer-conference-2026-haclathon
Book: https://hack.conference.ioer.info/
Background: https://ad.vgiscience.org/links/posts/2026-05-07-haclathon/
Slides: https://slides.ad.ioer.info/haclathon/

#OpenScience #OpenData #Sustainability #Jupyter #DevOps #GIS #Infrastructure #HaCLAthon

@ioer @diegorybski.bsky.social

[1]: https://hack.conference.ioer.info/
[2]: https://conference.ioer.info/
[3]: https://gitlab.hrz.tu-chemnitz.de/ioer/fdz/tools/cms-auth
[4]: https://slides.ad.ioer.info/haclathon/

We’re rethinking the conference #Hackathon format by launching a HaCLAthon (C=Collaborative, L=Long-term, A=Asynchronous) [1] for the #IOER 2026 conference. [2]

The goal is a living #JupyterBook that becomes a citable publication with a DOI. Here is the stack I built to make it actually work:

1. The Problem: Jupyter Notebooks are great for #DataScience, but a difficult for collaborative #Git diffs and non-technical domain experts. Solution: We use #Jupytext to maintain a bidirectional sync between .ipynb (for code) and .md (for text stories).

2. The Problem: Inviting external contributions usually means a security/privacy black box if you use 3rd-party CMS brokers to link into Github/Gitlabs. Solution: I deployed a self-hosted #Golang OAuth broker to handle the GitHub handshake on our servers as a microsservice. 100% #DSGVO compliant and sovereign. [3]

3. The Problem: We want domain experts to write, but we don't want to force them to learn Git. Solution: Integrated a browser-based visual editor (#DecapCMS/#SveltiaCMS). Edits enter a Kanban-style editorial workflow as PRs. We review/merge on Github, and our #GitLab CI/CD builds the book.

4. The Result: Developers get #Jupyter4NFDI or local #Docker environments. Writers get a WYSIWYG browser editor. Everyone gets listed as an author on a persistent scientific artifact.

Documentation is also about building inclusive pipelines!

Want to contribute a "hack" or spatial data story?
We are looking for contributions on urban resilience, circularity, and land-use change. 🌍

Github: https://github.com/ioer-dresden/ioer-conference-2026-haclathon
Book: https://hack.conference.ioer.info/
Background: https://ad.vgiscience.org/links/posts/2026-05-07-haclathon/
Slides: https://slides.ad.ioer.info/haclathon/

#OpenScience #OpenData #Sustainability #Jupyter #DevOps #GIS #Infrastructure #HaCLAthon

@ioer @diegorybski.bsky.social

[1]: https://hack.conference.ioer.info/
[2]: https://conference.ioer.info/
[3]: https://gitlab.hrz.tu-chemnitz.de/ioer/fdz/tools/cms-auth
[4]: https://slides.ad.ioer.info/haclathon/

We’re rethinking the conference #Hackathon format by launching a HaCLAthon (C=Collaborative, L=Long-term, A=Asynchronous) [1] for the #IOER 2026 conference. [2]

The goal is a living #JupyterBook that becomes a citable publication with a DOI. Here is the stack I built to make it actually work:

1. The Problem: Jupyter Notebooks are great for #DataScience, but a difficult for collaborative #Git diffs and non-technical domain experts. Solution: We use #Jupytext to maintain a bidirectional sync between .ipynb (for code) and .md (for text stories).

2. The Problem: Inviting external contributions usually means a security/privacy black box if you use 3rd-party CMS brokers to link into Github/Gitlabs. Solution: I deployed a self-hosted #Golang OAuth broker to handle the GitHub handshake on our servers as a microsservice. 100% #DSGVO compliant and sovereign. [3]

3. The Problem: We want domain experts to write, but we don't want to force them to learn Git. Solution: Integrated a browser-based visual editor (#DecapCMS/#SveltiaCMS). Edits enter a Kanban-style editorial workflow as PRs. We review/merge on Github, and our #GitLab CI/CD builds the book.

4. The Result: Developers get #Jupyter4NFDI or local #Docker environments. Writers get a WYSIWYG browser editor. Everyone gets listed as an author on a persistent scientific artifact.

Documentation is also about building inclusive pipelines!

Want to contribute a "hack" or spatial data story?
We are looking for contributions on urban resilience, circularity, and land-use change. 🌍

Github: https://github.com/ioer-dresden/ioer-conference-2026-haclathon
Book: https://hack.conference.ioer.info/
Background: https://ad.vgiscience.org/links/posts/2026-05-07-haclathon/
Slides: https://slides.ad.ioer.info/haclathon/

#OpenScience #OpenData #Sustainability #Jupyter #DevOps #GIS #Infrastructure #HaCLAthon

@ioer @diegorybski.bsky.social

[1]: https://hack.conference.ioer.info/
[2]: https://conference.ioer.info/
[3]: https://gitlab.hrz.tu-chemnitz.de/ioer/fdz/tools/cms-auth
[4]: https://slides.ad.ioer.info/haclathon/

We’re rethinking the conference #Hackathon format by launching a HaCLAthon (C=Collaborative, L=Long-term, A=Asynchronous) [1] for the #IOER 2026 conference. [2]

The goal is a living #JupyterBook that becomes a citable publication with a DOI. Here is the stack I built to make it actually work:

1. The Problem: Jupyter Notebooks are great for #DataScience, but a difficult for collaborative #Git diffs and non-technical domain experts. Solution: We use #Jupytext to maintain a bidirectional sync between .ipynb (for code) and .md (for text stories).

2. The Problem: Inviting external contributions usually means a security/privacy black box if you use 3rd-party CMS brokers to link into Github/Gitlabs. Solution: I deployed a self-hosted #Golang OAuth broker to handle the GitHub handshake on our servers as a microsservice. 100% #DSGVO compliant and sovereign. [3]

3. The Problem: We want domain experts to write, but we don't want to force them to learn Git. Solution: Integrated a browser-based visual editor (#DecapCMS/#SveltiaCMS). Edits enter a Kanban-style editorial workflow as PRs. We review/merge on Github, and our #GitLab CI/CD builds the book.

4. The Result: Developers get #Jupyter4NFDI or local #Docker environments. Writers get a WYSIWYG browser editor. Everyone gets listed as an author on a persistent scientific artifact.

Documentation is also about building inclusive pipelines!

Want to contribute a "hack" or spatial data story?
We are looking for contributions on urban resilience, circularity, and land-use change. 🌍

Github: https://github.com/ioer-dresden/ioer-conference-2026-haclathon
Book: https://hack.conference.ioer.info/
Background: https://ad.vgiscience.org/links/posts/2026-05-07-haclathon/
Slides: https://slides.ad.ioer.info/haclathon/

#OpenScience #OpenData #Sustainability #Jupyter #DevOps #GIS #Infrastructure #HaCLAthon

@ioer @diegorybski.bsky.social

[1]: https://hack.conference.ioer.info/
[2]: https://conference.ioer.info/
[3]: https://gitlab.hrz.tu-chemnitz.de/ioer/fdz/tools/cms-auth
[4]: https://slides.ad.ioer.info/haclathon/

So I was having so much trouble x2go-ing with vscode for notebooks. Moved the workflow to emacs with jupytext and voilà ! I can open as many instances as I want, my crappy ssh bandwidth is ok, and of course, I can actually code properly. Win!

#x2go #ssh #emacs #jupytext

So I was having so much trouble x2go-ing with vscode for notebooks. Moved the workflow to emacs with jupytext and voilà ! I can open as many instances as I want, my crappy ssh bandwidth is ok, and of course, I can actually code properly. Win!

#x2go #ssh #emacs #jupytext

So I was having so much trouble x2go-ing with vscode for notebooks. Moved the workflow to emacs with jupytext and voilà ! I can open as many instances as I want, my crappy ssh bandwidth is ok, and of course, I can actually code properly. Win!

#x2go #ssh #emacs #jupytext

So I was having so much trouble x2go-ing with vscode for notebooks. Moved the workflow to emacs with jupytext and voilà ! I can open as many instances as I want, my crappy ssh bandwidth is ok, and of course, I can actually code properly. Win!

#x2go #ssh #emacs #jupytext

So I was having so much trouble x2go-ing with vscode for notebooks. Moved the workflow to emacs with jupytext and voilà ! I can open as many instances as I want, my crappy ssh bandwidth is ok, and of course, I can actually code properly. Win!

#x2go #ssh #emacs #jupytext

Two tools called out for automating the process of extracting reusable code from #Jupyter Notebooks:

#nbconvert: https://nbconvert.readthedocs.io/en/latest/
#jupytext: https://jupytext.readthedocs.io/en/latest/

Jupytext has a feature that allows for notebooks and scripts to keep in sync. And both of them might work well for simpler notebooks, definitely try them out to save time.

Two tools called out for automating the process of extracting reusable code from #Jupyter Notebooks:

#nbconvert: https://nbconvert.readthedocs.io/en/latest/
#jupytext: https://jupytext.readthedocs.io/en/latest/

Jupytext has a feature that allows for notebooks and scripts to keep in sync. And both of them might work well for simpler notebooks, definitely try them out to save time.

Two tools called out for automating the process of extracting reusable code from #Jupyter Notebooks:

#nbconvert: https://nbconvert.readthedocs.io/en/latest/
#jupytext: https://jupytext.readthedocs.io/en/latest/

Jupytext has a feature that allows for notebooks and scripts to keep in sync. And both of them might work well for simpler notebooks, definitely try them out to save time.

Two tools called out for automating the process of extracting reusable code from #Jupyter Notebooks:

#nbconvert: https://nbconvert.readthedocs.io/en/latest/
#jupytext: https://jupytext.readthedocs.io/en/latest/

Jupytext has a feature that allows for notebooks and scripts to keep in sync. And both of them might work well for simpler notebooks, definitely try them out to save time.

Two tools called out for automating the process of extracting reusable code from #Jupyter Notebooks:

#nbconvert: https://nbconvert.readthedocs.io/en/latest/
#jupytext: https://jupytext.readthedocs.io/en/latest/

Jupytext has a feature that allows for notebooks and scripts to keep in sync. And both of them might work well for simpler notebooks, definitely try them out to save time.

I'm a bit frustrated that the markdown generated by #jupytext does not contain the images resulting from the cell executions... I can imagine it would be hard or impractical to make it work like that, but I'm not sure how to build a workflow out of it.

I'm a bit frustrated that the markdown generated by #jupytext does not contain the images resulting from the cell executions... I can imagine it would be hard or impractical to make it work like that, but I'm not sure how to build a workflow out of it.

I'm a bit frustrated that the markdown generated by #jupytext does not contain the images resulting from the cell executions... I can imagine it would be hard or impractical to make it work like that, but I'm not sure how to build a workflow out of it.

I'm a bit frustrated that the markdown generated by #jupytext does not contain the images resulting from the cell executions... I can imagine it would be hard or impractical to make it work like that, but I'm not sure how to build a workflow out of it.

I'm a bit frustrated that the markdown generated by #jupytext does not contain the images resulting from the cell executions... I can imagine it would be hard or impractical to make it work like that, but I'm not sure how to build a workflow out of it.

JupyterLab Desktop goes Thonny

Doch jetzt geht JupyterLab Desktop, die Variante der Jupyter-IDE, die JupyterLab aus den Klauen der Webbrowser befreien will, mit der aktuellen Version 4.1 noch einen Schritt weiter: Sie erlaubt die Erstellung, Verwaltung und den Aufruf virtueller Umgebungen aus der Applikation heraus, ohne sich in die (Un-) Tiefen der Kommandozeile begeben zu müssen. https://kantel.github.io/posts/2024022002_jupyterlabdesktop_thonny/ #Jupyter #Python #JupyterLabDesktop #Jupytext #MySTMarkdown

JupyterLab Desktop goes Thonny

Doch jetzt geht JupyterLab Desktop, die Variante der Jupyter-IDE, die JupyterLab aus den Klauen der Webbrowser befreien will, mit der aktuellen Version 4.1 noch einen Schritt weiter: Sie erlaubt die Erstellung, Verwaltung und den Aufruf virtueller Umgebungen aus der Applikation heraus, ohne sich in die (Un-) Tiefen der Kommandozeile begeben zu müssen. https://kantel.github.io/posts/2024022002_jupyterlabdesktop_thonny/ #Jupyter #Python #JupyterLabDesktop #Jupytext #MySTMarkdown

JupyterLab Desktop goes Thonny

Doch jetzt geht JupyterLab Desktop, die Variante der Jupyter-IDE, die JupyterLab aus den Klauen der Webbrowser befreien will, mit der aktuellen Version 4.1 noch einen Schritt weiter: Sie erlaubt die Erstellung, Verwaltung und den Aufruf virtueller Umgebungen aus der Applikation heraus, ohne sich in die (Un-) Tiefen der Kommandozeile begeben zu müssen. https://kantel.github.io/posts/2024022002_jupyterlabdesktop_thonny/ #Jupyter #Python #JupyterLabDesktop #Jupytext #MySTMarkdown

JupyterLab Desktop goes Thonny

Doch jetzt geht JupyterLab Desktop, die Variante der Jupyter-IDE, die JupyterLab aus den Klauen der Webbrowser befreien will, mit der aktuellen Version 4.1 noch einen Schritt weiter: Sie erlaubt die Erstellung, Verwaltung und den Aufruf virtueller Umgebungen aus der Applikation heraus, ohne sich in die (Un-) Tiefen der Kommandozeile begeben zu müssen. https://kantel.github.io/posts/2024022002_jupyterlabdesktop_thonny/ #Jupyter #Python #JupyterLabDesktop #Jupytext #MySTMarkdown

JupyterLab Desktop goes Thonny

Doch jetzt geht JupyterLab Desktop, die Variante der Jupyter-IDE, die JupyterLab aus den Klauen der Webbrowser befreien will, mit der aktuellen Version 4.1 noch einen Schritt weiter: Sie erlaubt die Erstellung, Verwaltung und den Aufruf virtueller Umgebungen aus der Applikation heraus, ohne sich in die (Un-) Tiefen der Kommandozeile begeben zu müssen. https://kantel.github.io/posts/2024022002_jupyterlabdesktop_thonny/ #Jupyter #Python #JupyterLabDesktop #Jupytext #MySTMarkdown

#Jupyter+#Jupytext. I just discovered Jupytext and it's completely changed my life. Suddenly my project which was to be code, documentation, and discourse trying to explain what it was all about has become just notebook chapters that are meant to be read, run, and imported as libraries. That's just terrific. Now my sub-modules are chapters, and my whole project without me realizing it has turned into a "book" in progress - which is actually the best way to present it all.

Using #MarkdownSQLPro Tools 🛠️ with new #SQLBookmarks 🔖, #SQLite & our #DuckDBPro #SQLTools in #VSCode IDE on @ploomber's #JupySQL #JupyText / #MyST #JupyterBook 📓 markdown docs 😎

#SQL #DuckDB #Markdown #ProDataTools 🧙‍♂️ ...

Using #MarkdownSQLPro Tools 🛠️ with new #SQLBookmarks 🔖, #SQLite & our #DuckDBPro #SQLTools in #VSCode IDE on @ploomber's #JupySQL #JupyText / #MyST #JupyterBook 📓 markdown docs 😎

#SQL #DuckDB #Markdown #ProDataTools 🧙‍♂️ ...

Using #MarkdownSQLPro Tools 🛠️ with new #SQLBookmarks 🔖, #SQLite & our #DuckDBPro #SQLTools in #VSCode IDE on @ploomber's #JupySQL #JupyText / #MyST #JupyterBook 📓 markdown docs 😎

#SQL #DuckDB #Markdown #ProDataTools 🧙‍♂️ ...

Using #MarkdownSQLPro Tools 🛠️ with new #SQLBookmarks 🔖, #SQLite & our #DuckDBPro #SQLTools in #VSCode IDE on @ploomber's #JupySQL #JupyText / #MyST #JupyterBook 📓 markdown docs 😎

#SQL #DuckDB #Markdown #ProDataTools 🧙‍♂️ ...

Using #MarkdownSQLPro Tools 🛠️ with new #SQLBookmarks 🔖, #SQLite & our #DuckDBPro #SQLTools in #VSCode IDE on @ploomber's #JupySQL #JupyText / #MyST #JupyterBook 📓 markdown docs 😎

#SQL #DuckDB #Markdown #ProDataTools 🧙‍♂️ ...

@philiph have u tried the tool that converts and syncs notebooks to .Md files #jupytext and #nbdime well for us. https://blog.reviewnb.com/tools-for-git-jupyter-workflow/ I haven’t tried #nbdime yet but in a workflow which is quick and dirty then getting more serious jupytext is nice and integrated documents with code overall is nice. Then u can use nbdev to turn it into a module.

@philiph have u tried the tool that converts and syncs notebooks to .Md files #jupytext and #nbdime well for us. https://blog.reviewnb.com/tools-for-git-jupyter-workflow/ I haven’t tried #nbdime yet but in a workflow which is quick and dirty then getting more serious jupytext is nice and integrated documents with code overall is nice. Then u can use nbdev to turn it into a module.

@philiph have u tried the tool that converts and syncs notebooks to .Md files #jupytext and #nbdime well for us. https://blog.reviewnb.com/tools-for-git-jupyter-workflow/ I haven’t tried #nbdime yet but in a workflow which is quick and dirty then getting more serious jupytext is nice and integrated documents with code overall is nice. Then u can use nbdev to turn it into a module.

@philiph have u tried the tool that converts and syncs notebooks to .Md files #jupytext and #nbdime well for us. https://blog.reviewnb.com/tools-for-git-jupyter-workflow/ I haven’t tried #nbdime yet but in a workflow which is quick and dirty then getting more serious jupytext is nice and integrated documents with code overall is nice. Then u can use nbdev to turn it into a module.

If you find yourself tracking revisions of #Jupyter #notebooks on #git (or an inferior #VCS), you will LOVE #Jupytext!

Since the text editor Atom (+Hydrogen) was sunset, I found myself coming back to Jupyter more often for interactive stuff. Now I can save notebooks as .py (Markdown in comments) or as .md (Python in code blocks) -- or both and have one updated when I change the other. And the best thing: Thanks to Jupytext they run and feel exactly as .ipynb. #python #ide

If you find yourself tracking revisions of #Jupyter #notebooks on #git (or an inferior #VCS), you will LOVE #Jupytext!

Since the text editor Atom (+Hydrogen) was sunset, I found myself coming back to Jupyter more often for interactive stuff. Now I can save notebooks as .py (Markdown in comments) or as .md (Python in code blocks) -- or both and have one updated when I change the other. And the best thing: Thanks to Jupytext they run and feel exactly as .ipynb. #python #ide