Understanding our Interface
TEI-Boilerplate
We display our TEI-encoded files using TEI-Boilerplate, a customizable interface developed by Dr. John Walsh and a team at Indiana University.
Our installation of TEI Boilerplate resides on server space hosted by Reclaim Hosting and managed by the Center for Instruction and Research Technology (CIRT) at UNF.
How It Works
TEI-Boilerplate turns our XML files into web pages by building an HTML wrapper around them (HTML is the language used to write web pages). It does so by using XSLT (the stylesheet/transformation language for XML), CSS (the stylesheet language for HTML), and javascript (a programming language).
Our adaptation of TEI-Boilerplate allows us to view our files three views:
- When displaying the transcription view, the interfaces uses a CSS stylesheet that styles output as close as possible to the original, using the elements on Representing the Text. The stylesheet also selects the values for <sic>, <orig> and <abbr> elements within the <choice> element.
- When displaying the reading text view, the interface uses a different CSS stylesheet to format output in a more standardized fashion, disregarding many of the elements on Representing the Text, and selecting the values for <corr>, <reg>, and <expand> elements within the <choice> element.
- When displaying the "intermediate" view, the interfaces uses a different CSS stylesheet that displays the formatting of the text as in the "edition" view, but showing both sets of values (<orig> and <reg>, for example) within a choice element.
In we wanted to create other ways of viewing the text, we could develop new CSS stylesheets and update the XSLT behind the interface to add those new views into the selector box.
How TEI-Boilerplate is Structured
TEI-Boilerplate consists of a directory of files. These are divided into different folders:
- build_tools
- css
- content
- images
- jss
You will deal with only the "content" and "images," where you will place your XML file(s) and image files, respectively.