home.social
Sign in Create account

#jupyterbook — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #jupyterbook, aggregated by home.social.

  1. Alexander Dunkel @[email protected] ·

    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: github.com/ioer-dresden/ioer-c
    Book: hack.conference.ioer.info/
    Background: ad.vgiscience.org/links/posts/
    Slides: slides.ad.ioer.info/haclathon/

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

    @ioer @diegorybski.bsky.social

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

    #hackathon #ioer #jupyterbook #datascience #git #jupytext
  2. Alexander Dunkel @[email protected] ·

    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: github.com/ioer-dresden/ioer-c
    Book: hack.conference.ioer.info/
    Background: ad.vgiscience.org/links/posts/
    Slides: slides.ad.ioer.info/haclathon/

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

    @ioer @diegorybski.bsky.social

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

    #hackathon #ioer #jupyterbook #datascience #git #jupytext
  3. Alexander Dunkel @[email protected] ·

    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: github.com/ioer-dresden/ioer-c
    Book: hack.conference.ioer.info/
    Background: ad.vgiscience.org/links/posts/
    Slides: slides.ad.ioer.info/haclathon/

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

    @ioer @diegorybski.bsky.social

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

    #hackathon #ioer #jupyterbook #datascience #git #jupytext
  4. Alexander Dunkel @[email protected] ·

    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: github.com/ioer-dresden/ioer-c
    Book: hack.conference.ioer.info/
    Background: ad.vgiscience.org/links/posts/
    Slides: slides.ad.ioer.info/haclathon/

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

    @ioer @diegorybski.bsky.social

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

    #haclathon #infrastructure #gis #devops #jupyter #sustainability
  5. Alexander Dunkel @[email protected] ·

    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: github.com/ioer-dresden/ioer-c
    Book: hack.conference.ioer.info/
    Background: ad.vgiscience.org/links/posts/
    Slides: slides.ad.ioer.info/haclathon/

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

    @ioer @diegorybski.bsky.social

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

    #decapcms #gitlab #jupyter4nfdi #docker #openscience #opendata
  6. Jörg Kantel @[email protected] ·

    Ein Geschenk zu Ostern: MyST Markdown 1.8.2 ist draußen

    Ich kann ja nicht immer nur von meinen (zukünftigen) virtuellen Reisen ins Wunderland träumen, sondern gelegentlich sollte ich auch mal wieder über meine Publikationsstrategie nachdenken. Und da stehen zur Zeit MkDocs (Material) und MyST Markdown ganz oben auf der Liste der dafür nutzbaren Werkzeuge. kantel.github.io/posts/2026040 #MystMarkdown #Markdown #Jupyter #JupyterLabDesktop #JupyterBook

    #mystmarkdown #markdown #jupyter #jupyterlabdesktop #jupyterbook
  7. Jörg Kantel @[email protected] ·

    Ein Geschenk zu Ostern: MyST Markdown 1.8.2 ist draußen

    Ich kann ja nicht immer nur von meinen (zukünftigen) virtuellen Reisen ins Wunderland träumen, sondern gelegentlich sollte ich auch mal wieder über meine Publikationsstrategie nachdenken. Und da stehen zur Zeit MkDocs (Material) und MyST Markdown ganz oben auf der Liste der dafür nutzbaren Werkzeuge. kantel.github.io/posts/2026040 #MystMarkdown #Markdown #Jupyter #JupyterLabDesktop #JupyterBook

    #mystmarkdown #markdown #jupyter #jupyterlabdesktop #jupyterbook
  8. Jörg Kantel @[email protected] ·

    Ein Geschenk zu Ostern: MyST Markdown 1.8.2 ist draußen

    Ich kann ja nicht immer nur von meinen (zukünftigen) virtuellen Reisen ins Wunderland träumen, sondern gelegentlich sollte ich auch mal wieder über meine Publikationsstrategie nachdenken. Und da stehen zur Zeit MkDocs (Material) und MyST Markdown ganz oben auf der Liste der dafür nutzbaren Werkzeuge. kantel.github.io/posts/2026040 #MystMarkdown #Markdown #Jupyter #JupyterLabDesktop #JupyterBook

    #jupyterbook #jupyterlabdesktop #jupyter #markdown #mystmarkdown
  9. Jörg Kantel @[email protected] ·

    Ein Geschenk zu Ostern: MyST Markdown 1.8.2 ist draußen

    Ich kann ja nicht immer nur von meinen (zukünftigen) virtuellen Reisen ins Wunderland träumen, sondern gelegentlich sollte ich auch mal wieder über meine Publikationsstrategie nachdenken. Und da stehen zur Zeit MkDocs (Material) und MyST Markdown ganz oben auf der Liste der dafür nutzbaren Werkzeuge. kantel.github.io/posts/2026040 #MystMarkdown #Markdown #Jupyter #JupyterLabDesktop #JupyterBook

    #mystmarkdown #markdown #jupyter #jupyterlabdesktop #jupyterbook
  10. Jörg Kantel @[email protected] ·

    Die Wiederentdeckung von MyST Markdown: Mein neues Publikationstool?

    Als mir jüngst zwei Videos zu MyST Markdown von unser allwissenden Datenkrake in meinen Feedreader gespült wurden, fiel mir ein, daß mir das Tool vor etwa zwei Jahren schon einmal untergekommen war und ich es so interessant fand, daß ich eigentlich ein paar Tests damit durchführen wollte. kantel.github.io/posts/2025111 #MySTMarkdown #JupyterLab #JupyterLabDesktop #Markdown #JupyterLite #JupyterBook #VisualStudioCode #Sphinx #Quarto

    #mystmarkdown #jupyterlab #jupyterlabdesktop #markdown #jupyterlite #jupyterbook
  11. Jörg Kantel @[email protected] ·

    Die Wiederentdeckung von MyST Markdown: Mein neues Publikationstool?

    Als mir jüngst zwei Videos zu MyST Markdown von unser allwissenden Datenkrake in meinen Feedreader gespült wurden, fiel mir ein, daß mir das Tool vor etwa zwei Jahren schon einmal untergekommen war und ich es so interessant fand, daß ich eigentlich ein paar Tests damit durchführen wollte. kantel.github.io/posts/2025111 #MySTMarkdown #JupyterLab #JupyterLabDesktop #Markdown #JupyterLite #JupyterBook #VisualStudioCode #Sphinx #Quarto

    #mystmarkdown #jupyterlab #jupyterlabdesktop #markdown #jupyterlite #jupyterbook
  12. Jörg Kantel @[email protected] ·

    Die Wiederentdeckung von MyST Markdown: Mein neues Publikationstool?

    Als mir jüngst zwei Videos zu MyST Markdown von unser allwissenden Datenkrake in meinen Feedreader gespült wurden, fiel mir ein, daß mir das Tool vor etwa zwei Jahren schon einmal untergekommen war und ich es so interessant fand, daß ich eigentlich ein paar Tests damit durchführen wollte. kantel.github.io/posts/2025111 #MySTMarkdown #JupyterLab #JupyterLabDesktop #Markdown #JupyterLite #JupyterBook #VisualStudioCode #Sphinx #Quarto

    #quarto #sphinx #visualstudiocode #jupyterbook #jupyterlite #markdown
  13. Jörg Kantel @[email protected] ·

    Die Wiederentdeckung von MyST Markdown: Mein neues Publikationstool?

    Als mir jüngst zwei Videos zu MyST Markdown von unser allwissenden Datenkrake in meinen Feedreader gespült wurden, fiel mir ein, daß mir das Tool vor etwa zwei Jahren schon einmal untergekommen war und ich es so interessant fand, daß ich eigentlich ein paar Tests damit durchführen wollte. kantel.github.io/posts/2025111 #MySTMarkdown #JupyterLab #JupyterLabDesktop #Markdown #JupyterLite #JupyterBook #VisualStudioCode #Sphinx #Quarto

    #mystmarkdown #jupyterlab #jupyterlabdesktop #markdown #jupyterlite #jupyterbook
  14. MyST Markdown @[email protected] ·

    MyST Markdown is soaring with 350,000 monthly downloads!

    Lots of data scientists and researchers are now able to author better scientific and technical documents — FASTER — thanks to MyST. #MySTMarkdown #JupyterBook #OpenSource
    executablebooks.org/en/latest/

    #mystmarkdown #jupyterbook #opensource
  15. MyST Markdown @mystmarkdown ·

    MyST Markdown is soaring with 350,000 monthly downloads!

    Lots of data scientists and researchers are now able to author better scientific and technical documents — FASTER — thanks to MyST.
    executablebooks.org/en/latest/

    #mystmarkdown #jupyterbook #opensource
  16. MyST Markdown @[email protected] ·

    MyST Markdown is soaring with 350,000 monthly downloads!

    Lots of data scientists and researchers are now able to author better scientific and technical documents — FASTER — thanks to MyST. #MySTMarkdown #JupyterBook #OpenSource
    executablebooks.org/en/latest/

    #mystmarkdown #jupyterbook #opensource
  17. MyST Markdown @[email protected] ·

    MyST Markdown is soaring with 350,000 monthly downloads!

    Lots of data scientists and researchers are now able to author better scientific and technical documents — FASTER — thanks to MyST. #MySTMarkdown #JupyterBook #OpenSource
    executablebooks.org/en/latest/

    #opensource #jupyterbook #mystmarkdown
  18. MyST Markdown @[email protected] ·

    MyST Markdown is soaring with 350,000 monthly downloads!

    Lots of data scientists and researchers are now able to author better scientific and technical documents — FASTER — thanks to MyST. #MySTMarkdown #JupyterBook #OpenSource
    executablebooks.org/en/latest/

    #mystmarkdown #jupyterbook #opensource
  19. Jörg Kantel @[email protected] ·

    Interaktive Publikationen mit MyST Markdown und Jupyter Book

    Mir ist mal wieder danach, ich muß über meine Publikationsstrategie nachdenken. Denn der Vorteil meines Rentnerdaseins ist unter anderem der, daß ich nicht mehr publizieren muß. Stattdessen kann ich darüber nachdenken, wie ich ohne den Druck der Verlagshäuser, Redaktionen und auch meines Brötchengebers publizieren könnte. kantel.github.io/posts/2023083 #MySTMarkdown #JupyterBook #JupyterLab #VisualStudioCode

    #mystmarkdown #jupyterbook #jupyterlab #visualstudiocode
  20. Jörg Kantel @[email protected] ·

    Interaktive Publikationen mit MyST Markdown und Jupyter Book

    Mir ist mal wieder danach, ich muß über meine Publikationsstrategie nachdenken. Denn der Vorteil meines Rentnerdaseins ist unter anderem der, daß ich nicht mehr publizieren muß. Stattdessen kann ich darüber nachdenken, wie ich ohne den Druck der Verlagshäuser, Redaktionen und auch meines Brötchengebers publizieren könnte. kantel.github.io/posts/2023083 #MySTMarkdown #JupyterBook #JupyterLab #VisualStudioCode

    #mystmarkdown #jupyterbook #jupyterlab #visualstudiocode
  21. Jörg Kantel @[email protected] ·

    Interaktive Publikationen mit MyST Markdown und Jupyter Book

    Mir ist mal wieder danach, ich muß über meine Publikationsstrategie nachdenken. Denn der Vorteil meines Rentnerdaseins ist unter anderem der, daß ich nicht mehr publizieren muß. Stattdessen kann ich darüber nachdenken, wie ich ohne den Druck der Verlagshäuser, Redaktionen und auch meines Brötchengebers publizieren könnte. kantel.github.io/posts/2023083 #MySTMarkdown #JupyterBook #JupyterLab #VisualStudioCode

    #visualstudiocode #jupyterlab #jupyterbook #mystmarkdown
  22. Taras Novak 🇺🇦 @[email protected] ·

    📢 We released new version of #MarkdownSQL Pro Tools. New features:

    ✅ SQL code block highlights & selections

    ✅ Detection of %%sql magic code blocks & %sql magic code lines

    ✅ New #SQLBookmarks 📑

    ✅ New Extract All SQL code lens

    ✅ MyST #JupyterBook markdown documents support

    ✅ SQL code lenses for #Quarto, #Rmarkdown, and #ObservableJS docs

    Docs and new demos at:

    📰 ⮚ randomfractals.github.io/pro-d

    These tools are free today, for one day only. Sign up to try them out!

    💖 ⮚ github.com/sponsors/RandomFrac

    #observablejs #rmarkdown #quarto #jupyterbook #sqlbookmarks #markdownsql
  23. Taras Novak 🇺🇦 @[email protected] ·

    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 🧙‍♂️ ...

    #prodatatools #markdown #duckdb #sql #jupyterbook #myst
  24. Taras Novak 🇺🇦 @[email protected] ·

    Same #JupySQL Intro #JupyterBook 📓 markdown document in #VSCode IDE with the added top level Execute All, Select All, Extract All SQL code lenses, and Execute, Select, Copy and Create SQL code lenses in the code cells with %%sql #SQLMagics:

    #MarkdownSQLProTools 🧙‍♂️ ...

    #markdownsqlprotools #sqlmagics #vscode #jupyterbook #jupysql
  25. Taras Novak 🇺🇦 @[email protected] ·

    Same #JupySQL Intro #JupyterBook 📓 markdown document in #VSCode IDE with the added top level Execute All, Select All, Extract All SQL code lenses, and Execute, Select, Copy and Create SQL code lenses in the code cells with %%sql #SQLMagics:

    #MarkdownSQLProTools 🧙‍♂️ ...

    #markdownsqlprotools #sqlmagics #vscode #jupyterbook #jupysql
  26. Taras Novak 🇺🇦 @[email protected] ·

    Same #JupySQL Intro #JupyterBook 📓 markdown document in #VSCode IDE with the added top level Execute All, Select All, Extract All SQL code lenses, and Execute, Select, Copy and Create SQL code lenses in the code cells with %%sql #SQLMagics:

    #MarkdownSQLProTools 🧙‍♂️ ...

    #markdownsqlprotools #sqlmagics #vscode #jupyterbook #jupysql
  27. Taras Novak 🇺🇦 @[email protected] ·

    Same #JupySQL Intro #JupyterBook 📓 markdown document in #VSCode IDE with the added top level Execute All, Select All, Extract All SQL code lenses, and Execute, Select, Copy and Create SQL code lenses in the code cells with %%sql #SQLMagics:

    #MarkdownSQLProTools 🧙‍♂️ ...

    #jupysql #jupyterbook #vscode #sqlmagics #markdownsqlprotools
  28. Taras Novak 🇺🇦 @[email protected] ·

    Same #JupySQL Intro #JupyterBook 📓 markdown document in #VSCode IDE with the added top level Execute All, Select All, Extract All SQL code lenses, and Execute, Select, Copy and Create SQL code lenses in the code cells with %%sql #SQLMagics:

    #MarkdownSQLProTools 🧙‍♂️ ...

    #markdownsqlprotools #sqlmagics #vscode #jupyterbook #jupysql
  29. Taras Novak 🇺🇦 @[email protected] ·

    Quick demo of the new Extract All SQL and Execute SQL code lenses in the upcoming #MarkdownSQL Pro Tools v1.2.0 with #JupyterBook markdown support and #JupySQL / #SQLMagics SQL code extraction and execution in action:

    This example uses VS Code #SQLTools and #DuckDBPro Tools to execute SQL queries directly from the Jupy SQL Jupyter Book markdown document (github.com/ploomber/jupysql/bl).

    #VSCode #ProDataTools 🧙‍♂️ ...

    #prodatatools #vscode #duckdbpro #sqltools #sqlmagics #jupysql
  30. Taras Novak 🇺🇦 @[email protected] ·

    Quick demo of the new Extract All SQL and Execute SQL code lenses in the upcoming #MarkdownSQL Pro Tools v1.2.0 with #JupyterBook markdown support and #JupySQL / #SQLMagics SQL code extraction and execution in action:

    This example uses VS Code #SQLTools and #DuckDBPro Tools to execute SQL queries directly from the Jupy SQL Jupyter Book markdown document (github.com/ploomber/jupysql/bl).

    #VSCode #ProDataTools 🧙‍♂️ ...

    #prodatatools #vscode #duckdbpro #sqltools #sqlmagics #jupysql
  31. Taras Novak 🇺🇦 @[email protected] ·

    Quick demo of the new Extract All SQL and Execute SQL code lenses in the upcoming #MarkdownSQL Pro Tools v1.2.0 with #JupyterBook markdown support and #JupySQL / #SQLMagics SQL code extraction and execution in action:

    This example uses VS Code #SQLTools and #DuckDBPro Tools to execute SQL queries directly from the Jupy SQL Jupyter Book markdown document (github.com/ploomber/jupysql/bl).

    #VSCode #ProDataTools 🧙‍♂️ ...

    #prodatatools #vscode #duckdbpro #sqltools #sqlmagics #jupysql
  32. Taras Novak 🇺🇦 @[email protected] ·

    Quick demo of the new Extract All SQL and Execute SQL code lenses in the upcoming #MarkdownSQL Pro Tools v1.2.0 with #JupyterBook markdown support and #JupySQL / #SQLMagics SQL code extraction and execution in action:

    This example uses VS Code #SQLTools and #DuckDBPro Tools to execute SQL queries directly from the Jupy SQL Jupyter Book markdown document (github.com/ploomber/jupysql/bl).

    #VSCode #ProDataTools 🧙‍♂️ ...

    #markdownsql #jupyterbook #jupysql #sqlmagics #sqltools #duckdbpro
  33. Taras Novak 🇺🇦 @[email protected] ·

    Quick demo of the new Extract All SQL and Execute SQL code lenses in the upcoming #MarkdownSQL Pro Tools v1.2.0 with #JupyterBook markdown support and #JupySQL / #SQLMagics SQL code extraction and execution in action:

    This example uses VS Code #SQLTools and #DuckDBPro Tools to execute SQL queries directly from the Jupy SQL Jupyter Book markdown document (github.com/ploomber/jupysql/bl).

    #VSCode #ProDataTools 🧙‍♂️ ...

    #prodatatools #vscode #duckdbpro #sqltools #sqlmagics #jupysql
  34. Ben Companjen 🟥 @[email protected] ·

    I would like to include structured metadata as JSON-LD in a JupyterBook, e.g. following the bioschemas.org/profiles/Traini schema. But JB and Sphinx seem to only support very limited metadata.
    Does anyone have experience with this?

    #metadata #learningResource #OER #JupyterBook #SphinxDoc

    #metadata #learningresource #oer #jupyterbook #sphinxdoc
  35. Vincent-Xavier ⏚ @[email protected] ·

    Pour pas que @poulmairecharles me grille en train de jouer sur la #fcen, j'ai joué sur #Framagit et j'ai produit framagit.org/lamadone/informat
    En gros, on peut instancier un service #kroki/#mermaid dans un build dockerisé, utilisable sans dépendre du service externe.

    Je ne sais pas si vous me suivez, mais moi, je suis fier de moi et ça me suffit.

    #gitlab #ci #jupyterbook #docker

    #docker #jupyterbook #ci #gitlab #kroki #framagit
  36. Vincent-Xavier ⏚ @[email protected] ·

    Pour pas que @poulmairecharles me grille en train de jouer sur la #fcen, j'ai joué sur #Framagit et j'ai produit framagit.org/lamadone/informat
    En gros, on peut instancier un service #kroki/#mermaid dans un build dockerisé, utilisable sans dépendre du service externe.

    Je ne sais pas si vous me suivez, mais moi, je suis fier de moi et ça me suffit.

    #gitlab #ci #jupyterbook #docker

    #docker #jupyterbook #ci #gitlab #kroki #framagit
  37. Vincent-Xavier ⏚ @[email protected] ·

    Pour pas que @poulmairecharles me grille en train de jouer sur la #fcen, j'ai joué sur #Framagit et j'ai produit framagit.org/lamadone/informat
    En gros, on peut instancier un service #kroki/#mermaid dans un build dockerisé, utilisable sans dépendre du service externe.

    Je ne sais pas si vous me suivez, mais moi, je suis fier de moi et ça me suffit.

    #gitlab #ci #jupyterbook #docker

    #docker #jupyterbook #ci #gitlab #kroki #framagit
  38. Vincent-Xavier ⏚ @[email protected] ·

    Pour pas que @poulmairecharles me grille en train de jouer sur la #fcen, j'ai joué sur #Framagit et j'ai produit framagit.org/lamadone/informat
    En gros, on peut instancier un service #kroki/#mermaid dans un build dockerisé, utilisable sans dépendre du service externe.

    Je ne sais pas si vous me suivez, mais moi, je suis fier de moi et ça me suffit.

    #gitlab #ci #jupyterbook #docker

    #fcen #framagit #kroki #gitlab #ci #jupyterbook