Understanding Sitecore Stream API and Its Role in Language Translation

Sitecore’s Stream API is one of the latest innovations introduced in Sitecore XM Cloud, enabling faster and more flexible content delivery. It provides a modern, high-performance API that streams content directly at the component level, allowing front-end applications like Next.js or Vercel-hosted sites to fetch only the data they need — in real time.

While the Stream API does not translate content automatically, it seamlessly supports multilingual delivery. This means if your Sitecore content items have versions in multiple languages (e.g., English, Arabic, Chinese, Japanese), the Stream API can automatically deliver the correct localized version based on the language context of the request.

For automatic translation, you can integrate the Stream API with Azure Cognitive Services Translator or other AI-based translation engines. This approach allows you to:

• Automatically translate editorial content into multiple languages.

• Store the translated versions as separate language variants within Sitecore.

• Deliver localized content efficiently through the Stream API to your front-end application.

In short, the Stream API acts as the real-time multilingual content delivery layer, while external AI translation services handle the actual language conversion and localization.

Sitecore 10.4 -Fixing Sitecore Installation Errors: .NET Hosting Bundle Download (dotnet-hosting-6.0.21) Fails with "EOF" or "400 Bad Request

When installing Sitecore XP/XM on-premises using SIF (Sitecore Installation Framework), you may run into frustrating issues during the .NET Hosting Bundle download step. The issue often looks like this:

Issue - the download link is not suported as it's tryign to find the old version 

[-------- DownloadDotNetMultiTargeting : DownloadFile ------------------------]

[DownloadDotNetMultiTargeting]:[Download] https://download.visualstudio.microsoft.com/download/pr/b50f2f63-23ed-4c96-9b38-71d319107d1b/26f8c79415eccaef1f2e0614e10cd701/dotnet-hosting-6.0.21-win.exe => C:\Users\jitus\AppData\Local\Temp\dotnet-hosting-win.exe

Error downloading https://download.visualstudio.microsoft.com/download/pr/b50f2f63-23ed-4c96-9b38-71d319107d1b/26f8c79415eccaef1f2e0614e10cd701/dotnet-hosting-6.0.21-win.exe: The underlying connection was closed: The connection was closed unexpectedly.

[TIME] 00:00:19

Error downloading https://download.visualstudio.microsoft.com/download/pr/b50f2f63-23ed-4c96-9b38-71d319107d1b/26f8c79415eccaef1f2e0614e10cd701/dotnet-hosting-6.0.21-win.exe: The underlying connection was closed: The connection was closed unexpectedly.

When I checked the URL, I got 404 to fix the issue

I replace the URL in 

Prerequisites.json

Value https://builds.dotnet.microsoft.com/dotnet/aspnetcore/Runtime/6.0.36/aspnetcore-runtime-6.0.36-win-x64.exe and that fixed the issue

XMC how to fix a network with name ABC-xmc_default exists but was not created by compose

Recently during the new XMC project setup, I got below error

 Starting Sitecore environment...

 level=warning msg="a network with name ABC-xmc_default exists but was not created by compose.\nSet `external: true` to use an existing network"

network ABC-xmc_default was found but has incorrect label com.docker.compose.network set to ""

You cannot call a method on a null-valued expression.

At C:\Projects\ABC-xmc\docker\add-host.ps1:8 char:1

+ $containerId = $containerId.Replace("failed to get console mode for s ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : InvalidOperation: (:) [], ParentContainsErrorRecordException

    + FullyQualifiedErrorId : InvokeMethodOnNull

Fix

Go to your docker compose overide file and at the last add this lines

networks:

  default:

    external: true

    name: ABC-xmc_default