About¶

Citing depictr¶

If depictr helps your work, a citation is appreciated:

Bernabeu, P. (2026). depictr: A unified, colourblind-safe toolkit for publication-ready statistical visualisation (Python). Version 0.3.0. https://doi.org/10.5281/zenodo.21266311

@Manual{depictr-py,
  title  = {depictr: A unified, colourblind-safe toolkit for publication-ready statistical visualisation (Python)},
  author = {Pablo Bernabeu},
  year   = {2026},
  note   = {Python package version 0.3.0},
  doi    = {10.5281/zenodo.21266311},
  url    = {https://doi.org/10.5281/zenodo.21266311},
}

Download .bib

The repository's CITATION.cff carries the same metadata in machine-readable form.

The developer¶

depictr is developed by Pablo Bernabeu, a researcher in the Department of Education at the University of Oxford. His work spans cognitive psychology and neuroscience, linguistics, education and digital technologies, drawing on a range of methods that include behavioural and EEG experiments, corpus analysis and computational modelling. He is a Fellow of the Software Sustainability Institute (2020), recognised for his work on R-based tools for data presentation, and holds a PhD in Psychology from Lancaster University.

More about his work is at pablobernabeu.github.io, on GitHub and via ORCID 0000-0003-1083-2460.

depictr has a sibling R package that shares the same design.

Licence¶

depictr is released under the MIT licence, whose full text is on this site's licence page and in the repository's LICENSE file. The licence permits use, modification and redistribution, commercially or not, provided the copyright and permission notice travel with the code.

Versioning and archival¶

Releases are tagged on GitHub and archived on Zenodo. The concept DOI, 10.5281/zenodo.21266311, always resolves to the latest archived version, so a citation that uses it does not go stale. The changelog records what changed in each release.

Contributing and support¶

Bug reports and feature requests are welcome on the issues page, where a small, self-contained example (and, for a plotting bug, a screenshot) makes a problem much easier to act on. The contributing guide explains how to set up a development install and what conventions a pull request should follow.