This was my first #SUGCON EU. Even though it was only few days, it was an excellent event. This year SUGCON Europe took place in London, capital of Great Britain. I travelled from Houston, Texas. 9 hour flight with United Airlines, arrived a day before the Conference, took few photos of the city.
It all started with Registration and Sitecore Certifications Exam.
First day was opened by Mark Frost the CEO of Sitecore, with a #sitecoreSelfie
Opening Keynote was by Donovan Brown from Microsoft. He talked about DevOps. Showed how easy it is to use Azure Boards, as well as Azure Pipelines and Azure Repos and Azure Artifacts, to get started you can visit azure.com/devops
There were many great Sessions at the #SUGCON, but the ones that caught my attention were the #JSS Sessions.
JSS Immersion Session by Sitecore Front End Evangelist Anastasiya Flynn was really interesting. She went into the details about creating an event search page and shared some interesting and popular React Libraries.
She showed how you can debug your Sitecore JSS application in VS Code
GraphQL – Lessons Learned
React Libraries that were shared on this presentation:
Category: Best enhancement to the Sitecore Admin (XP) UI for Content Editors & Marketers
So the idea of this solution is to make the life of a Marketer much easier, whenever the Content Author is creating an article and new content on the page, without opening a new page, you can just work in Experience Editor and pull up a TwitterFeed, and see what is trending now.
With Sitecore 9.1 Sitecore JSS will no longer be in Technical Preview.
By Using JSS you get to keep Full Experience Platform capabilities such as:
Personalization and Testing
Tracking and Analytics
JSS currently supports OOTB, Angular, React and Vue.JS, who knows what will be coming next, it seems to be that more front end developers are interested to learn JSS because it gives them freedom.
Sitecore JSS requires a different License. Partners will need to regenerate a license in SPN.
– JSS 9 with React requires React 16.3 or later, because of new Context API in React.
– JSS 9 with Angular requires Angular 6.x , anybody on Angular 5 can continue on JSS 8 npm packages.
– Layout Service will no longer return ‘editable’ value for fields, unless Sitecore is actually in Experience Editor.
– Sitecore.Ship is replaced with manifest package deployment system. What does that mean, a shared secret known to the deployer and server is used to deploy signed package HMAC.
– Completely refactored React, Angular and Vue apps. There is no more Basic or Advanced App. The content of Sample App has been refactored to JSS Specific Style-guides.
– Sample Apps have been heavily documented for ease of learning.
– All Sample apps now support GraphQL.
A new scaffold has been added that will automatically scaffold a JSS component.
The following instructions is done in Disconnected mode and in ReactJS
Once you add it, you will need to modify few areas:
Sitecore Component itself, to reflect the changes, that you have made in the route.
This is the area where the component is added automatically when you are running the command (jss scaffold <componentName>)
And for the changes to the component in the index.js see the screenshot below:
And this is what it will look like:
As you can see on the right side, this is how you will be able to identify that I did not hard code the text 🙂
Go ahead start experimenting with JSS, and look a the sample content that comes with initial creation of an app.
If you have any questions, do not hesitate to reach out to me, on twitter or Sitecore community, on slack on specific #JSS channel.
If you get a requirement to disable PhantomJS on your Content Delivery environments, this trick will do it.
How PhantomJS is implemented with Sitecore:
Content Testing in Sitecore uses the Phantom JS tool for generation of the screenshot image files. In case you didn’t know, Sitecore has had screenshot generation features for quite some time. We use it to generate icons for items that you’ll be listing in the UI like renderings. These icon generation features are based on the System.Windows.Forms.WebBrowser control built into .net. So why did we not use the existing screenshot features for Content Testing? In early testing we found discrepancies with the WebBrowser control. WebBrowser uses Internet Explorer installed on the server where Sitecore is running. But the specific version that it uses isn’t always the latest. There are registry updates one can make to force the appropriate IE version, but this seemed like a big ask of users. This was one of the reasons we chose to use Phantom JS instead.
All you have to do, is create a patch file that will disable getScreenshotForUrl
Copy the above code into the configuration file and name it whatever you want and it into App_Config\Include\zzz