<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by Stephan Kvart</title><link href="http://world.optimizely.com" /><updated>2011-03-11T09:29:15.0000000Z</updated><id>https://world.optimizely.com/blogs/Stephan-Kvart/</id> <generator uri="http://world.optimizely.com" version="2.0">Optimizely World</generator> <entry><title>An EPiServer developer&#39;s introduction to the Umbraco Document API</title><link href="http://blog.bigfinger.se/2011/3/11/an-episerver-developers-introduction-to-the-umbraco-document-api.aspx" /><id>
When working with EPiServer we&#39;re used to having a single class
to work with (if not using PageTypeBuilder), the PageData class. At
first glance it&#39;s equivalent in Umbraco is the Document class, but
after looking closer you&#39;ll see that there is one enormously
important difference, caching.

In EPiServer, we get all PageData objects from the DataFactory,
since EPiServer implements a factory
pattern. It&#39;s also implemented as a singleton, making it
very simple to interact with. We get the page ...</id><updated>2011-03-11T09:29:15.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>An EPiServer developer&#39;s introduction to the Umbraco UI</title><link href="http://blog.bigfinger.se/2011/3/6/an-episerver-developers-introduction-to-the-umbraco-ui.aspx" /><id>

Both CMS&#39;s, of course, comes with an administration
interface. I&#39;ll assume that you are familliar with the EPiServer
OnlineCenter Dashboard, and the EPiServer CMS Edit- and
Admin-modes. However, if you&#39;re an Umbracian, I suppose you can
imagine, and get the general idea of how EPiServer is laid out.
Again, this comparison is not intended to establish which CMS is
better, but to serve as a translation of sorts, between the two
systems, to get you, as an EPiServer developer, started with
Umbr...</id><updated>2011-03-06T22:39:34.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>An introduction to Umbraco for EPiServer-developers. Or vice-versa.</title><link href="http://blog.bigfinger.se/2011/3/1/an-introduction-to-umbraco-for-episerver-developers-or-vice-versa.aspx" /><id>

This is the first part in a series introducing Umbraco to
EPiServer developers, however, it can also be seen as an
introduction to EPiServer for Umbraco developers. It all depends on
your perspective. Please keep in mind that this is not an attempt
at comparing the two for the sake of which is better, and I do not
make the argument for either platform. Both have their pro&#39;s and
con&#39;s, but I leave it up to you to select the platform that best
suits your needs and requirements.





In my exp...</id><updated>2011-03-01T15:58:34.0000000Z</updated><summary type="html">Blog post</summary></entry></feed>