> 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-1-and-2/twitter.md). # Using Twitter After our first class, you should have signed up for a Twitter account and integrated it into our [Slack](https://digitalarchiving.slack.com), so that we will be able to find one another easily. When you tweet about the class, you should use a #hashtag (that we decide on together to represent the class) to ensure we're in dialogue with one another. You might be asking why we're using Twitter. Our goal in using Twitter is, in part, to get you used to communicating as an academic outside the classroom/ outside the university. Also, Twitter allows us to offer evidence of the hard work you're doing in the classroom (and doesn't everyone want to see more pictures of medieval manuscripts?). Thirdly, Twitter allows you to join a larger community of scholars and interested laypeople (as well as potential critics). Twitter thus has the potential to be productive and informative (learning about new people, ideas and resources), interactive (talking with other experts in the field) and fun (doesn't everyone want to create new memes about medieval manuscripts?). **Expectations**: 1. everyone set up a Twitter account and adds all class members to their circle, as well as a few more professionals in manuscripts studies/ DH. These latter follows can be drawn from my existing twitter list. 2. at minimum students will tweet 2-3 times in weeks 2 and 3 of the course, and then more occasionally thereafter. 3. students should remember that Twitter is a public forum and thus should show suitably professional decorum 4. in your work, Twitter might be a key part of your research process. By using Zotero (which the professor can see) or Twitter bookmarks (which the professor cannot), keep track of posts that you find intriguing, thought-provoking or simply amusing. You might want to cite some tweets in your bibliographies, blog posts or in class discussions. 5. Bring up Tweets in class. If Twitter has given you some information or highlighted some new resource, let other people know in person and post links on Twitter/ Slack. These guidelines are developed from suggestions made in Joanna Dunlap and Patrick Lowenthal, "Tweeting the night away: Using Twitter to enhance social presence." *Journal of Information Systems Education*, 20.2 (2009). --- # 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-1-and-2/twitter.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.