The Lexicon of Scholarly Editing is an open academic resource for definitions of concepts that are relevant to the field of Scholarly Editing. Rather positing new definitions, however, the lexicon quotes existing definitions from textual scholars as they appear in academic articles, monographs, and the like. The Lexicon was first developed in WordPress (2012 onwards), but has been redeveloped into a Jekyll website in 2020 to make it more sustainable, more citable, to improve collaboration, crediting, and versioning options, and to allow for more automation while also publishing the definitions as a dataset. Find out more on our About page.
This repository was originally developed by Wout Dillen, as part of his position as a postdoctoral researcher at the University of Antwerp, while he was the university's coordinator of CLARIAH-VL. Wout currently works as a Senior Lecturer in Library and Information Science at the University of Borås, Sweden. He is also the Secretary of the European Society of Textual Scholarship (ESTS), and part of the Executive Board of the DH Benelux community. He is also the General Editor of the ESTS's journal Variants, Deputy Editor of Information Research, and on the editorial board of the DH Benelux Journal – all Open Access publications.
The repository's website was developed using Jekyll, and is hosted on GitHub Pages by making use of GitHub Actions (as documented in the Jekyll documentation). It uses Jekyll plugins such as jekyll-scholar and jekyll-last-modified-at, and its search function makes use of lunar.js. Except for the definitions themselves, the copyright of which belong to the relevant holders, this website's contents and design are licensed under a CC-BY 4.0 license.
The Lexicon is always looking for new definitions. If you have one or more that you'd like to share, please do! Follow our simple contribution steps, and you'll be credited for your efforts in the Lexicon.
For a trimmed down quick reference guide on how to add definitions to the Lexicon, check out our contribution file, as well as our Code of Conduct. For a more elaborate walk through the different steps, have a look at our wiki.