Add news post about PWD preprint (#98)

To fix linkcheck:
* Add eosc-hub.eu to linkcheck_ignore
* materialscloud.org/explore -> materialscloud.org/explore/menu to see if fixes exceeding redirects.

Author: GeigerJ2

docs/conf.py

@@ -156,6 +156,7 @@
     r"https://www.tara.tcd.ie/handle/2262/91467",
     r"https://juser.fz-juelich.de/record/873744",
     r"https://openbis.ch",  # Not accessibla as of 06-06-2025. Might come back
+    r"https://www.eosc-hub.eu/",  # Privacy warning when accessing manually
 ]
 
 aiida_ignore_event_checks = [

docs/news/posts/2025-05-26-python-workflow-definition.md

@@ -0,0 +1,29 @@
+---
+blogpost: true
+category: News
+tags: article
+date: 2025-05-26
+---
+
+# Preprint published: A Python workflow definition for computational materials design
+
+We're excited to announce the submission of our [paper preprint](https://arxiv.org/abs/2505.20366) titled "A Python workflow definition for computational materials design" to arXiv.
+
+In this joint effort, together with developers from the [pyiron](https://github.com/pyiron) and [jobflow](https://github.com/materialsproject/jobflow) workflow managers, we define a common format that allows sharing workflows between the different frameworks.
+
+To achieve this, the following three workflow ingredients are required:
+1. a conda environment that specifies the software dependencies,
+1. a Python module that contains the Python functions represented as nodes in the workflow graph, and
+1. a workflow graph stored in the JavaScript Object Notation (JSON).
+
+This means that, a workflow defined by the execution of Python functions, can therefore be:
+1. transformed into any of the workflow representations provided by the three worfklow managers (aiida, jobflow, pyiron),
+1. exported to the common, shared format, and, finally,
+1. executed by any of the other workflow managers.
+
+On our side, this has been made possible by the [`aiida-workgraph`](https://github.com/aiidateam/aiida-workgraph/) package, that allows for the flexible and dynamic construction of AiiDA workflows.
+You can find the code and documentation in the corresponding `Python Workflow Definition` [GitHub organization](https://github.com/pythonworkflow).
+
+Happy computing!
+
+The AiiDA team

docs/sections/about.md

@@ -14,7 +14,7 @@ AiiDA is built to support and streamline the four core pillars of the [ADES mode
 - **Advanced queries**: AiiDA’s query language enables fast graph queries on millions of nodes.
 - **Plugin interface**: AiiDA can support via plugins any computational code and data analytics tool, data type, scheduler, connection mode, etc. (see [public plugin repository](https://aiidateam.github.io/aiida-registry/))
 - **HPC interface**: AiiDA can seamlessly deal with heterogeneous and remote computing resources; it works with many schedulers out of the box (SLURM, PBS Pro, torque, SGE or LSF).
-- **Open science**: AiiDA allows to export both full databases and selected subsets, to be shared with collaborators or made available and browsable online on the [Archive](https://archive.materialscloud.org/) and [Explore](https://www.materialscloud.org/explore) sections of [Materials Cloud](https://www.materialscloud.org/).
+- **Open science**: AiiDA allows to export both full databases and selected subsets, to be shared with collaborators or made available and browsable online on the [Archive](https://archive.materialscloud.org/) and [Explore](https://www.materialscloud.org/explore/menu) sections of [Materials Cloud](https://www.materialscloud.org/).
 - **Open source**: AiiDA is released under the MIT open-source license.
 
 ## Features