Nothing could be more clear than the fact that the web is built from “small pieces loosely joined,” in David Weinberger’s classic phrase. This week we discuss the digital pieces (concentrating on text and images), the hyperlinks that join them, and the resulting network. This network structure has implications for the ways that we present history and cite sources, the ways that others find and consume our work, and the ways that careers are made (or not).
- Anderson, “The Long Tail,” Wired 12, no. 10 (October 2004).
- Ayers, “History in Hypertext,” (1999).
- Barringer, “A Scanner and a Mission,” AIGA.org (5 June 2007).
- Berners-Lee, “Linked Data,” W3.org (18 June 2009).
- Bilton, “Erasing the Digital Past,” New York Times (1 April 2011).
- Cohen, “Digital History: The Raw and the Cooked,” Rethinking History 8, no. 2 (June 2004).
- Crane and Jones, “Text, Information, Knowledge and the Evolving Record of Humanity,” D-Lib Magazine 12, no. 3 (March 2006).
- Darnton, “The New Age of the Book,” The New York Review of Books 46, no. 5 (18 Mar 1999).
- Farid, “Photo Tampering throughout History,” FourandSix.com (2011).
- Kraus, “When Data Disappears,” New York Times (6 August 2011).
- Krause, “Discovery Through Digitization,” Slant of Light (23 April 2011).
- Landrum, “Camera, Laptop, and What Else? Hacking Better Tools for the Short Archival Research Trip,” Cliotropic (19-20 February 2010).
- Posner, “Batch-Processing Photos from Your Archive Trip,” (5 March 2011).
- Shirky, “Power Laws, Weblogs, and Inequality,” Clay Shirky’s Writings about the Internet (10 February 2003).
- Sullivan, “When OCR Goes Bad: Google’s Ngram Viewer and the F-Word,” Search Engine Land (19 December 2010).
This assignment comes in three flavours.
- If you don’t know HTML. For this assignment you are going to create a simple webpage to publicize yourself. There are a number of ways that you can do this without learning any new technical skills. At Google Sites, for example, you can create quite a sophisticated website without using any HTML at all. Tools like Dreamweaver or Expression Web will create HTML for you, which you can then upload to a web server. This convenience comes at a price. The automatically generated code is often baroque, and, since you didn’t know how to create it in the first place, you aren’t going to have much hope of maintaining it or fixing bugs. So we’re going to go old school instead. Start by working through the W3 Schools HTML tutorial. When you are finished, create a new index.html file and include the following information, marked up in a way that appeals to you: name, contact information, link to your blog and Twitter feed, previous experience, related skills, and your research / public history interests. E-mail the index.html file to me and write a brief blog post about your experiences with markup.
- If you know some HTML but haven’t tried CSS. Make a quick personal webpage for yourself (as in the above version of the assignment) using basic HTML. Next work through the W3 Schools CSS tutorial. When you are finished, edit your index.html file to read from an external style file called style.css, then edit the style.css file to create styles that make your web page look the way you want. If you get very ambitious, you might try working with floating elements. See the Floatutorial for more information. (N.B. This is strictly optional). As before, e-mail me your index.html and style.css files and write a brief blog post about what you did.
- If you already know HTML and CSS. Solve a problem of your choice using digital or computational techniques, and blog about the problem and how you solved it. E-mail me if you need some suggestions; the Posner blog post on batch processing photos is a good example of what you should be aiming for.