<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by Arve Systad</title><link href="http://world.optimizely.com" /><updated>2017-03-09T21:08:45.0000000Z</updated><id>https://world.optimizely.com/blogs/Arve-Systad/</id> <generator uri="http://world.optimizely.com" version="2.0">Optimizely World</generator> <entry><title>Epinova.JsResourceHandler open sourced!</title><link href="https://www.epinova.no/en/blog/epinova.jsresourcehandler-open-sourced/" /><id>Writing client side applications in your Episerver-solutions, and creating custom localization functionality in the front end? Why not use what Episerver already has?</id><updated>2017-03-09T21:08:45.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Missing images when importing from inRiver PIM to Episerver</title><link href="https://www.epinova.no/en/blog/pim-episerver-missing-images/" /><id>Missing wildcard hostname mapping might make the inRiver connector fail when importing resources.</id><updated>2017-02-21T08:56:32.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Missing images when importing from inRiver PIM to Episerver</title><link href="https://www.epinova.no/en/blog/pim-episerver-missing-images/" /><id>Missing wildcard hostname mapping might make the inRiver connector fail when importing resources.</id><updated>2017-02-21T08:56:32.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Breaking changes with inRiver PIM</title><link href="https://www.epinova.no/en/blog/breaking-changes-when-upgrading-inriver-pim-using-episerver-connector/" /><id>If you&#39;re using inRiver PIM with the Episerver connector, and upgrading the PIM system from 6.2 to 6.3, there&#39;s a breaking change you should be aware of, that could potentially make products on your page invisible.</id><updated>2017-02-16T20:11:44.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Epinova.Associations open sourced!</title><link href="https://www.epinova.no/en/blog/epinova.associations-open-sourced/" /><id>Having two-way-relationships between content is a common scenario on the web today. Automatically linking from each end of the relationship to the other. We&#39;ve composed our own, very simple module to do this - and it&#39;s now open sourced!</id><updated>2017-02-01T21:12:40.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Making awesome distributable packages</title><link href="https://www.epinova.no/en/blog/making-awesome-distributable-packages/" /><id>Many companies set up their own, internal package feeds these days, in addition to all the public ones out there. To create awesome packages, there are a few things you should keep in mind.</id><updated>2016-11-12T21:50:55.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Clean views with UIHints</title><link href="https://www.epinova.no/en/blog/clean-views-with-uihints/" /><id>Simple lists of label-value-pairs on information pages often result in cluttered views. Tidy those up drastically with some simple UIHint-magic.</id><updated>2016-08-26T21:09:47.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>A Letter to Episerver</title><link href="https://world.optimizely.com/blogs/Arve-Systad/Dates/2016/4/a-letter-to-episerver/" /><id>&lt;p&gt;I have followed you for more than five years now. Things have happened in those five years; as with the rest of internet technology. I like you, but you are not without flaws. You improve over time, but some things, sadly, remain untouched.&lt;/p&gt;
&lt;p&gt;https://www.epinova.no/en/blog/a-letter-to-episerver/&lt;/p&gt;</id><updated>2016-04-28T23:19:12.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Creating custom form elements in Episerver.Forms</title><link href="https://www.epinova.no/en/blog/creating-custom-form-elements-in-episerver.forms/" /><id>With the new Episerver.Forms, you get the opportunity to create your own form elements, which vastly extends the use case for them.</id><updated>2016-01-12T10:44:09.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Custom data feeds in Episerver.Forms</title><link href="https://www.epinova.no/en/blog/custom-data-feeds-in-episerver.forms/" /><id>In the new Episerver.Forms, you can control data sources for selection form elements through code. Here&#39;s how.</id><updated>2016-01-11T15:24:41.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Could not load Microsoft.Reporting.RdlCompile in TeamCity after updating to Visual Studio 2015</title><link href="http://www.epinova.no/blog/arve-systad/dates/2015/7/could-not-load-microsoftreportingrdlcompile-in-teamcity-after-updating-to-visual-studio-2015/" /><id>After upgrading the build runner to use VS2015, it could no longer find this assembly.</id><updated>2015-07-23T12:14:40.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Container pages, and why you shouldn&#39;t use them</title><link href="http://www.epinova.no/blog/arve-systad/dates/2015/6/container-pages-and-why-you-shouldnt-use-them/" /><id>Container pages without a template has been a concept in the EPiServer community for a long time. And I&#39;ve always hated them. Here&#39;s why.</id><updated>2015-06-16T00:37:18.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Quality Assurance Checklists for EPiServer projects</title><link href="http://www.epinova.no/blog/arve-systad/dates/2015/3/quality-assurance-checklists-for-episerver-projects/" /><id>Here are the quality assurance checklists (for backend + commerce) we use, as promised on the meetup we had in our offices at March 3rd, 2015. I have removed items that are specific to our internal company infrastructure and software, replacing th...</id><updated>2015-03-03T20:30:10.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>EPiServer Commerce essentials 6: Project set up and infrastructure</title><link href="http://www.epinova.no/blog/arve-systad/dates/2014/12/episerver-commerce-essentials-6-project-set-up-and-infrastructure/" /><id>Compared to normal CMS projects, there will be a few key differences in your Visual Studio solution, and a some things you need to think about while organising your code.</id><updated>2014-12-02T17:57:19.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>EPiServer Commerce essentials 5: Search, performance and analytics</title><link href="http://www.epinova.no/blog/arve-systad/dates/2014/11/episerver-commerce-essentials-5-search-performance-and-analytics/" /><id>When creating an e-commerce site, it&#39;s important to give your customer relevant content. Good search capabilities and responsiveness are key features in delivering a good experience.</id><updated>2014-11-24T16:18:32.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>Part 4: Importing from external systems</title><link href="http://www.epinova.no/blog/arve-systad/dates/2014/11/episerver-commerce-essentials-4-import-from-external-systems/" /><id>Importing data from legacy or third party systems is very often a requirement when building a Commerce site. This should greatly affect your planning and estimates.</id><updated>2014-11-10T21:19:05.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>EPiServer Commerce essentials 3: Markets, currencies and localization</title><link href="http://www.epinova.no/blog/arve-systad/dates/2014/10/episerver-commerce-essentials-3-markets-currencies-and-localization/" /><id>After deciding on your products, payment and shipping options, it’s time to think about who to sell to.</id><updated>2014-10-28T23:25:32.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>EPiServer Commerce essentials 2: Payment, shipping and inventory</title><link href="http://www.epinova.no/blog/arve-systad/dates/2014/10/episerver-commerce-essentials-2-payment-shipping-and-inventory/" /><id>After products, the next critical requirement for any e-commmerce site are payment and shipping. You might also need to handle inventory.</id><updated>2014-10-24T21:14:48.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>EPiServer Commerce project essentials 1: Product knowledge</title><link href="http://www.epinova.no/blog/arve-systad/dates/2014/10/episerver-commerce-project-essentials-1-product-knowledge/" /><id>Your products are the foundation for any e-commerce site. Without them, the site would be pointless. Get to know the details of the products.</id><updated>2014-10-22T00:06:56.0000000Z</updated><summary type="html">Blog post</summary></entry> <entry><title>EPiServer Commerce project essentials</title><link href="http://www.epinova.no/blog/arve-systad/dates/2014/10/episerver-commerce-project-essentials/" /><id>EPiServer Commerce projects are by nature more complex than pure CMS projects. In this blog series I will dive into essential concepts that will help you plan and estimate EPiServer Commerce projects. </id><updated>2014-10-22T00:05:31.0000000Z</updated><summary type="html">Blog post</summary></entry></feed>