-
2017-08-09
Olivia Koivisto
With over 13 years with One North, One North Architect Mike Skutta knows what it takes to be successful in the digital world. While it’s true that Skutta works remotely in Florida, he is oftentimes seen rolling down the office hallways using the remote bot and is in constant contact with the team members based in Chicago. Skutta is also in charge of the mentorship program for recently graduated developers at One North.
-
2017-08-09
Mike Skutta and Alex Pershteyn
During an exercise with our Sitecore configuration we notice a bug with the patch instead action that is described here http://sitecore.stackexchange.com/questions/2049/patchinstead-removes-an-element-with-no-attributes
-
I run into various occasions where I need to programmatically publish an Sitecore item. One thing you don't want to forget about are multiple publishing targets. You may have more than one target due to hosting content delivery servers in different geographic regions with separate web databases. Instead of publishing to a fixed or hard-coded database, you should use the configured publishing targets to determine the databases to publish to.
-
Sitecore Experience Analytics reporting supports a list control that renders tabular data. The data includes the Key along with Visits, Value per visit, Average duration, Bounce Rate, Conversion Rate, and Page views per visit. Only standard analytics data can be displayed in the out of the box list control. The columns are fixed and cannot be configured.
-
I just wanted to share a quick shortcut I recently used. I had the need to view the Sitecore configuration on a content delivery server. The problem was the content delivery server was already hardened and all non-essential files were removed, including ShowConfig.aspx. I created a temporary .aspx file that can be dropped anywhere on the content delivery server. A request can be made against this page to return the contents of the typical show config.
-
I was recently working on a project building a custom dashboard in Sitecore. We decided to build the dashboard using SPEAK v2. The primary reason for this decision was we wanted a consistent user experience that followed the same look and feel as the rest of the Sitecore applications. I received the designs of the new dashboard from our design team. I quickly noticed that the designs were not completely in line with the components that are typically seen in SPEAK UIs. I asked the designers if they were familiar with the SPEAK Components Guidance; they were not aware of it. I realized that the SPEAK Components Guidance may not be well known.