There are those features that you always have to implement when coming towards the end of the project and think about going live.
robots.txt is one of them.
In general the robots.txt is responsible for telling Search Engines what parts of the website to index and which ones not. That does not mean that Search Engines care. If you want to read more: https://developers.google.com/search/docs/crawling-indexing/robots/intro
Luckily Headless SXA provides that feature so you don't have to implement something yourself.
There is always remaining tasks you have to do in order to finalize a website. Out of this series I'd like to share my simple Meta Tag and Open Graph implementation in XM Cloud using Headless SXA, JSS and NextJs.
There are a lot of bricks and pieces on the web how to setup DNS for a local Site in SXA but no end to end description. At least I could not find it. Here's one from A-Z
A nice and commonly used feature in SXA is the "not found" functionality. Sadly here is no from A-Z documentation and SXA defaults collide a bit with Sitecore defaults. So let's walk through setting up a Not Found Page as intended by general requirements.
Sitecore 10 has been recently released with SXA 10. There has been a lot of feedback on the fresh SXA 10 CLI and the news are great:
So how can you benefit from all that new stuff while running Sitecore and SXA 9.3?
Having different images to optimize the experience on different devices (or screen resolutions) is essential. Here's a quick implementation example on how to achieve that using Rendering Variants (Scriban or Items).
A walk through from A to Z starting creating a module, clone a rendering, adjust the templat, create a custom experience button, creating the variants using items and scriban and installing the module to the site in order to test it.
A common task when implementing a website is to handle the height equality of components in one row even though the content might differ. SXA has an already inbuild solution.
Even though SXA is there since many years, adopting towards SXA seems to be a very slow process. When I heared of SXA in 2016 for the first time I directly fell in love with it. I managed to introduce it to a Multisite and Multilanguage Project end of 2017 and by working with it, I became an ambassador for SXA. Let's check out some material I recommend to see before getting started.
With Powershell Extensions for Sitecore you can run Powershell scripts in Sitecore. Also SXA is offering a bunch of Scripts supporting your activities. I recently had to run Powershell remotely. There is good Documentation out there but somehow I missed some pieces that stopped me from using that feature smoothly. So I try to connect the pieces of the puzzle in this blog post.
See the Symposium 2019 talk of Natasha Batra and me (rerecorded) how Metronom developed a Multisite Solution at scale and walk through how we utilized the greadt potential of SXA to accelerate.
I recently had the problem that my SOLR Service was not starting all of a sudden. So I searched the internet and asked colleages but I had quite a hard time figuring out what the issue was. So here is a summary of possible reasons that you can check.
When you have created Components and you figure out later that they are used always in a bunch of e.g. 3, or you want to prepare a one-time-drag-and-drop experience for the editor even though several components are involved (like in a header or a footer) then the component renderer (introduced with SXA 1.8) is a good solution for you.
Do you have agreed on SLAs towards your website and authoring environments? When thinking about your Sitecore Infrastructure you have many opportunities to scale out. Let's take a look what we considered in our project.
Here you can find my presentation about 100% availability with a video taken from SUGPL in December 2017 and links to the single Blogposts that deal with that topic.
In case you run several websites in one Sitecore instance and need to distinguish users between those different sites here’s what we did.
When starting a project usually there are so many requests and ideas that you create ambitious Role concepts and rolling these out to all of your sites. After a while you see that not all features are really used. This was the point in time for me to get back to a more lean approach.
As any system, also your Sitecore installation will historically grow. And for sure, none of the users will tell you when he or she stops working on Sitecore or leaves the company. Also noone of the local administrators (in case you have some) will tell. So, to keep Sitecore a bit clean you can check for users that are not active in the system.