Deploying to gh-pages from @ b2601ef 🚀

Author: jan-janssen

README.html

@@ -367,15 +367,12 @@ <h2> Contents </h2>
 <h1>Python Workflow Definition<a class="headerlink" href="#python-workflow-definition" title="Link to this heading">#</a></h1>
 <p><a class="reference external" href="https://github.com/pythonworkflow/python-workflow-definition/actions/workflows/pipeline.yml"><img alt="Pipeline" src="https://github.com/pythonworkflow/python-workflow-definition/actions/workflows/pipeline.yml/badge.svg" /></a>
 <a class="reference external" href="https://mybinder.org/v2/gh/pythonworkflow/python-workflow-definition/HEAD"><img alt="Binder" src="https://mybinder.org/badge_logo.svg" /></a>
+<a class="reference external" href="https://arxiv.org/abs/2505.20366"><img alt="arXiv" src="https://img.shields.io/badge/arXiv-2505.20366-b31b1b.svg" /></a>
 <a class="reference external" href="https://doi.org/10.5281/zenodo.15516179"><img alt="DOI" src="https://zenodo.org/badge/945869529.svg" /></a></p>
 <section id="definition">
 <h2>Definition<a class="headerlink" href="#definition" title="Link to this heading">#</a></h2>
 <p>In the Python Workflow Definition (PWD) each node represents a Python function, with the edges defining the connection
 between input and output of the different Python functions.</p>
-<p>Publication:</p>
-<ul class="simple">
-<li><p><a class="reference external" href="https://doi.org/10.1039/D5DD00231A">J. Janssen, J. George, J. Geiger, M. Bercx, X. Wang, C. Ertural, J. Schaarschmidt, A.M. Ganose, G. Pizzi, T. Hickel and J. Neugebauer. A python workflow definition for computational materials design. Digital Discovery, 2025</a></p></li>
-</ul>
 </section>
 <section id="format">
 <h2>Format<a class="headerlink" href="#format" title="Link to this heading">#</a></h2>

_sources/README.md

@@ -1,15 +1,13 @@
 # Python Workflow Definition
 [![Pipeline](https://github.com/pythonworkflow/python-workflow-definition/actions/workflows/pipeline.yml/badge.svg)](https://github.com/pythonworkflow/python-workflow-definition/actions/workflows/pipeline.yml)
 [![Binder](https://mybinder.org/badge_logo.svg)](https://mybinder.org/v2/gh/pythonworkflow/python-workflow-definition/HEAD)
+[![arXiv](https://img.shields.io/badge/arXiv-2505.20366-b31b1b.svg)](https://arxiv.org/abs/2505.20366)
 [![DOI](https://zenodo.org/badge/945869529.svg)](https://doi.org/10.5281/zenodo.15516179)
 
 ## Definition
 In the Python Workflow Definition (PWD) each node represents a Python function, with the edges defining the connection 
 between input and output of the different Python functions. 
 
-Publication:
-* [J. Janssen, J. George, J. Geiger, M. Bercx, X. Wang, C. Ertural, J. Schaarschmidt, A.M. Ganose, G. Pizzi, T. Hickel and J. Neugebauer. A python workflow definition for computational materials design. Digital Discovery, 2025](https://doi.org/10.1039/D5DD00231A)
-
 ## Format
 Each workflow consists of three files, a Python module which defines the individual Pythons, a JSON file which defines
 the connections between the different Python functions and a conda environment file to define the software dependencies.