<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Technical Blog</title>
    <link>https://grep.elasticpath.com/community/techblog/blog</link>
    <description />
    <pubDate>Fri, 08 Jan 2010 23:16:17 GMT</pubDate>
    <generator>Clearspace 2.5.7 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2010-01-08T23:16:17Z</dc:date>
    <item>
      <title>Targeted Selling for the Masses: Extending and Configuring</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2010/01/15/targeted-selling-for-the-masses-extending-and-configuring</link>
      <description>Targeted Selling is Elastic Path's personalization engine. It collects data about the shopper from various sources and exposes it for rule-based conditional evaluation. In Elastic Path, this is done via Business User rule configurations. The underlying</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">customization</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">custom</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">tagging_framework</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">tags</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">targeted_selling</category>
      <pubDate>Fri, 15 Jan 2010 17:00:01 GMT</pubDate>
      <author>andrew.lau@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2010/01/15/targeted-selling-for-the-masses-extending-and-configuring</guid>
      <dc:date>2010-01-15T17:00:01Z</dc:date>
      <clearspace:dateToText>2 years, 1 month ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/targeted-selling-for-the-masses-extending-and-configuring</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1093</wfw:commentRss>
    </item>
    <item>
      <title>Case Study - Upgrading Elastic Path - 6.0 to 6.1</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2009/06/16/case-study--upgrading-elastic-path--60-to-61</link>
      <description>Background &amp;nbsp; Our client's e-commerce store has been powered by Elastic Path for well over a year now. Our team started development of the store on a beta version of Elastic Path 6.0 in January 2008. After 3 months of development, including a merge</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">6.0</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">6.1</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">upgrade</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">custom</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">subversion</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">case_study</category>
      <pubDate>Tue, 16 Jun 2009 22:21:32 GMT</pubDate>
      <author>eddie.chan@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2009/06/16/case-study--upgrading-elastic-path--60-to-61</guid>
      <dc:date>2009-06-16T22:21:32Z</dc:date>
      <clearspace:dateToText>2 years, 7 months ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/case-study--upgrading-elastic-path--60-to-61</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1068</wfw:commentRss>
    </item>
    <item>
      <title>Upgrading Customized EP Code using Vendor Branches</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2009/03/16/upgrading-customized-ep-code-using-vendor-branches</link>
      <description>Alternative title: How to Make Your Life Easier and Not Go Bald from Pulling Your Hair out Trying to Keep Current on a Constantly Evolving and Shifting Codebase &amp;nbsp; This is probably the biggest and most avoided question from all of our successfully</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">upgrade</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">customization</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">custom</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">subversion</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">perforce</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">source_control</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">vendor_branch</category>
      <pubDate>Tue, 17 Mar 2009 01:13:55 GMT</pubDate>
      <author>andrew.lau@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2009/03/16/upgrading-customized-ep-code-using-vendor-branches</guid>
      <dc:date>2009-03-17T01:13:55Z</dc:date>
      <clearspace:dateToText>2 years, 11 months ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/upgrading-customized-ep-code-using-vendor-branches</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1048</wfw:commentRss>
    </item>
    <item>
      <title>Adding Custom Settings with the EP6.1 Settings Framework</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2009/01/20/adding-custom-settings-with-the-ep61-settings-framework</link>
      <description>Elastic Path 6.1 provides a new way to manage your application configuration. In the past, settings were stored in a variety of places throughout the system; some were in XML files, others were in properties files, and still others were stored in</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">database</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">6.1</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">configuration</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">api</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">value</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">custom</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">setting</category>
      <pubDate>Tue, 20 Jan 2009 19:39:55 GMT</pubDate>
      <author>daniel.wu@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2009/01/20/adding-custom-settings-with-the-ep61-settings-framework</guid>
      <dc:date>2009-01-20T19:39:55Z</dc:date>
      <clearspace:dateToText>3 years, 2 weeks ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/adding-custom-settings-with-the-ep61-settings-framework</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1024</wfw:commentRss>
    </item>
  </channel>
</rss>


