<node id="429351">
  <nid>429351</nid>
  <type>news</type>
  <uid>
    <user id="27244"><![CDATA[27244]]></user>
  </uid>
  <created>1438183584</created>
  <changed>1475896755</changed>
  <title><![CDATA[Fresh, Local, Sustainable: Georgia Tech Dining Services]]></title>
  <body><![CDATA[<p>As part of our campus-wide commitment to provide quality, value, and convenience to the Georgia Tech community, Dining Services officially unveiled our new branding at the Class of 2019 Freshman Orientation sessions. Our new branding, which will be used on all marketing pieces and signage across campus, as well as both the Dining Services website and Meal Plan website, embraces our culinary program, which is centered around fresh, local, and sustainable cuisine.</p><p>The three pillars of our culinary program each incorporate a distinct, important piece of our value proposition on the Georgia Tech campus, and represent larger re-branding of our organization. Our food is fresh, from the salsa, pico de gallo, guacamole, and salad dressings across campus, to our newly established fresh pastry and dessert programs at our Community Restaurants, inspired by our Campus Pastry Chef. Our ingredients are local, from the hydroponic Bibb lettuce sourced from the Georgia Tech Dining Services greenhouse at R&amp;G Farm in Dublin, GA to the grass-fed Angus Beef burgers that we serve from Cox Family Farms from Florence, Alabama. And our program is sustainable, from our locally sourced produce to our responsibly sourced cage-free eggs, and the Mindful options that we offer across the Georgia Tech campus.</p><p>Our community has made it clear that they want quality, value, and convenience in their foodservice provider, and Georgia Tech Dining Services is here to answer that call with our fresh, local, and sustainable culinary program. To learn more about out our program, visit <a href="http://www.gatechdining.com/">www.gatechdining.com</a>.</p>]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2015-07-29T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[As part of our campus-wide commitment to provide quality, value, and convenience to the Georgia Tech community, Dining Services officially unveiled our new branding at the Class of 2019 Freshman Orientation sessions.]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_media>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <!--  TO DO: correct to not conflate categories and news room topics  -->
  <!--  Disquisition: it's funny how I write these TODOs and then never
         revisit them. It's as though the act of writing the thing down frees me
         from the responsibility to actually solve the problem. But what can I
         say? There are more problems than there's time to solve.  -->
  <links_related> </links_related>
  <files> </files>
  <og_groups>
          <item>1298</item>
      </og_groups>
  <og_groups_both>
      </og_groups_both>
  <field_categories>
      </field_categories>
  <core_research_areas>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>1298</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Parent and Family Programs]]></item>
      </og_groups_both>
  <field_keywords>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
