> 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/week-13.md).

# Week 13 - The Theory of the Digital

What is the difference between a manuscript and a digital version of it? This class welcomes students back from break and begins our focus on digitization in earnest. Our first question should be, what makes a digital project, digital? When we turn a manuscript into 1's and 0's, what do we do to it? What do we gain, or lose?&#x20;

This class is largely debate, discussion and brainstorming of [this week's readings](https://medievalbook.gitbook.io/digitizing-medieval-archives/~/drafts/-LV9QO5ZkrjBsV-qnO7l/primary/readings#13-the-theory-of-the-digital). If we have time, we will look at Github's project management tools.&#x20;


---

# 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/week-13.md?ask=<question>&goal=<endgoal>
```

`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.
