<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gary Wenneker's Blog</title>
    <description>Thoughts, stories and ideas</description>
    <link>/</link>
    <atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
    <pubDate>Mon, 22 Sep 2025 11:02:52 +0000</pubDate>
    <lastBuildDate>Mon, 22 Sep 2025 11:02:52 +0000</lastBuildDate>
    <generator>Jekyll v3.10.0</generator>
    
      <item>
        <title>Sitecore JSS: React Hooks Global State</title>
        <description>&lt;p&gt;When developing in Sitecore JSS I am always happy to do that in React. Most of the React components I’ve been building are small ones, rendering the context of that data. That’s not special at all and for this I use the React &lt;a href=&quot;https://reactjs.org/docs/components-and-props.html#function-and-class-components&quot;&gt;Function Component&lt;/a&gt;. It has no side effects. Where &lt;a href=&quot;https://reactjs.org/docs/components-and-props.html#function-and-class-components&quot;&gt;Class Components&lt;/a&gt; has &lt;a href=&quot;https://reactjs.org/docs/state-and-lifecycle.html&quot;&gt;state&lt;/a&gt; and livecycle methods the Function Component has not. This means the Function Component only renders the markup.&lt;/p&gt; &lt;blockquote&gt; &lt;p&gt;Previously, refs were only supported for Class-based components. With the advent of React Hooks, that’s no longer the case&lt;/p&gt; &lt;/blockquote&gt; &lt;h2 id=&quot;common-issues-with-react&quot;&gt;Common issues with...</description>
        <pubDate>Fri, 14 Feb 2020 07:21:12 +0000</pubDate>
        <link>/sitecore-jss-react-hooks-global-state/</link>
        <guid isPermaLink="true">/sitecore-jss-react-hooks-global-state/</guid>
        
        <category>sitecore</category>
        
        <category>react</category>
        
        <category>state</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>SpotiTube: Using GraphQL in Sitecore JSS</title>
        <description>&lt;blockquote&gt; &lt;p&gt;Talk data to me!&lt;/p&gt; &lt;/blockquote&gt; &lt;p&gt;&lt;img src=&quot;/assets/img/uploads/2019/07/image-11.png&quot; alt=&quot;&quot; /&gt;&lt;/p&gt; &lt;p&gt;Working with JSS is a growing thing and more and more sites are built with Sitecore’s headless technology. It allows you to build application based websites with an enormous speed something unknown in the world of “classic” ASP.NET MVC development. This post is about a sample application I build to show how GraphQL can be used in Sitecore Javascript Services.&lt;/p&gt; &lt;p&gt;For this demo I created a Spotify Web front end and attached a GraphQL backend to it. This app will not use any Sitecore items but it rather consumes the...</description>
        <pubDate>Fri, 19 Jul 2019 07:21:12 +0000</pubDate>
        <link>/spotitube-using-graphql-in-sitecore-jss/</link>
        <guid isPermaLink="true">/spotitube-using-graphql-in-sitecore-jss/</guid>
        
        <category>jss</category>
        
        <category>sitecore</category>
        
        <category>graphql</category>
        
        <category>nodejs</category>
        
        <category>reactjs</category>
        
        <category>nvm</category>
        
        <category>git</category>
        
        <category>css</category>
        
        <category>headless</category>
        
        <category>cms</category>
        
        <category>typescript</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Sitecore JSS Adal Authentication</title>
        <description>&lt;p&gt;When it comes to providing a login for the visitors of your website a lot needs to be done. With Sitecore JavaScript Services we are now entering a whole new ball game.&lt;br /&gt; This post will focus on implementing Microsoft Azure’s ADAL. I also shared the &lt;a href=&quot;https://github.com/GaryWenneker/jss-adal&quot;&gt;JSS template&lt;/a&gt; which allows you to start with the ADAL connected JSS site immediately.&lt;/p&gt; &lt;h3 id=&quot;what-is-adal&quot;&gt;What is ADAL&lt;/h3&gt; &lt;blockquote&gt; &lt;p&gt;&lt;em&gt;The Windows Azure Authentication Library (ADAL) is a library meant to help developers to take advantage of Active Directory for enabling client apps to access protected resources.&lt;/em&gt;&lt;/p&gt; &lt;/blockquote&gt; &lt;h3 id=&quot;setting-up-your-azure-configuration&quot;&gt;Setting up your Azure configuration&lt;/h3&gt;...</description>
        <pubDate>Thu, 23 May 2019 07:21:12 +0000</pubDate>
        <link>/sitecore-jss-adal-authentication/</link>
        <guid isPermaLink="true">/sitecore-jss-adal-authentication/</guid>
        
        <category>jss</category>
        
        <category>sitecore</category>
        
        <category>graphql</category>
        
        <category>nodejs</category>
        
        <category>reactjs</category>
        
        <category>headless</category>
        
        <category>cms</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Sitecore JSS: Umbrella Update 2</title>
        <description>&lt;p&gt;A few weeks ago I released &lt;a href=&quot;https://gary.wenneker.org/umbrella-for-sitecore-jss/&quot;&gt;Umbrella for Sitecore JSS&lt;/a&gt;, a utility that synchronizes items from your Sitecore JSS website to your local &lt;a href=&quot;https://jss.sitecore.com/&quot;&gt;JSS development environment&lt;/a&gt;. Behind the scenes I've been working very hard to add new features as you can read below.&lt;/p&gt; &lt;h3 id=&quot;use-umbrella-globally&quot;&gt;Use Umbrella globally&lt;/h3&gt; &lt;figure class=&quot;kg-image-card kg-width-full&quot;&gt;&lt;img src=&quot;/assets/img/uploads/2019/05/image-1.png&quot; class=&quot;kg-image&quot; /&gt;&lt;/figure&gt; &lt;p&gt;&lt;a href=&quot;https://github.com/GaryWenneker/jss-umbrella&quot;&gt;Umbrella&lt;/a&gt; is now available from &lt;a href=&quot;https://www.npmjs.com/package/jss-umbrella&quot;&gt;NPM&lt;/a&gt;! The CLI can be used globally. Install Umbrella using the command &lt;code&gt;npm link jss-umbrella&lt;/code&gt;. There is no reason to add the script locally in your project anymore. Use the same command to update the CLI. For the...</description>
        <pubDate>Mon, 20 May 2019 07:21:12 +0000</pubDate>
        <link>/sitecore-jss-umbrella-update-2/</link>
        <guid isPermaLink="true">/sitecore-jss-umbrella-update-2/</guid>
        
        <category>sitecore</category>
        
        <category>nodejs</category>
        
        <category>jss</category>
        
        <category>headless</category>
        
        <category>git</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Sitecore JSS: Umbrella</title>
        <description>&lt;blockquote&gt; &lt;p&gt;Would’t it be great if we could sync our Sitecore JSS website to our local JSS dev environment?&lt;/p&gt; &lt;/blockquote&gt; &lt;p&gt;You are a hardcore Sitecore developer, or a front end wizard and are starting with Sitecore JSS. At first you might think, I don’t know anything about front end stuff, or as a front end dev, you don’t want to do anything with Sitecore. Then there’s two ways to work with JSS (developer workflows) C&lt;a href=&quot;https://jss.sitecore.com/docs/fundamentals/dev-workflows/code-first&quot;&gt;ode First&lt;/a&gt; and &lt;a href=&quot;https://jss.sitecore.com/docs/fundamentals/dev-workflows/sitecore-first&quot;&gt;Sitecore First&lt;/a&gt;. And what about the structure? How is data handled? Feeling desperate yet? You can also get into annoying discussions...</description>
        <pubDate>Fri, 03 May 2019 07:21:12 +0000</pubDate>
        <link>/umbrella-for-sitecore-jss/</link>
        <guid isPermaLink="true">/umbrella-for-sitecore-jss/</guid>
        
        <category>sitecore</category>
        
        <category>nodejs</category>
        
        <category>reactjs</category>
        
        <category>typescript</category>
        
        <category>jss</category>
        
        <category>cms</category>
        
        <category>git</category>
        
        <category>asp.net</category>
        
        <category>headless</category>
        
        <category>mvc</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Sitecore: Warp factor nine!</title>
        <description>&lt;p&gt;And for the Nth time I went to the servicedesk to reinstall everything on my machine. Why? Too much stuff on it, getting slow, C-drive just notified that my drive was full. Do you recognize it?&lt;/p&gt; &lt;p&gt;So you think your laptop is fast? Then take in account that by default your laptop will be running  in this state.&lt;/p&gt; &lt;h3 id=&quot;energy-power-plan-thats-tricking-you-that-its-all-ok-but-its-not&quot;&gt;Energy Power Plan that’s tricking you that it’s all ok, but it’s not!&lt;/h3&gt; &lt;p&gt;This seams like it means that it streamlines the performance in general. I experienced that a Unicorn sync which normally would run for a maximum of 30 minutes...</description>
        <pubDate>Mon, 22 Apr 2019 07:21:12 +0000</pubDate>
        <link>/sitecore-warp-factor-nine/</link>
        <guid isPermaLink="true">/sitecore-warp-factor-nine/</guid>
        
        <category>sitecore</category>
        
        <category>react</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Looking back at the Sitecore Hackathon 2019 challenge: DinoCore</title>
        <description>&lt;p&gt;While being scared a little if I could handle the whole 24 hours I started this great adventure with &lt;a href=&quot;https://ca.linkedin.com/in/jflheureux&quot;&gt;Jean-François &quot;Jeff&quot; L'Heureux&lt;/a&gt; (Canada) and &lt;a href=&quot;https://nl.linkedin.com/in/wessel-t-hoen-76818519&quot;&gt;Wessel 't Hoen&lt;/a&gt; (the Netherlands). Before the &lt;a href=&quot;http://www.sitecorehackathon.org/sitecore-hackathon-2019/&quot;&gt;Hackathon&lt;/a&gt; even began we had meetings to think about directions and possible things we wanted to build.  But the judges made the contest harder. This year they added additional requirements! :-)&lt;/p&gt; &lt;p&gt;&lt;/p&gt; &lt;h2 id=&quot;starting-with-an-idea&quot;&gt;Starting with an idea&lt;/h2&gt; &lt;p&gt;And so our ideas were flushed down the drain and we started thinking about something new. We chose the JSS way. Functionality that would change the presentation of our...</description>
        <pubDate>Tue, 05 Mar 2019 23:04:12 +0000</pubDate>
        <link>/looking-back-at-the-sitecore-hackathon-2019-challenge/</link>
        <guid isPermaLink="true">/looking-back-at-the-sitecore-hackathon-2019-challenge/</guid>
        
        <category>sitecore</category>
        
        <category>hackathon</category>
        
        <category>nodejs</category>
        
        <category>reactjs</category>
        
        <category>typescript</category>
        
        <category>jss</category>
        
        <category>cms</category>
        
        <category>graphql</category>
        
        <category>design</category>
        
        <category>git</category>
        
        <category>vsts</category>
        
        <category>css</category>
        
        <category>flexbox</category>
        
        <category>asp.net</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Sitecore JSS: Triggering Marketing Events</title>
        <description>&lt;p&gt;With Sitecore JSS the development strategy has shifted. It enables frontend developers to participate in Sitecore development teams, whether you are creating a single page application (SPA) or consuming the JSS layout service providing you with the context of the route. User interaction is done on the client side which offers us certain advantages and challenges. One of the advantages we get is that we can trigger marketing events from the frontend with just a few lines of code.&lt;/p&gt; &lt;p&gt;The following steps will show you how to set up your Sitecore and frontend environment and how to trigger an event...</description>
        <pubDate>Sun, 03 Feb 2019 07:21:12 +0000</pubDate>
        <link>/sitecore-jss-triggering-marketing-events/</link>
        <guid isPermaLink="true">/sitecore-jss-triggering-marketing-events/</guid>
        
        <category>jss</category>
        
        <category>sitecore</category>
        
        <category>nodejs</category>
        
        <category>reactjs</category>
        
        <category>headless</category>
        
        <category>cms</category>
        
        <category>typescript</category>
        
        <category>mvc</category>
        
        <category>design</category>
        
        <category>marketing</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Sitecore JSS: Get Typed!</title>
        <description>&lt;p&gt;In this post I will get you setting up typing in place in your JSS application. You might ask what it is for and why you would use it? Because it is great! It gives you type checking, forcing you to use types/interfaces and best of all, you’ll have intellisense!&lt;/p&gt; &lt;p&gt;Because the Sitecore Javascript Services template is in plain Javascript we have to add some extra’s to make the typings work. We can go with two directions: &lt;a href=&quot;https://flow.org/en/&quot;&gt;Flow&lt;/a&gt; or TypeScript. Because the way JSS builds it’s bundles we must keep the actual js-files for the components.&lt;/p&gt; &lt;p&gt;What I want...</description>
        <pubDate>Tue, 18 Dec 2018 07:21:12 +0000</pubDate>
        <link>/sitecore-jss-get-typed/</link>
        <guid isPermaLink="true">/sitecore-jss-get-typed/</guid>
        
        <category>jss</category>
        
        <category>sitecore</category>
        
        <category>graphql</category>
        
        <category>nodejs</category>
        
        <category>reactjs</category>
        
        <category>headless</category>
        
        <category>cms</category>
        
        <category>typescript</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Sitecore JSS: Authentication</title>
        <description>&lt;p&gt;Building a website at some point always requires some mechanism for a user to be able to login. And because we are working in a headless enviroment we have to check if we can accomplish this.&lt;/p&gt; &lt;h3 id=&quot;jss-authentication-recipe&quot;&gt;JSS Authentication Recipe&lt;/h3&gt; &lt;p&gt;Before we can actually log in we must have some some stuff in our JSS project. Most of the time we execute GET-requests and consume the data we receive from the server. Now we have to add user interaction and also post data to the server.&lt;/p&gt; &lt;p&gt;I want to have some state in my app and that means that I...</description>
        <pubDate>Mon, 01 Oct 2018 07:21:12 +0000</pubDate>
        <link>/sitecore-jss-authentication/</link>
        <guid isPermaLink="true">/sitecore-jss-authentication/</guid>
        
        <category>headless</category>
        
        <category>cms</category>
        
        <category>jss</category>
        
        <category>sitecore</category>
        
        <category>nodejs</category>
        
        <category>reactjs</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Sitecore JSS: Using a custom Layout Service configuration</title>
        <description>&lt;p&gt;It's easy to change the output of the JSS Layout Service. You can either choose to use the out of the box Content Resolvers or build your own one as I have shown in my post &lt;strong&gt;&lt;a href=&quot;https://gary.wenneker.org/sitecore-jss-extending-the-layout-service/&quot;&gt;&lt;em&gt;Sitecore JSS: Extending the Layout Service&lt;/em&gt;&lt;/a&gt;&lt;/strong&gt;. The outcome is that you need to define a Content Resolver and point it to your assembly and having your rendering making use of it. So far so good. But what if you have multiple renderings? Then you need to change them all to make them use your resolver. This creates the need of a global Layout...</description>
        <pubDate>Wed, 26 Sep 2018 07:21:12 +0000</pubDate>
        <link>/sitecore-jss-using-a-custom-layout-service-configuration/</link>
        <guid isPermaLink="true">/sitecore-jss-using-a-custom-layout-service-configuration/</guid>
        
        <category>jss</category>
        
        <category>sitecore</category>
        
        <category>nodejs</category>
        
        <category>graphql</category>
        
        <category>reactjs</category>
        
        <category>headless</category>
        
        <category>cms</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Sitecore JSS: Extending the Layout Service</title>
        <description>&lt;p&gt;JSS (JavaScript Services) is Sitecore's answer to the need of having a decoupled CMS. One of the reasons for the popularity of the headless architecture is because you can redesign your CMS without setting up a new implementation of the CMS itself. A second reason is that developers do not need to know anything about the backend system. JSS is highly flexible and out of the box it supports a a lot when it comes to customization. Nevertheless, we sometimes need to extend the reality as we see it  ;-)&lt;/p&gt; &lt;figure class=&quot;kg-image-card kg-width-full&quot;&gt;&lt;img src=&quot;/assets/img/uploads/2018/09/demo.png&quot; class=&quot;kg-image&quot; /&gt;&lt;figcaption&gt;example output of Sitecore JSS...</description>
        <pubDate>Wed, 26 Sep 2018 07:21:12 +0000</pubDate>
        <link>/sitecore-jss-extending-the-layout-service/</link>
        <guid isPermaLink="true">/sitecore-jss-extending-the-layout-service/</guid>
        
        <category>jss</category>
        
        <category>sitecore</category>
        
        <category>graphql</category>
        
        <category>nodejs</category>
        
        <category>reactjs</category>
        
        <category>headless</category>
        
        <category>cms</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Troubleshooting the Sitecore Dynamic Placeholder Glitch</title>
        <description>&lt;p&gt;A few weeks ago I was asked to do some generic implementation of ReactJS renderings in &lt;a href=&quot;https://doc.sitecore.net/sitecore_experience_accelerator&quot;&gt;Sitecore SXA&lt;/a&gt;. The challenges: It needs to work with standard SXA, using dynamic placeholders, using an ORM mapper like &lt;a href=&quot;http://glass.lu/&quot;&gt;Glass&lt;/a&gt; but also pass only needed data structures to the components, thus the serialization may not be too bloated. During this journey I found an interesting issue you might get into as well.&lt;/p&gt; &lt;p&gt;So what happened? My placeholders did not show up in my component. One component had one, the other did not. What went wrong?! They used the same codebase in the...</description>
        <pubDate>Mon, 10 Sep 2018 07:21:12 +0000</pubDate>
        <link>/troubleshooting-the-sitecore-sxa-and-dynamic-placeholder-glitch/</link>
        <guid isPermaLink="true">/troubleshooting-the-sitecore-sxa-and-dynamic-placeholder-glitch/</guid>
        
        <category>sitecore</category>
        
        <category>reactjs</category>
        
        <category>sxa</category>
        
        <category>asp.net</category>
        
        <category>mvc</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>How to work with Git: Left Git or right Git?</title>
        <description>&lt;p&gt;I know this post hasn't to do anything with Sitecore but also with Sitecore development we want to make sure our sourcecode is protected in some repository. In my past live I had to use Microsoft's source repository VSS to store my code and collaborate with my fellow colleagues. Even with VSTS this was still the way to go. And then it all changed when VSTS had the option to use it as a Git repository. All open source developers probably will laugh in my face right now but for me it was the first time I actually had fun...</description>
        <pubDate>Mon, 10 Sep 2018 07:21:12 +0000</pubDate>
        <link>/left-git-or-right-git/</link>
        <guid isPermaLink="true">/left-git-or-right-git/</guid>
        
        <category>git</category>
        
        <category>vsts</category>
        
        <category>sitecore</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Sitecore JSS: Create your own GraphQL schema</title>
        <description>&lt;p&gt;One very great feature is added to the Sitecore JSS module: &lt;a href=&quot;https://graphql.org&quot; target=&quot;_blank&quot;&gt;GraphQL&lt;/a&gt; support. It allows you to query an API with a JSON payload. Compared to REST API's GraphQL is more maintainable and more flexible as GraphQL services can be stiched together.&lt;/p&gt; &lt;blockquote&gt; &lt;p&gt;GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data.&lt;/p&gt; &lt;/blockquote&gt; &lt;h2 id=&quot;building-the-sitecore-graphql-schemaprovider&quot;&gt;Building the Sitecore GraphQL SchemaProvider&lt;/h2&gt; &lt;p&gt;In this post I will walk through the following steps to guide you setting up a custom GraphQL SchemaProvider from which you can query the enpoint.&lt;/p&gt; &lt;h3 id=&quot;steps-to-create-your-own-graphql-schema-in-sitecore&quot;&gt;Steps to create...</description>
        <pubDate>Thu, 06 Sep 2018 07:21:12 +0000</pubDate>
        <link>/sitecore-jss-create-you-own-graphql-schema/</link>
        <guid isPermaLink="true">/sitecore-jss-create-you-own-graphql-schema/</guid>
        
        <category>jss</category>
        
        <category>sitecore</category>
        
        <category>graphql</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Sitecore JSS: Development Modes</title>
        <description>&lt;p&gt;Sitecore JSS is the new way of developing in and with Sitecore. The &lt;a href=&quot;https://jss.sitecore.net/docs/getting-started/quick-start&quot;&gt;quickstart &lt;/a&gt;is pretty straightforward when it comes to the disconnected mode. This blog also focuses on the &lt;a href=&quot;https://jss.sitecore.net/docs/fundamentals/dev-workflows/code-first&quot;&gt;Code-First workflow&lt;/a&gt; and the &lt;a href=&quot;https://jss.sitecore.net/docs/fundamentals/dev-workflows/sitecore-first&quot;&gt;Sitecore-First workflow&lt;/a&gt;.&lt;/p&gt; &lt;h2 id=&quot;sitecore-jss-modes&quot;&gt;Sitecore JSS: modes&lt;/h2&gt; &lt;p&gt;When you want to start developing in Sitecore JSS you can choose beween four flavours. For only one of them Sitecore isn't required.&lt;/p&gt; &lt;ul&gt;&lt;li&gt; &lt;em&gt;&lt;strong&gt;Disconnected mode&lt;/strong&gt;&lt;/em&gt; - As I described before this mode is pretty straightforward. Does not require Sitecore and it's just like developing a plain ReactJS website with webpack. In one of the next posts...</description>
        <pubDate>Wed, 29 Aug 2018 07:21:12 +0000</pubDate>
        <link>/sitecore-jss-development-modes/</link>
        <guid isPermaLink="true">/sitecore-jss-development-modes/</guid>
        
        <category>jss</category>
        
        <category>sitecore</category>
        
        <category>nodejs</category>
        
        <category>reactjs</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Sitecore JSS: Failed to start Node process</title>
        <description>&lt;p&gt;JSS is Sitecore's answer to have the ability to offload your website from sitecore and run the website somewhere else. There are several ways to run the site, disconnected, connected and integrated.&lt;/p&gt; &lt;blockquote&gt;JSS is a complete SDK for JavaScript developers that enables you to build full-fledged solutions using Sitecore and modern JavaScript UI libraries and frameworks. You can develop completely disconnected from Sitecore and even get your project started without a Sitecore install.&lt;/blockquote&gt; &lt;h2 id=&quot;running-jss-integrated-in-sitecore&quot;&gt;Running JSS integrated in Sitecore&lt;/h2&gt; &lt;p&gt;During my exploration of JSS I also wanted to deploy my app to Sitecore and check if I could open the...</description>
        <pubDate>Mon, 27 Aug 2018 07:21:12 +0000</pubDate>
        <link>/sitecore-jss-failed-to-start-node-process/</link>
        <guid isPermaLink="true">/sitecore-jss-failed-to-start-node-process/</guid>
        
        <category>jss</category>
        
        <category>nodejs</category>
        
        <category>nvm</category>
        
        <category>sitecore</category>
        
        <category>reactjs</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Performance tuning Sitecore: Ludicrous Speed!</title>
        <description>&lt;p&gt;Developing with Sitecore and specifically deployments for me is similar to developing with SharePoint in the old days. You have to deploy a bunch of files to the server and IIS has to spin up again. Depending on the amount of processes, services and other stuff this can take a while. So when we want to debug our code and do a couple of deployments the amount of waiting time stacks up. I easily could open an extra tab in my browser and load up Netflix to watch a new episode of whatever series that's running at the moment.&lt;/p&gt; &lt;p&gt;And...</description>
        <pubDate>Sat, 26 May 2018 07:21:12 +0000</pubDate>
        <link>/performance-tuning-sitecore-ludicrous-speed/</link>
        <guid isPermaLink="true">/performance-tuning-sitecore-ludicrous-speed/</guid>
        
        <category>sitecore</category>
        
        <category>sxa</category>
        
        <category>asp.net</category>
        
        <category>mvc</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Amplify your website using AMP in Sitecore</title>
        <description>&lt;p&gt;So, the customer wants to have some pages in AMP I heard a colleague say. Amp? What’s that? Never heard of that. I opened op my digital bible Google and started to search.&lt;/p&gt; &lt;h2 id=&quot;what-is-amp&quot;&gt;What is AMP?&lt;/h2&gt; &lt;blockquote&gt; &lt;p&gt;AMP or &lt;a href=&quot;https://www.ampproject.org/learn/overview/&quot;&gt;Accelerated Mobile Pages&lt;/a&gt; is Google’s CDN where your indexed mobile pages are served to mobile pages&lt;/p&gt; &lt;/blockquote&gt; &lt;p&gt;This means that the AMP version of your page gets indexed. When someone with a mobile device searches on Google and clicks on the link rather than going to your website the cached version of that page is served: the AMP page....</description>
        <pubDate>Sun, 25 Mar 2018 14:46:05 +0000</pubDate>
        <link>/amplify-your-website-using-amp-in-sitecore/</link>
        <guid isPermaLink="true">/amplify-your-website-using-amp-in-sitecore/</guid>
        
        <category>sitecore</category>
        
        <category>amp</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Becoming MacGyver using the CSS Swiss Army Knife in Sitecore SXA</title>
        <description>&lt;h2 id=&quot;using-css-in-the-old-days&quot;&gt;Using CSS in the old days&lt;/h2&gt; &lt;p&gt;One of the things I started to dislike when working on a project is Bootstrap. Using Bootstrap in a simple site is fine as you can easily use it as a starter and throughout the years it has been very well documented and supported. But it also comes with an extensive list of components and base styling for most HTML elements. And this is where advanced design projects will expect advantages when using Bootstrap as it will style your components and even the ones that you do not want to be styled. So...</description>
        <pubDate>Sat, 17 Feb 2018 07:21:12 +0000</pubDate>
        <link>/becoming-macgyver-using-the-css-swiss-army-knife-in-sitecore-sxa/</link>
        <guid isPermaLink="true">/becoming-macgyver-using-the-css-swiss-army-knife-in-sitecore-sxa/</guid>
        
        <category>sitecore</category>
        
        <category>mvc</category>
        
        <category>sxa</category>
        
        <category>css</category>
        
        <category>flexbox</category>
        
        <category>design</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Turbo boosting Sitecore SXA Rendering Variants</title>
        <description>&lt;p&gt;In my post &lt;a href=&quot;https://gary.wenneker.org/2018/01/04/sitecore-experience-accelerator/&quot;&gt;Tuning Sitecore Experience Accelerator (SXA) with React.Net&lt;/a&gt; and &lt;a href=&quot;http://gary.wenneker.org/2018/01/21/supercharging-sitecore-with-sxa/&quot;&gt;Supercharging Sitecore with SXA&lt;/a&gt; I have proven that you can do just do about anything in SXA like the greatness of having the ability to use your own design (markup/html) whenever you like withing Sitecore SXA and use them in the Experience Editor Toolbox and drag and drop your components.&lt;/p&gt; &lt;p&gt;Of course some of you might think that there's more to SXA than just components and the toolbox and that's true. But it would be unfair to SXA to just cover all of the functionality in one...</description>
        <pubDate>Sun, 11 Feb 2018 07:21:12 +0000</pubDate>
        <link>/turboboosting-sitecore-sxa-rendering-variants/</link>
        <guid isPermaLink="true">/turboboosting-sitecore-sxa-rendering-variants/</guid>
        
        <category>sitecore</category>
        
        <category>react</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Supercharging Sitecore with SXA</title>
        <description>&lt;p&gt;One of the most interesting discussions I had the last couple of weeks is when to use custom build solutions, maybe a boilerplate or Sitecore Experience Accelerator (in short &lt;a href=&quot;https://doc.sitecore.net/sitecore_experience_accelerator&quot;&gt;SXA&lt;/a&gt;.  In my &lt;a href=&quot;http://gary.wenneker.org/2018/01/04/sitecore-experience-accelerator/&quot;&gt;previous post&lt;/a&gt; I wrote about the feeling one can have when playing around with SXA, how I could use my own (React) components in SXA, but there is so much more under the hood. &lt;/p&gt; &lt;p&gt;In this post I will zoom in more into the world of SXA and try to convince you that SXA is the way to go.&lt;/p&gt; &lt;p&gt;&lt;em&gt;Want to skip to the &lt;a&gt;conclusion&lt;/a&gt;?&lt;/em&gt;&lt;/p&gt;...</description>
        <pubDate>Sun, 21 Jan 2018 07:21:12 +0000</pubDate>
        <link>/supercharging-sitecore-with-sxa/</link>
        <guid isPermaLink="true">/supercharging-sitecore-with-sxa/</guid>
        
        <category>sitecore</category>
        
        <category>mvc</category>
        
        <category>sxa</category>
        
        <category>reactjs</category>
        
        <category>asp.net</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Tuning Sitecore Experience Accelerator (SXA) with React.Net</title>
        <description>&lt;blockquote&gt;Bob's way - tuning SXA This post is my black and white vision of Sitecore's Experience Accelerator and colorized like Bob Ross would do :-) &lt;/blockquote&gt; &lt;p&gt;What to jump straight to my findings? &lt;a&gt;Click here&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt;&lt;/p&gt; &lt;p&gt;Since 2001 I have been developing in SharePoint and last year I made the swith to Sitecore. When I started working with Sitecore my first project was with SXA. This was a somewhat awkward experience as I was used to create markup and bind data to it.&lt;/p&gt; &lt;p&gt;Something I heard a while ago:&lt;br /&gt;&lt;/p&gt; &lt;figure class=&quot;kg-image-card&quot;&gt;&lt;img src=&quot;/assets/img/uploads/2018/01/ac46f197edea1834d37274078166d904.jpg&quot; class=&quot;kg-image&quot; /&gt;&lt;/figure&gt; &lt;blockquote&gt;&lt;em&gt;After the implementation we give...</description>
        <pubDate>Thu, 04 Jan 2018 07:21:12 +0000</pubDate>
        <link>/sitecore-experience-accelerator/</link>
        <guid isPermaLink="true">/sitecore-experience-accelerator/</guid>
        
        <category>sitecore</category>
        
        <category>mvc</category>
        
        <category>sxa</category>
        
        <category>flexbox</category>
        
        <category>nodejs</category>
        
        <category>reactjs</category>
        
        <category>asp.net</category>
        
        <category>blog</category>
      </item>
    
      <item>
        <title>Installing Sitecore Experience Platform 9.0</title>
        <description>&lt;p&gt;&lt;a href=&quot;https://www.sitecore.net/events/symposium-2017/introduction&quot;&gt;SitecoreSym&lt;/a&gt; finished last week and now Sitecore Experience Platform 9.0 &lt;strong&gt;initial release&lt;/strong&gt; is availabe. As a full stack developer  am always curious about new things so the first thing I did was to download all the &lt;a href=&quot;https://dev.sitecore.net/Downloads/Sitecore_Experience_Platform/90/Sitecore_Experience_Platform_90_Initial_Release.aspx&quot;&gt;files&lt;/a&gt; and try to install the thing on a virtual machine. I'm running a Macbook as I abandoned Sharepoint after more than ten years and found myself writing code in all sorts of Javascript frontend frameworks. Therefore I do not needed a Windows machine anymore.&lt;/p&gt; &lt;p&gt;This post will guide you through the installation of a &lt;em&gt;single server installation&lt;/em&gt;.&lt;/p&gt; &lt;h3 id=&quot;so-they-re-saying-it-is-an-easy-install-let-me-give-you-the-short-version-of-it&quot;&gt;So they're saying...</description>
        <pubDate>Thu, 26 Oct 2017 07:21:12 +0000</pubDate>
        <link>/installing-sitecore-9/</link>
        <guid isPermaLink="true">/installing-sitecore-9/</guid>
        
        <category>sitecore</category>
        
        <category>docker</category>
        
        <category>blog</category>
      </item>
    
  </channel>
</rss>
