For over 20 years the web has provided continuous deluge of cultural production. Digital artifacts such as websites, images, and videos have much to communicate about our social and cultural evolution, and yet their messages or moments can be fleeting or quickly lost. Both the accessibility and longevity of digital content are subject to a wide range of risks, from technological obsolescence to outright deletion by their creator or host. So what is being done to preserve these cultural objects for the long term? Approaching web content from a cultural and artistic perspective, this panel will convene leading writers, archivists, thinkers and technologists to discuss to the questions, challenges, and imperatives involving preserving the creative culture of the web. We’ll cover topics like "what is the long-term significance of a website, and why would it be worth preserving?", "should web sites and artifacts be treated like works of art or architecture?", and "how do we go about archiving digital content to ensure its accessibility and longevity?". Example initiatives to be discussed will be the Archive Team’s various projects (such as the Geocities torrent), the Internet Archive’s Wayback Machine, Internet Archeology, and the Rhizome ArtBase. This panel will be presented by Rhizome, an organization dedicated to the creation, presentation, preservation, and critique of emerging artistic practices that engage technology.
Tagged with “sxswi” (2)
In the early days of CSS the web industry cut its teeth on blogs and small personal sites. Much of the methodology still considered best-practise today originated from the experiences of developers working alone, often on a single small style sheet, with few of the constraints that come from working with large distributed teams on large continually changing web projects.
The mechanics of CSS are relatively simple. But creating large maintainable systems with it is still an unsolved problem. For larger sites, CSS is a difficult and complex component of the codebase to manage and maintain. It’s difficult to document patterns, and it’s difficult for developers unfamiliar with the code to contribute safely.
How can we do better? What are the CSS best practises that are letting us down and that we must shake off? How can we take a more precise, structured, engineering-driven approach to writing CSS to keep it bug-free, performant, and most importantly, maintainable?