> For the complete documentation index, see [llms.txt](https://medievalbook.gitbook.io/digitizing-medieval-archives/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://medievalbook.gitbook.io/digitizing-medieval-archives/master.md). # Introduction Welcome, HIST4006-ers! This resource is intended to guide students through the exercises for learning about digitizing medieval manuscripts. Over the course of the year, we will be learning terminology, how to use different kinds of digital tools as well as picking up a basic sense of how to think about/ describe medieval material. The sidebar organizes material week by week so this guide should act as a kind of calendar for exercises to be done after/ for class. A rough overview of what we're doing this year follows this page, but generally the class develops as follows. We'll start by talking about a few platforms we'll be using this year (Twitter, Humanities Commons, Github) and then by week five we'll start playing with our medieval sources – a task which will occupy the rest of the first term. In the second term, we'll continue to explore digital tools and try to understand the different ways we are able to make digital surrogates of medieval manuscripts. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://medievalbook.gitbook.io/digitizing-medieval-archives/master.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.