Personal blog by Serge van den Oever - als je maar lol hebt...
LinkedIn: Serge van den Oever - articles on LinkedIn
Technology Consultant @ Macaw
Competence Team Lead Custom Application Development @ Macaw
2021-2023 Technology Sitecore Most Valuable Professional
A new XM Cloud project is scaffolded from a headstart provided by Sitecore. But how do you stay in sync with that headstart in case Sitecore decides to fix issues or include innovations? In this post, I will describe how we do this in general when starting from a headstart.
I had quite a few occasions while working with XM Cloud that I got the generic ASP.NET RunTime Error screen, instead of a detailed error description. In this post I explain how to apply modifications to the web.config file of your XM Cloud environment using an XML Document Transform (XDT) file to enable detailed error information.
XM Cloud Deploy has the Sitecore CLI and a web UI for deployment, but both are based on a well-documented API!
I would like to work with the latest version of the Sitecore CLI and its plugins, but upgrading to it is not that easy... In this blog post, you will learn how to find the version of the Sitecore CLI and its plugins, and how to upgrade them.
XM Cloud Deploy has a web UI with some great features to start a build and deploy, monitor the progress, and inspect the log files. But it also has some drawbacks. In this blog post, I will describe these drawbacks and show how to improve the workflow.
Sitecore XM and its cloud sister XM Cloud can be completely tailored through configuration files. But especially on XM Cloud testing out configuration changes is a lengthy process (10+ minutes) because a build and deploy is required to see the changes. In this blog post I will describe how I test configuration changes in just seconds.
XM Cloud is a cloud environment we would like to automate against using PowerShell. In this blog post, I explain how to enable the PowerShell ISE and configure your XM Cloud environment for PowerShell remoting.
XM Cloud comes with an out-of-the-box internal editing host. Deployment to this host is currently slow (Sitecore is working on decoupling Editing Host builds/deployments from CM builds/deployments so that Editing Host builds/deployments are fast). Lets use a locally running editing host, and expose it to the outside world using a reverse-proxy so the Experience Editor and Pages can work with the rendering host on your dev box.
Ok, you have access to XM Cloud, but now you want to extend the set of renderings available to design your pages. In this post I will take you on a trip to take this first steps.
When working with the Sitecore CLI against XM Cloud, the Project Id is needed as a parameter. There are multiple ways to retrieve this Project Id.
The XM Cloud Play! Summit demo is similar to the Play! Summit demo as available in de Sitecore demo portal, but tailered for XM Cloud. And in just a few command you can get it running on your local machine...
XM Cloud documentation is getting there!
A failed experiment to make a local XM Cloud development environment known to the outside world.
Although XM Cloud runs in the cloud, development can be done locally using Docker containers. This way we can see what we can do with XM Cloud without having access to the real stuff (yet).
In this second part of the Sitecore demo portal series I investigate if the Sitecore CLI, as used during the configuration of Sitecore XM 10.2 by the Sitecore demo portal provisioning scripts, also works for the developer.
In this first part of theSitecore demo portal series I will spin up an empty environment using the Sitecore demo portal. I will guide you through all required steps, so everything is prepared to take the next steps of creating a Sitecore headless site, a "head" website using Next.js, and utilizing Experience Edge for content delivery.
After mistakenly thinking that the Sitecore demo portal was using XM Cloud, I rewrote this blog post to explain I made a mistake.
A short post that will save you a lot of time if you need to watch a lot of box.com videos: keyboard shortcuts!
A cheat sheet for Sitecore SXA without C# coding.
When you run an npm script that has not exit code 0, an annoying set of useless error lines is shown. But there are some options to get rid of them!
For custom tools reporting problems like errors and warnings it is nice if they end up in the "Problems" panel in Visual Studio Code. In this post I describe how to achieve this.
Get chalk working with TypeScript, get color output with chalk in Lerna.
Running Sitecore JSS headless frontend with Next.js on Azure with all its CSR, SSR, SSG, and ISG goodness could look like this...
Running Next.js on Azure with all its CSR, SSR, SSG, and ISG goodness. And as an example run also Sitecore JSS on it!
Want to use the power of Gulp within your NodeJS application, instead of using the Gulp CLI and a gulpfile.js file? I finally found out how...
Processing multipart/form-data containing both fields, files and images is not as easy as it seems to be in a NodeJS Azure function with HttpTrigger. But it can be done, and I will show you how!
Netlify functions are a powerful beast for all your API needs. But what if I want to return as soon as possible from my API call to keep my web UI responsive, but still need to do something like sending out an e-mail? Enter the "classic" function style that makes this possible.
Sitecore SXA is a great way forward in structuring the way of building Sitecore web sites, providing a set of standard renderings and provide an editing experience for the web site maintainers. But sooner than later you want to extend/replace the out-of-the-box set of renderings, calling in the front-end developers to do their magic. At that moment there are many ways they can do their work, and in this post, I will describe in what is in my opinion the optimal way for performance, SEO, front-end developer experience, and separation of concerns.
Creating custom renderings can be done completely without adding C# code. In this post, we explore how to create a new SXA Toolbox section and a new rendering through the Sitecore web interface.
When you look at the out-of-the-box Sitecore SXA components you can see that the Sitecore SXA team writes most SXA components using jQuery and a small utility API called XA (eXperience Accelerator). In this post, I will dissect how Sitecore writes components and I will show you how to write a simple clock component in TypeScript using the XA API.
Mark van Aalst provides a great "no C# code" SXA sample project with the SXA.Styleguide project available on Github. In this post I describe how to get this project up and running on your local Sitecore 9.3 installation.
After investing a lot of time and effort in working with Sitecore SXACLI and creating enhancements on the standard SXACLI tooling I decided that it was time for a different approach. Please meet SXA Umbrella!
If you are still one of those losers like me that install their Sitecore 9.3 on their local machine with the Sitecore Install Assistant (SIA) instead of in a fancy set of docker containers using Docker Compose, and if you are an even bigger loser (like me) that you mess up your Sitecore installation or even worse forgot your Sitecore admin password, welcome to this life-saver post to uninstall your installation in seconds!
When you have an npm script that does use a NodeJS library (through gulp for example) that does web request that you want to monitor with Fiddler, checkout this simple script!
When you get this annoying "sgen.exe" error, you can use this fix!
To understand the way Sitecore Experience Accelerator (SXA) works, how components are built and theming is done you need to do some deep-diving. In this blog post I describe the best way to do this deep dive using the creative exchange.
In my Sitecore 9.3 SXA CLI endeavors I find myself searching for the internal field names of Sitecore items so I can use them in my Scriban templates. Using this remote PowerShell script you can look up the item fields of any Sitecore item.
I write blogposts on my own blogging platform, because I want to be the owner of my own content. I'm also a fan of https://dev.to as a great developer community blogging platform. Fortunately https://dev.to allows and supports cross posting...
PowerApps Portals is positioned as a low-code platform. Built on top of the Dynamics and the underlying Common Data Services (CDS) it enables the "citizen" developer to create public facing websites with support for logged-in users. Underlying the WYSIWYG editing GraphQL is used to do updates on the content and configuration of the portal.
Manage your SXA 9.3 theme under source control instead of as artifacts under the `Media Library/Themes` folder using the SXA CLI - make your front-end developers happy!
I really tried hard. But Azure - you failed me!
When you need to request files from GitHub with the correct mime-types GitHub itself is not the best place.
Umbrella for Sitecore JSS is our vision on how a website should be developed and hosted while using the JSS SDK and Sitecore as a headless CMS.
Use a custom Node based server to render Sitecore 9.1 JSS pages.
At my company we use TypeScript for front-end development where possible. In my first steps in using JSS I wanted to build my first component in TypeScript, which did not work out of the box. In this post I describe how I got ypeScript compilation working.
This weblog is created with GatsbyJS and after build results in a static website that can be hosted anywhere. I host my weblog on a Microsoft Azure static website. In this post I provide links to how to set up an Azure static website, and how to automate the deployment based on commits to the Github repository.
That mandatory first blog post on my own "blogging platform". After blogging for years on http://weblogs.asp.net/soever and some endeavors with the Medium blogging platform.
Given an old Git repo, pull out changed files into a zip file.