<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="228" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://com395.omeka.chass.ncsu.edu/items/show/228?output=omeka-xml" accessDate="2026-07-11T20:56:50+00:00">
  <fileContainer>
    <file fileId="228">
      <src>https://com395.omeka.chass.ncsu.edu/files/original/57c89df31379419b048736a39b697c5a.png</src>
      <authentication>b30de290c7e9e56556ed27a55e03c120</authentication>
    </file>
  </fileContainer>
  <collection collectionId="11">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1501">
                <text>Digital Artifacts</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1502">
                <text>Designed Digital Interfaces and Devices</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1503">
                <text>This collection is various designed digital devices. This is a rather broad category. The intent is to capture the scope of design in digital space from a variety of perspectives.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1504">
                <text>Students of COM/ENG 395</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1505">
                <text>Students of COM/ENG 395</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="6">
    <name>Still Image</name>
    <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1497">
              <text>Monticello Website</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1498">
              <text>Digital Artifacts</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1499">
              <text>Emma Moore</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="1500">
              <text>Emma Moore</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1615">
              <text>This is a screenshot of the homepage of the Monticello website. I find the homepage very overwhelming. While it is neatly organized in distinct, differently-colored sections, each of the seven sections take up the entire screen and to get to the bottom, you have to pass through so much information it can become overwhelming. However, I think the creators of the page were trying to fit all the greatest hits from each menu item into one page. Their goal is for something, anything, to hook you. If any of them do and you want to see more, each corresponding menu link takes you to that page. The nested pages are much less sophisticated. There is a navigation tree to the left, allowing you to jump down the pages and to different sections within that nested page. Those pages are expressly for the user who intentionally wanted to know about that specific topic, not someone who came to browse. The Monticello website is also a marketing tool. The website is a stepping stone to the grounds, so its main goal is to convince visitors to make the trip to Monticello, even if (and especially when) planning the trip was not the main reason for visiting the site. It is well known in today’s world that “good graphic design is a highly efficient way of communicating a marketing message visually” (Towers, Omnific Design). The muted colors are meant to be visually pleasing in order to foster a feeling of peace and suggest to visitors that the grounds will give them that same feeling.</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
