Chapter 20. Anthology Customization

Introduction to Anthologies

The documentation in this chapter is for anthology leads (such as the Coordinating Editors of the ISE, DRE, or MoMS, or the QME General Editors).

Rationale

LEMDO supports a number of anthology projects (DRE, EMEE, ISE, MoMS, NISE, QME, and others). These anthologies are central to LEMDO’s core objective: to increase the number of teachable and performable early modern plays by creating open-access digital critical editions.

Role Divisions

The LEMDO team at UVic focuses on building the publication platform and editorial tools according to the current best practices for long-lived, light-weight, archivable websites. The anthologies focus on working with editors to prepare editions. Anthologies have their own editorial and advisory boards, their own peer review processes, and their own internal workflows. Generally, the LEMDO team will not work directly with your editors—except to help them get set up to work in the LEMDO repository—unless you invite us to liaise directly with an editor.

What’s Common to All Anthologies

All anthologies share the same TEI customization, the same underlying encoding, the same processing, the same core set of functionalities, and the same text analysis tools in order to make texts interoperable and interchangeable between anthologies.

What’s Unique to Each Anthology

Anthologies have their own look, menus, colour schemes, and logos. Anthologies may have different methodologies. For example, QME adopts a Performance as Research (PAR) methodology. Anthologies will have their own requirements for the length, number, and scope of critical paratexts. LEMDO’s documentation flags points on which anthologies have to make a decision or can choose between options.
Each anthology will have its own role names for team members. Whatever you call yourself (General Editor, Textual Editor, Coordinating Editor), LEMDO thinks of you as an anthology lead.

Contents

Section Description
Set Up Your Anthology in the LEMDO Repository Learn how to add your anthology’s directory to the LEMDO repository and how to organize its folder structure
Anthology About Pages Learn about how to add and write your anthology’s about pages, and which required about pages are written by members of the LEMDO team
LEMDO’s Default Style Learn about what you can expect your anthology to look like with LEMDO’s default styling
Customize Your Anthology Learn about what you can customize to give your anthology a unique look and feel

Further Reading

Anthology leads interested in the technical aspects of building and customizing their anthologies may want to read LEMDO’s Build Process in the chapter on Programming.

Set Up Your Anthology in the LEMDO Repository

Rationale

Each anthology has a directory in the LEMDO repository’s data/anthologies directory. This documentation explains how your anthology directory is created and named, the organizational structure of anthology directories, and who is responsible for adding and updating the various components found in anthology directories.

Creation of Anthology Directories

The LEMDO team will add your anthology directory to the LEMDO repository. The name of your directory will be your anthology’s internal abbreviation,1 given in all lower-case letters.

Current Anthology Directory Paths
Anthology Public Abbreviation Internal Abbreviation Directory path
LEMDO Classroom Classroom classroom lemdo/data/anthologies/classroom
The Douai Shakespeare Manuscript Project Douai/DSMP douai lemdo/data/anthologies/douai
Digital Restoration Drama DRD drd lemdo/data/anthologies/drd
Digital Renaissance Editions DRE dre lemdo/data/anthologies/dre
Early Modern Dramatic Paratexts EMDP emdp lemdo/data/anthologies/emdp
Early Modern England Encyclopedia EMEE emee lemdo/data/anthologies/emee
MoEML Mayoral Shows MoMS moms lemdo/data/anthologies/moms
New Internet Shakespeare Editions NISE nise lemdo/data/anthologies/nise
LEMDO Peer-Review Peer-Review peer-review lemdo/data/anthologies/peer-review
Queen’s Men Editions QME qme lemdo/data/anthologies/qme
LEMDO will add the following folders and files to your anthology directory:
about: Although you may choose to add additional folders to organize your anthology about pages, LEMDO will add one folder called about for files such as your anthology history, contributors, and user guide. For more information on anthology about pages, see Anthology About Pages.
site: Your site directory contains anthology-specific styling in a Cascading Style Sheet (aka CSS file), interactions in JavaScript (aka JS file), and a site template in HTML. There is more information on the contents of your site directory in Anthology Site Directories. Generally speaking, if you hire a developer or designer for your anthology, this directory is the one in which they will work.
config_staticSearch.xml: This file adds the code for staticSearch to your anthology. staticSearch is the fully Endings-Compliant search function that is used in all LEMDO anthologies. You will not make any changes in this file.
[anth].xml (i.e., dre.xml, moms.xml, etc.): This file contains the metadata for your entire anthology along with the content and metadata for your anthology’s home page. You will add to this file the content that you wish to appear when people visit your site. For more information on anthology XML pages, see Special Case: Anthology XML Pages.
[anth]_stopwords.txt: This file is used by the staticSearch code to make your anthology searchable. You will not make any changes in this file.
[anth]_words.txt: You will not make any changes in this file.
VERSION: This file captures the version number of your next release. You will not make any changes in this file.

Anthology Site Directories

Your site directory contains the files that give your anthology website its own unique feel. Inside site, you will find the following folders:
css
favicon
fonts (optional)
images
js
template

The CSS Folder

CSS, or Cascading Style Sheets, is the language that we use to style our Web pages. CSS is a core language used across the Web. We also use the CSS extension language SCSS (Sassy Cascading Style Sheets), which allows us to nest styling.
In your anthology’s css folder, you will find an [anth].scss file. Typically, LEMDO’s standard styling will suffice for almost everything that your anthology needs. You will, however, want to add your anthology’s colours in this file. For more information on what to update in your anthology’s SCSS file, see Customize Your Anthology. For more technical information on how to update your anthology’s SCSS file, see Customize Your Anthology’s CSS.

Favicons

A favicon is the tiny image that appears beside the Web page name in browser tabs. For example, if you visit the MoMS anthology site, you will see that their favicon in the browser tab is the City of London crest.
Your favicon folder contains your favicon at the different sizes and resolutions required in different browsers and on different devices. If you are uncertain about the sizes that you require, contact the LEMDO team.

Fonts

Although most anthologies use LEMDO’s default Alegreya fonts on their websites, you may choose to use a different font. If your anthology wants to use a different font, you will need to download the font family that you wish to use into a fonts folder.

Anthology Images

You will add all of the images that you require for your anthology about pages (including your homepage) in your images folder.

The JavaScript Folder

JavaScript, or JS, is the language that we use to add interactions to our websites. Like CSS, JavaScript is a core language used across the Web. It allows us to do things like change the directions of the arrows in our top navigation bar when each tab is opened or closed.
In your anthology’s js folder, you will find an [anth].js file. Typically, you will not need to add or change anything in your [anth].js file. If you do wish to add interactivity beyond what LEMDO has applied to all anthologies, consult with the LEMDO team.

The Template Folder

Your template folder will contain a sitePage.html file. This file is written in HTML (Hypertext Markup Language), which is the XML language in which our websites are built (from the underlying XML files). Like CSS and JavaScript, HTML is a core language of the Web. While CSS is how things look and JS is how things happen, HTML is the foundation for all the content that is styled by CSS and made interactive by JS.
Your sitePage.html files acts as the scaffolding for your anthology’s website. What appears in this file is the base template for the structure of each of your Web pages. You will work with the LEMDO team to determine what you need to add or change in your sitePage.html file. These are the key sections that are required in all anthology sitePage.html files:
A link to LEMDO’s SCSS so that our standard styling applies to your website.
A link to your anthology’s SCSS so that your anthology’s styling applies to your website.
Links to your favicons so that a favicon appears in the browser tab for your website.
The contents of your top navigation bar so that people can easily move through your website.
The contents of your footer so that your supporters get due credit.

Practice: Customize the Contents of Your Anthology Directory

If you wish to add more folders to your anthology directory, you may. Additional folders should be used to organize your anthology’s about files. To add a new folder:
In Terminal, cd (change directory) into your anthology’s directory.
Run the command svn add followed by the name of your new directory. Note that anthology folders’ names should use camel case (i.e., the first letter is lower-case and the first letter of following words is capitalized such as in performanceEditions).
svn commit as usual.
You might need to refresh the parent directory in your Project view in Oxygen in order to see the folder that you just created. To do so, right-click on your anthology directory in your Project view and select “Refresh” from the drop-down menu that appears.
You may find it helpful to look at other anthologies’ directories while you decide how to customize your own. You are able to view other anthologies’ directories in Oxygen, but you are not able to commit changes to directories other than your own.

Further Reading

Customize Your Anthology’s CSS (for Programmers or anthology leads that intend to work on their own anthology styling)

Anthology About Pages

Rationale

Your anthology’s About pages are a key part of your anthology. You may add About pages to give readers additional context about the editions in your anthology and to provide information about your anthology’s history, scope, editorial practices, contributors, and more. In addition to pages you write for your anthology, LEMDO has some standard About pages that you must include in your anthology: User Guide, staticSearch, Privacy, Release Notes, and Publisher and Platform.
This documentation outlines what you can add in your anthology’s About pages, what is required by LEMDO, and who is responsible for writing and updating your About pages. It also includes information on your anthology page ([anth].xml; e.g., dre.xml) and explains how you will use your anthology page to include editions in your anthology.

Disambiguation

This documentation does not explain where to save your anthology About pages. Each anthology will have a slightly different folder structure in its anthology directory. For information about how to organize the files in your anthology directory, see Set Up Your Anthology in the LEMDO Repository.

About Pages Required in All Anthologies

All LEMDO anthologies must include the following About pages:
Anthology Bibliography (for works cited in the About pages)
Contributors (or equivalent)
Release Notes
StaticSearch
User Guide
Privacy
Platform and Publisher
In addition, each anthology will have homepage content. Homepage content is captured in the anthology page ([anth].xml; e.g., dre.xml). For more information on anthology homepages, see Special Case: Anthology XML Pages.

Anthology Bibliographies

You anthology bibliography will include all of the sources cited in your anthology’s About pages. Optional: You may also include all the sources cited in the editions in your anthology, but remember that every edition has its own bibliography page; for some anthologies (e.g., DRE, NISE), such a task would be daunting, while other anthologies (e.g., MoMS) might want to aggregate all the scholarship in one place. Use your common sense about what will serve your users best.
Use our edition bibliography template (lemdo/data/templates/editionBibliography_template.xml) to create your anthology bibliography file. Customize the divisions to match your anthology’s bibliography needs. For example, you may wish to have two bibliography lists, each contained within its own <listBibl> element: one for works cited in your About pages and one for works cited in your anthology’s editions. For information on creating a new file from a LEMDO template, see Use LEMDO’s Oxygen Templates. For information on how to structure and encode your bibliography, see Curate Edition Bibliography.
In your anthology bibliography, add a <bibl> element for each of the unique sources cited with a <ref> element in your anthology directory (e.g., lemdo/data/anthologies/dre. Ensure that you also add commented-out human-readable information about the source as outlined in Practice: Create Sections in Your Edition Bibliography.
To compile sources for your anthology bibliography from your About pages (and, if you wish, your anthology’s editions), follow these steps:
To find all of the sources cited in your anthology About pages, go to the Project pane in Oxygen and find your anthology’s directory (e.g., lemdo/data/anthologies/moms).
Right-click on your anthology’s directory and select Find/Replace in Files …. (Note that you are merely finding things, not replacing them.)
In the Text to find search bar, type <ref type="bibl" (include the opening pointy bracket < but do not add a closing pointy bracket).
Click the Find all button. This search will find all of the sources cited with a <ref> element in your anthology directory.
Optional steps if you are aggregating edition bibliographies:
Go into each of your published editions’ bibliography files and copy the contents of their <listBibl> elements (i.e., copy all of the <bibl> elements and their associated XML comments).
Paste the contents as children of the appropriate <listBibl> element in your anthology bibliography file.
Put the pasted <bibl> elements in alphabetical order, ensuring that you keep the correct XML comment beside each <bibl> element.
Where there are duplicate entries, delete all but one. The easiest time to delete duplicates is after you have put the bibliography into alphabetical order.

Contributors Page(s)

Your anthology should have at least one page listing and giving credit to contributors. There are various ways to organize and title such pages. Here are some examples from already published anthologies:
LEMDO’s People page (under the About menu)
MoMS’s Team page (under the Credits menu)
MoMS’s Editors page (with a table showing editions, links, and release dates; also under the Credits menu)
QME’s Acknowledgements page (also under the About menu)
DSMP’s People page (under their About menu)
DSMP’s Supporters page (under the Credits menu)
Remember that every name can be tagged with a <persName> element and a @target attribute pointing to the contributor’s bio-bibliographical note from the LEMDO-wide PERS1.xml file. The LEMDO processing will automatically create a clickable link and a pop-up window with the contributor’s name and their LEMDO bio at the time of your anthology release. If you want to customize someone’s bio or capture their bio at a particular moment in time other than the release, then you may wish to include and encode a bio (instead of tagging the person’s name). Generally, however, it’s better to pull in the current contributor bio by tagging the contributor’s name.
If LEMDO developers, designers, and project managers contribute substantially to the functionality, design, and release of your anthology, please acknowledge them.2

Release Notes

Every anthology must have a Release Notes page. LEMDO recommends beginning the page with an explanation of the static release model. Recommended text:
<p>The <!-- insert project name --> (<!-- insert project acronym -->) follows the <ref target="https://endings.uvic.ca/principles.html#release-management">Endings Principles for Release Management</ref>. We periodically release new static versions of this website as new material is created and peer-reviewed. The release is comprised of a complete and self-contained set of HTML files; these files have no dependencies on external code libraries or on a back-end server. The Endings <ref target="https://endings.uvic.ca/staticSearch/docs/howDoesItWork.html">
  <title level="m">staticSearch</title> engine</ref> (created by <name ref="pers:HOLM1">Martin Holmes</name> and <name ref="pers:TAKE1">Joey Takeda</name>) is built into the release so that <!-- insert project acronym --> is fully concordanced, indexed, and searchable. The <!-- insert project acronym --> release schedule allows us to publish editions as they are completed, add new documentary discoveries, and update our bibliography in a systematic way. Each static release has a version number. Major releases are indicated by a change to the whole number integer (1.0 to 2.0). Minor releases of content are indicated by a change to the point number (1.0 to 1.1). The first <!-- insert project acronym --> release on the LEMDO platform is numbered 1.0. Releases are described on this page in chronological order.</p>
With each release, you will add a new <div> below the <div> for the previous release.3 The <head> element should contain the release number. Here’s an example for the second release of the Douai Shakespeare Manuscript Project:
<div xml:id="douai_release_1.1">
  <head>DSMP 1.1</head>
  <p xml:id="douai_release_p5">This second release of the DSMP anthology on the LEMDO platform on 2025-07-03 is the first release of the semi-diplomatic editions of the Douai <title level="m">As You Like It</title>, <title level="m">Comedy of Errors</title>, and <title level="m">Romeo and Juliet</title>. The contextual pages released with DSMP 1.0 are largely unchanged, except for some minor rewording in the metadata.</p>
  <p xml:id="douai_release_p6"><!-- Paragraph content here --></p>
</div>
Information to include in each set of release notes, with notes about who is responsible for writing the notes:
New additions to the anthology, written by the anthology lead(s)
New functionalities (if any), written by the LEMDO team if there have been improvements to LEMDO’s publication and processing
Corrections/changes to previously published contents, written by the anthology lead(s)
Intentional omissions (if any), written by the anthology lead(s) if the omissions pertain to content and by the LEMDO team if the omissions pertain to functionalities
Acknowledgements of (and/or credit to) the contributors and the release team. Anthology lead(s) will write most of this section; the LEMDO team will add a bit of information about the release team and any RAs who helped with the pre-freeze and freeze processes.
Use narrative paragraphs and/or lists as seems appropriate to the information you need to convey. Add links to new content if you wish. Here are some examples from already published anthologies:
MoMS’s Release Notes page (under the Preface menu)
QME’s Release Notes page (under the About menu)
DSMP’s Release Notes page (under the About menu)

staticSearch

LEMDO includes staticSearch (a fully functional, Endings-compliant search engine) in each anthology. A member of the LEMDO team will add an [anth]_search.xml file to your anthology’s about folder; this file generates a landing page (i.e., a search page) in your anthology with all the functionalities of staticSearch. Generally speaking, you will not need to make any changes to the search page.

User Guides

LEMDO has a standard user guide that we add to each anthology. You may make minor changes to some parts of your user guides, following the instructions in the LEMDO template for what to update and what to leave as it is. If your anthology has added features that are not mentioned in the user guide, you will want to add a section for each added feature.

About Pages that are Unique to Your Anthology

You will likely wish to add additional About pages, such as a page about your anthology, a mission statement, and/or an anthology history page. When deciding what you want to add, you may find it helpful to look at what our other published LEMDO anthologies have included in their anthology about pages by clicking through the options in their top navigation bars. For a list of our published anthologies, see the public LEMDO homepage.

Special Case: Anthology XML Pages

Each anthology has its own anthology XML page named [anth].xml, where [anth] is replaced by your anthology’s abbreviation (e.g., dre.xml). Your [anth].xml page has three functions:
To provide metadata for the anthology as a whole.
To provide the metadata and content for your anthology’s homepage.
To include editions for publication in your anthology.
The LEMDO team will create this file and set up its structure for you, but you will update and maintain it. If you have questions about how to update your [anth].xml file, contact the LEMDO team.
Your anthology XML file is different from the other XML files in your anthology and its editions. The anthology XML file is rooted not on the <TEI> element (as is the case in every other LEMDO TEI-XML file) but on a <teiCorpus> element. The <teiCorpus> element has a <teiHeader> element followed by a <TEI> element containing its own <teiHeader> and <text> children and a series of processing instructions:
<teiHeader> : This is the first of two <teiHeader> elements in your [anth].xml file. It gives the metadata for your anthology as a whole.
<TEI> : This is a standard <TEI> element that contains a <teiHeader> giving metadata for your anthology homepage and a <text> element that contains (in a child <body> element the content of your anthology homepage.
<?lemdo-import ref="doc:emd[ABBR]_edition"?>: This processing instruction is the mechanism by which an edition is included in your anthology. You will have one processing instruction for each edition.

Practice: Include Editions for Release

For each edition that you wish to include in your next anthology release, you will add a lemdo-import processing instruction to import the entire edition and all its files into your anthology. LEMDO’s processing instructions allow you to include content from elsewhere in the project; in this case, the lemdo-import processing instruction includes in your anthology build the edition file and all the files listed as <relatedItem> s in the edition file. To add the processing instruction:
Copy this instruction into the bottom of your anthology XML file after the closing </TEI> (as a child of <teiCorpus> ): <?lemdo-import ref="doc:emd[ABBR]_edition"?>.
Replace [ABBR] with the play ID of the edition that you wish to include. If you do not know the play ID, search for the play title in DRE Play IDs.

Further Reading

LEMDO’s Default Style

Rationale

LEMDO uses a standard shared stylesheet across all of our projects. Before you can start customizing your anthology’s styling, you (or your web designer) must understand LEMDO’s default styling so that you know which aspects of the styling are in your control. This documentation will guide you through the basics of LEMDO’s standard stylesheet.

Styling Basics

LEMDO’s general style includes a basic font and colour scheme. It also includes styling for a top navigation bar, hamburger menu, popout navigation panel, and footer. Although you can expect the overall functionality of your anthology to be standardized across the LEMDO platform, you may customize some aspects of your anthology’s appearance using CSS variables.
Variables are customizable values that make it easier to manage colours, fonts, and sizes across a website. LEMDO uses variables to determine some of our styling. The table below outlines variables that anthology leads may wish to change.
Variable LEMDO Default Style Description
primarySans Alegreya Sans The primary sans-serif font on your website
primarySerif Alegreya The primary serif font on your website
highlightColor 4 LEMDO blue (#009DFF) General highlight colour
highlightColorNotActive Light blue (#BFE0FF) Highlight colour for inactive links
highlightColorActive LEMDO blue (#009DFF) Highlight colour for active links
topnav-bg-color White (#FFFFFF) Background colour for the top navigation bar
topnav-border-color Titanium white (#E4E4E4) Border colour for the top navigation bar
topnav-bg-color-desktop White (#FFFFFF) Background colour for the top navigation bar on a laptop or desktop computer
mobile-toggler-color Medium grey (#565656) Font colour for the hamburger menu on mobile
topnav-searchfield-button-bg-color-active LEMDO blue (#009DFF) Background colour for the GO button when hovered
clicky-color-inactive-desktop Medium grey (#565656) Colour for dropdown menus on laptop or desktop computers
clicky-dropdown-inactive-desktop Medium grey (#565656) Colour for dropdown menu items on laptop or desktop computers
clicky-svg-inactive-desktop Medium grey (#565656) Colour for the arrow marker in an unclicked dropdown menu on laptop or desktop computers
leftNav-bg-color White (#FFFFFF) Background colour for the left navigation panel
leftNav-tabarea-bg-color White smoke (#EBEBEB) Background colour for the header area on the left navigation panel
leftNav-tab-color Medium grey (#565656) Font colour for tab items on the left navigation panel
leftNav-button-bg-color LEMDO blue (#009DFF) Background colour for the X button on the left navigation panel
leftNav-button-color White (#FFFFFF) Colour for the hamburger icon that activates the left navigation panel
leftNav-border-color Titanium white (#E4E4E4) Border colour for the left navigation menu
mainBgColor White (#FDFDFD) Background colour for the main content area of your website
offPageBgColor White smoke (#EBEBEB) Background colour for areas outside of the maximum page width
chainColorActive White (#FFFFFF) Colour for the chain icon when active (hovered)
footer-bg-color Platinum (#E7E7E7) Background colour for your website’s footer

Special Case: Modernized Texts

LEMDO has specific styling that applies to stage directions in modernized texts. For more detailed information on stage direction placement in modernized texts, see Stage Direction Rendering in Modernized Texts.

Special Case: Semi-Diplomatic Transcriptions

LEMDO also has specific styling for semi-diplomatic transcriptions intended to imitate common features in most early modern playbooks. For more detailed information on semi-diplomatic styling, see Default Style in Semi-Diplomatic Transcriptions.

Further Reading

Customize Your Anthology

This documentation is for anthology leads. For programmers and designers who are interested in the technical aspects of anthology customization, see Chapter 22. Programming.

Rationale

All LEMDO anthology websites inherit our functionality and style. Although your anthology website would be fully functional without any style customization, most anthology leads choose to make some modifications so that their anthology has a unique look and feel. Depending on the extent to which you want to customize your anthology site, you may need to hire a programmer and/or a web designer to support you.
This documentation will outline what you may modify for your anthology site, the principles that should guide your customizations, and information about when and how to hire a programmer or web designer.

What You Can Customize

All anthologies will customize:
Their logo.
Their favicon (the tiny image that appears beside the Web page name in browser tabs).
The number and names of items in the top navigation bar of their website (e.g., QME has About | Performance Editions | Production Records | Contexts in its top navigation bar, while MoMS has Preface | Introduction | Editions | Resources | Credits).
The drop-down menus under each top navigation item.
The credits and links in their website’s footer.
Additionally, some anthologies choose to customize:
The appearance of their banner/header.
The appearance of their top navigation bar.
Their colour palette.
The appearance of their footer.
The appearance of their side panels (i.e., the hamburger menu, the metadata pane, and the annotation/collation pane).
The font(s) that they use.
The splash image on their home page.
If you want to customize something not on this list such as adding extra interactions or functionalities, you must first consult with the LEMDO Project Director.

Principles for Customizing Your Anthology

All anthology customizations must follow LEMDO’s standards for Endings-compliance, accessibility, and overall functionality. In order to do that, your anthology must:
Customize using only HTML, Cascading Style Sheets (CSS), and JavaScript (JS).
Ensure that the top navigation bar and contents of the page are navigable by keyboard.
Ensure that colours have good contrast.
Not remove any functionality that comes with standard LEMDO anthology websites.

When and How to Hire a Developer

Most anthologies need to work with a developer to customize their functionality and appearance. The only cases where you do not need to work with a developer are if:
You are customizing only your logo, favicon, and navigation bar and you know basic HTML and CSS.
You meet all of the technical and competency requirements for LEMDO anthology developers and you have the time to devote to customizing your anthology’s appearance.
If you are not in either of those scenarios, then you should set aside funds to either hire a developer or work with a LEMDO developer.
We have developed a list of technical and competency requirements that you can use to create a job advertisement. All anthology developers must:
Know HTML and CSS/SCSS.
Have a computer that is able to run the required software. Practically speaking, this means they must use either a Linux or Mac operating system (Windows is not able to run required scripts).
Be willing and able to install and work with the software outlined in Software to be Installed Locally.
Like anyone working in the LEMDO repository, they will also need to install a Subversion client and check out the shared LEMDO repository.
If you want to customize your anthology’s functionalities as well as its style, your developer will also need to know JavaScript (JS).
If you want the LEMDO Director to look at the resumes of your top candidates, please ask. Your developer will have to work closely with the LEMDO Team, so we have a shared interest in hiring the right person.
Once you have hired someone, introduce them to the LEMDO team via email and let us know that this person has your permission to make changes to files in your anthology. We will help them apply for a UVic NetLink ID, point them to technical documentation written specifically for developers, and grant them permission to make changes to the required directories. Note that LEMDO will not grant that permission without your explicit instructions to do so.
You may also want to hire a graphic designer to make your logo, favicon, and banner, as well as pick your colour palette.

Decisions To Make Before Hiring A Developer

Before you hire your developer, you should have answers to the following questions ready:
What top-level menus do you want in your top navigation bar? Every anthology should have an About menu. Most will want to have an item for Plays. Look at other anthologies and other scholarly websites for examples.
What items do you want to appear under each top-level menu? For example, an About menu will probably have items like Team, Credits, Editorial Guidelines, and Contact Us. Each of these items will correspond to a page in your anthology. Think carefully about how you want to organize the information and resources in your anthology.
What would you like your logo to look like?
What would you like to see at the top of your page as a banner? Text? A picture? Both? A plain or textured colour?
What is the colour scheme of your anthology? If you do not have an idea yet, you might gather up some typical images from the period and from your project.

Notes

1.This abbreviation is also used as a prefix in your filenames. You will determine this abbeviation/prefix in collaboration with the LEMDO Director↑
2.Individual LEMDO team members who contribute substantially to editions should be acknowledged at the edition level and (if appropriate) at the level of files within editions.↑
3.If you wish to present release notes in reverse chronological order, note that you will have to renumber all the paragraphs in the file.↑
4.CSS variables follow American spelling conventions.↑

Prosopography

Janelle Jenstad

Janelle Jenstad is a Professor of English at the University of Victoria, Director of The Map of Early Modern London, and Director of Linked Early Modern Drama Online. With Jennifer Roberts-Smith and Mark Kaethler, she co-edited Shakespeare’s Language in Digital Media: Old Words, New Tools (Routledge). She has edited John Stow’s A Survey of London (1598 text) for MoEML and is currently editing The Merchant of Venice (with Stephen Wittek) and Heywood’s 2 If You Know Not Me You Know Nobody for DRE. Her articles have appeared in Digital Humanities Quarterly, Elizabethan Theatre, Early Modern Literary Studies, Shakespeare Bulletin, Renaissance and Reformation, and The Journal of Medieval and Early Modern Studies. She contributed chapters to Approaches to Teaching Othello (MLA); Teaching Early Modern Literature from the Archives (MLA); Institutional Culture in Early Modern England (Brill); Shakespeare, Language, and the Stage (Arden); Performing Maternity in Early Modern England (Ashgate); New Directions in the Geohumanities (Routledge); Early Modern Studies and the Digital Turn (Iter); Placing Names: Enriching and Integrating Gazetteers (Indiana); Making Things and Drawing Boundaries (Minnesota); Rethinking Shakespeare Source Study: Audiences, Authors, and Digital Technologies (Routledge); and Civic Performance: Pageantry and Entertainments in Early Modern London (Routledge). For more details, see janellejenstad.com.

Joey Takeda

Joey Takeda is LEMDO’s Consulting Programmer and Designer, a role he assumed in 2020 after three years as the Lead Developer on LEMDO.

Mahayla Galliford

Project manager, 2025-present; research assistant, 2021-present. Mahayla Galliford (she/her) graduated with a BA (Hons with distinction) from the University of Victoria in 2024. Mahayla’s undergraduate research explored early modern stage directions and civic water pageantry. Mahayla continues her studies through UVic’s English MA program and her SSHRC-funded thesis project focuses on editing and encoding girls’ manuscripts, specifically Lady Rachel Fane’s dramatic entertainments, in collaboration with LEMDO.

Martin Holmes

Martin Holmes has worked as a developer in the UVic’s Humanities Computing and Media Centre for over two decades, and has been involved with dozens of Digital Humanities projects. He has served on the TEI Technical Council and as Managing Editor of the Journal of the TEI. He took over from Joey Takeda as lead developer on LEMDO in 2020. He is a collaborator on the SSHRC Partnership Grant led by Janelle Jenstad.

Navarra Houldin

Training and Documentation Lead 2025–present. LEMDO project manager 2022–2025. Textual remediator 2021–present. Navarra Houldin (they/them) completed their BA with a major in history and minor in Spanish at the University of Victoria in 2022. Their primary research was on gender and sexuality in early modern Europe and Latin America. They are continuing their education through an MA program in Gender and Social Justice Studies at the University of Alberta where they will specialize in Digital Humanities.

Sofia Spiteri

Sofia Spiteri is currently completing her Bachelor of Arts in History at the University of Victoria. During the summer of 2023, she had the opportunity to work with LEMDO as a recipient of the Valerie Kuehne Undergraduate Research Award (VKURA). Her work with LEMDO primarily includes semi-diplomatic transcriptions for The Winter’s Tale and Mucedorus.

Tracey El Hajj

Junior Programmer 2019–2020. Research Associate 2020–2021. Tracey received her PhD from the Department of English at the University of Victoria in the field of Science and Technology Studies. Her research focuses on the algorhythmics of networked communications. She was a 2019–2020 President’s Fellow in Research-Enriched Teaching at UVic, where she taught an advanced course on Artificial Intelligence and Everyday Life. Tracey was also a member of the Map of Early Modern London team, between 2018 and 2021. Between 2020 and 2021, she was a fellow in residence at the Praxis Studio for Comparative Media Studies, where she investigated the relationships between artificial intelligence, creativity, health, and justice. As of July 2021, Tracey has moved into the alt-ac world for a term position, while also teaching in the English Department at the University of Victoria.

Metadata

Authority title Chapter 20. Anthology Customization
Type of text Documentation
Publisher Linked Early Modern Drama
Series
Source
Editorial declaration
Edition
Encoding description
Document status prgGenerated
License/availability