Caching updates for XM Cloud
1. The media cache is no longer populated by indexing operations, to prevent situations where the instance might run out of disk space during an index rebuild.
2. Content in XM Cloud applications is now also indexed and searchable in languages that are not part of the default Solr schema.
3. The memory cache was separated into different databases, resulting in less frequent memory allocations and improved performance.
1. The media cache is no longer populated by indexing operations, to prevent situations where the instance might run out of disk space during an index rebuild.
2. Content in XM Cloud applications is now also indexed and searchable in languages that are not part of the default Solr schema.
3. The memory cache was separated into different databases, resulting in less frequent memory allocations and improved performance.
Word docs and PDFs now supported in Media link fields
Pages builder, in any link field configured as Media, you can now select the following file types if they have been uploaded to the Media library:
-
-
-
Pages builder, in any link field configured as Media, you can now select the following file types if they have been uploaded to the Media library:
-
.doc-
.docx-
.pdfSitecore Cloud SDK v0.4
If you haven't heard of Cloud SDK, you must definitely check it here - https://tinyurl.com/2yroqfzt.
New version 0.4 brings lots of so expected features:
- Web experiences: run Sitecore Personalize web experiences and experiments in your app. If you previously chose the Engage SDK because of the support for web experiences, consider switching to the Cloud SDK.
- Unified tracking: set up tracking for an event once in your app, then find the event data in your Sitecore DXP products - XM Cloud, CDP, Personalize, and Sitecore Search.
- Sitecore Search events: capture widget view and widget click events.
- Improved initialization: centralize your SDK initialization code for better scalability and easier enablement of further SDK packages in the future.
- More granular cookie handling: as a direct benefit of the new initialization logic, cookies will only be stored by those SDK packages that depend on them.
Start building
Access the SDK packages on npm, then start building with the SDK using the official documentation - https://tinyurl.com/288qy7rv. The documentation contains:
- https://tinyurl.com/2aakbpr5: Guides that take you from initialization to event tracking to enabling web experiences, step by step.
- https://tinyurl.com/2c2qqphw: An upgrade guide for developers currently on SDK version 0.3 or earlier.
- https://tinyurl.com/29lcftmx: A list of terms to help you understand the most important Cloud SDK concepts.
- https://tinyurl.com/27ufff5l: Extensive reference documentation with code examples to help you during development.
- https://tinyurl.com/22we6958: In-depth explanations and code examples of the new initialization process
- https://tinyurl.com/292n6ngt: Everything about tracking
- https://tinyurl.com/2dql5md8: Personalization options
- https://tinyurl.com/26hv7oz5: Cookie settings
One cannot underestimate the importance of Sitecore Cloud SDK. he good news is that it is already built into the latest version of XM Cloud StarterKit also knows as Foundation Head, located at: https://tinyurl.com/23xugwwl
If you haven't heard of Cloud SDK, you must definitely check it here - https://tinyurl.com/2yroqfzt.
New version 0.4 brings lots of so expected features:
- Web experiences: run Sitecore Personalize web experiences and experiments in your app. If you previously chose the Engage SDK because of the support for web experiences, consider switching to the Cloud SDK.
- Unified tracking: set up tracking for an event once in your app, then find the event data in your Sitecore DXP products - XM Cloud, CDP, Personalize, and Sitecore Search.
- Sitecore Search events: capture widget view and widget click events.
- Improved initialization: centralize your SDK initialization code for better scalability and easier enablement of further SDK packages in the future.
- More granular cookie handling: as a direct benefit of the new initialization logic, cookies will only be stored by those SDK packages that depend on them.
Start building
Access the SDK packages on npm, then start building with the SDK using the official documentation - https://tinyurl.com/288qy7rv. The documentation contains:
- https://tinyurl.com/2aakbpr5: Guides that take you from initialization to event tracking to enabling web experiences, step by step.
- https://tinyurl.com/2c2qqphw: An upgrade guide for developers currently on SDK version 0.3 or earlier.
- https://tinyurl.com/29lcftmx: A list of terms to help you understand the most important Cloud SDK concepts.
- https://tinyurl.com/27ufff5l: Extensive reference documentation with code examples to help you during development.
- https://tinyurl.com/22we6958: In-depth explanations and code examples of the new initialization process
- https://tinyurl.com/292n6ngt: Everything about tracking
- https://tinyurl.com/2dql5md8: Personalization options
- https://tinyurl.com/26hv7oz5: Cookie settings
One cannot underestimate the importance of Sitecore Cloud SDK. he good news is that it is already built into the latest version of XM Cloud StarterKit also knows as Foundation Head, located at: https://tinyurl.com/23xugwwl
XM Cloud forms support all accessibility standards (including autocomplete)
Keyboard navigation - form elements are accessible via keyboard, with logical tab order and visible focus indicators.
Screen reader compatibility - controls are labeled and announced correctly by screen readers. This includes descriptive aria labels for navigation buttons and error messages.
Form labels and instructions - fields have visible, programmatically associated labels and clear instructions.
Error handling - error messages are clear, specific, and linked to the relevant fields. Also, icons have been added to error messages to assist people with color blindness.
ARIA attributes - forms uses appropriate ARIA roles and attributes for custom elements, and includes dynamic content announcements.
Responsive design - accessibility is tested across various devices and screen sizes.
Input assistance - forms supports autocomplete features offered by the browser, and ensures that custom inputs are accessible via keyboard and screen readers. For example, when the user of the form enter text in fields like name, email, and address, the browser provides relevant suggestions based on previously entered data.
Form's accessibility validation tool: https://tinyurl.com/2yb7jwsa
Keyboard navigation - form elements are accessible via keyboard, with logical tab order and visible focus indicators.
Screen reader compatibility - controls are labeled and announced correctly by screen readers. This includes descriptive aria labels for navigation buttons and error messages.
Form labels and instructions - fields have visible, programmatically associated labels and clear instructions.
Error handling - error messages are clear, specific, and linked to the relevant fields. Also, icons have been added to error messages to assist people with color blindness.
ARIA attributes - forms uses appropriate ARIA roles and attributes for custom elements, and includes dynamic content announcements.
Responsive design - accessibility is tested across various devices and screen sizes.
Input assistance - forms supports autocomplete features offered by the browser, and ensures that custom inputs are accessible via keyboard and screen readers. For example, when the user of the form enter text in fields like name, email, and address, the browser provides relevant suggestions based on previously entered data.
Form's accessibility validation tool: https://tinyurl.com/2yb7jwsa
๐1
Cloud portal SSO now supports up to 50 domains for all new SSO connections (OIDC and SAML).
Pages Editor now allows editing all written content at both page-level and content datasource item fields
Content fields that are associated with the page itself, including metadata, can be edited in the Page content pane. This pane can be viewed alongside the page canvas, letting you edit content while also viewing the page presentation. Alternatively, you can expand the content view to a full screen mode that persists as you browse your pages.
You can also edit any content item fields that are included in a component. To do this, select the component and, in the right-hand panel, click the Content tab. This tab displays the content item selector and all content fields belonging to the selected content item.
As part of this enhanced authoring experience, the page builder now also enables you to edit the following fields:
- File
- Droplist
- Droplink
- Droptree
- Taglist
- Checklist
- Multilist
- Treelist
- Multiroot treelist
- Checkbox
- General link with email links.
Link: https://tinyurl.com/28pkztj5
Content fields that are associated with the page itself, including metadata, can be edited in the Page content pane. This pane can be viewed alongside the page canvas, letting you edit content while also viewing the page presentation. Alternatively, you can expand the content view to a full screen mode that persists as you browse your pages.
You can also edit any content item fields that are included in a component. To do this, select the component and, in the right-hand panel, click the Content tab. This tab displays the content item selector and all content fields belonging to the selected content item.
As part of this enhanced authoring experience, the page builder now also enables you to edit the following fields:
- File
- Droplist
- Droplink
- Droptree
- Taglist
- Checklist
- Multilist
- Treelist
- Multiroot treelist
- Checkbox
- General link with email links.
Link: https://tinyurl.com/28pkztj5
๐3โค1๐1
Cloud SDK 0.5.1 released. This minor features two things mainly:
- you now need to manually enable the capture of geolocation data. This ensures compatibility with Next.js 15, which no longer captures geolocation data automatically.
- document grouping, which lets you display all variations of an item (such as a product entity) as individual search results, or as a single grouped result based on a specific attribute.
- capture of country and referrer in search event interfaces is now supported
Cloud SDK release notes: https://tinyurl.com/32ww4whk
- you now need to manually enable the capture of geolocation data. This ensures compatibility with Next.js 15, which no longer captures geolocation data automatically.
- document grouping, which lets you display all variations of an item (such as a product entity) as individual search results, or as a single grouped result based on a specific attribute.
- capture of country and referrer in search event interfaces is now supported
Cloud SDK release notes: https://tinyurl.com/32ww4whk
๐1
Content SDK โ a revolution in front-end application development for XM Cloud!
As part of Sitecoreโs drive to support developers building optimized applications for XM Cloud, weโre proud and excited to announce the first beta release of Content SDK. This new SDK not only extracts the functionality of JSS designed for XM Cloud development but also makes that functionality simpler to build with and maintain.
When you build an app using Content SDK, youโll get all the packages and services you need to support your XM Cloud environment. This vastly reduces the size and complexity of your template apps, and you no longer need to remember which parts of JSS are necessary for XM Cloud. The apps you create using the Content SDKโs Next.js starter template require minimal decision-making and fine-tuning, but youโll find them significantly easier to adapt to your needs.
In line with our focus on simplicity, weโve shifted focus away from the XM-centric Experience Editor to enable Content SDK to keep pace with the ever-growing feature set of XM Cloud Pages, which is integrated out of the box with Content SDK. As a result, the chromes integration necessary to integrate with Experience Editor has been removed from Content SDK, resulting in further code optimizations.
Documentation: https://tinyurl.com/5dzht745
How to migrate: https://tinyurl.com/7unfjyub
As part of Sitecoreโs drive to support developers building optimized applications for XM Cloud, weโre proud and excited to announce the first beta release of Content SDK. This new SDK not only extracts the functionality of JSS designed for XM Cloud development but also makes that functionality simpler to build with and maintain.
When you build an app using Content SDK, youโll get all the packages and services you need to support your XM Cloud environment. This vastly reduces the size and complexity of your template apps, and you no longer need to remember which parts of JSS are necessary for XM Cloud. The apps you create using the Content SDKโs Next.js starter template require minimal decision-making and fine-tuning, but youโll find them significantly easier to adapt to your needs.
In line with our focus on simplicity, weโve shifted focus away from the XM-centric Experience Editor to enable Content SDK to keep pace with the ever-growing feature set of XM Cloud Pages, which is integrated out of the box with Content SDK. As a result, the chromes integration necessary to integrate with Experience Editor has been removed from Content SDK, resulting in further code optimizations.
Documentation: https://tinyurl.com/5dzht745
How to migrate: https://tinyurl.com/7unfjyub
๐2
Minor but pleasant fix: An XM Cloud userโs name, as defined in the Cloud Portal, is now correctly presented in the User Manager and Content Editor interfaces.
XM Cloud knowledge reference
Did you know thereโs a communityโcurated XM Cloud Knowledge Base on GitHub? It aggregates the best blog posts and resources, neatly classified by topicโperfect for zeroing in on a specific area of the platform.
Say youโre about to wire up NextAuth or integrate Storybook into an XM Cloud project. Before scoping the work, you need a clear view of the platformโs capabilities and constraints. Instead of hunting through scattered articles, you can dive into one โpoolโ of verified insights and confirm thereโs water before you jump.
Official Sitecore docs keep improving, but thirdโparty tooling (like Storybook) isnโt always covered. Thatโs where the Sitecore community shines.
Explore - and contribute to - the repo here: https://tinyurl.com/4v8mafuy. Itโs Markdownโbased, easy to navigate, and ready for your pull requests. Yet again, Sitecore has proven its greatest strength is the community who build with it!
Did you know thereโs a communityโcurated XM Cloud Knowledge Base on GitHub? It aggregates the best blog posts and resources, neatly classified by topicโperfect for zeroing in on a specific area of the platform.
Say youโre about to wire up NextAuth or integrate Storybook into an XM Cloud project. Before scoping the work, you need a clear view of the platformโs capabilities and constraints. Instead of hunting through scattered articles, you can dive into one โpoolโ of verified insights and confirm thereโs water before you jump.
Official Sitecore docs keep improving, but thirdโparty tooling (like Storybook) isnโt always covered. Thatโs where the Sitecore community shines.
Explore - and contribute to - the repo here: https://tinyurl.com/4v8mafuy. Itโs Markdownโbased, easy to navigate, and ready for your pull requests. Yet again, Sitecore has proven its greatest strength is the community who build with it!
โค2
Content SDK 0.2.0 released, bringing further simplicity and extensibility
The beta program for Content SDK continues with the release of version 0.2.0! In this release, we've focused on giving you more of what you need to develop powerful applications for XM Cloud while also removing or optimizing resources to make your apps more efficient.
One important change to highlight: this release updates the framework dependencies to use React 19 and Next.js 15, so you'll need to complete the update process for both frameworks while upgrading your app to the latest version of Content SDK.
Upgrade apps from SDK 0.1.0 to version 0.2.0: https://tinyurl.com/wwcvjbup
The beta program for Content SDK continues with the release of version 0.2.0! In this release, we've focused on giving you more of what you need to develop powerful applications for XM Cloud while also removing or optimizing resources to make your apps more efficient.
One important change to highlight: this release updates the framework dependencies to use React 19 and Next.js 15, so you'll need to complete the update process for both frameworks while upgrading your app to the latest version of Content SDK.
Upgrade apps from SDK 0.1.0 to version 0.2.0: https://tinyurl.com/wwcvjbup
New JSS wrapper component for Forms
JSS version 22.6 introduces a new Form component for wrapping XM Cloud forms. This component was previously available in the JSS Angular package, but it is now also part of the Next.js package.
All new and upgraded Next.js applications built with JSS 22.6 or later include the new component and will use it automatically whenever you create a form in the XM Cloud Forms builder. Existing form components need to be manually converted to use the new wrapper, as explained in the JSS 22.6 upgrade guide for Next.js: https://tinyurl.com/h48c66cu
JSS version 22.6 introduces a new Form component for wrapping XM Cloud forms. This component was previously available in the JSS Angular package, but it is now also part of the Next.js package.
All new and upgraded Next.js applications built with JSS 22.6 or later include the new component and will use it automatically whenever you create a form in the XM Cloud Forms builder. Existing form components need to be manually converted to use the new wrapper, as explained in the JSS 22.6 upgrade guide for Next.js: https://tinyurl.com/h48c66cu
Annoying bug fixed: resizing png images with transparent backgrounds using query string parameters (such as
w, h, mw, mh) now preserves transparency in preview mode. Previously, the background appeared black.โค3
Forwarded from Sitecore Telegram
Sitecore Accelerate Cookbook has got another release done with 17 recipes between new & updates for XM Cloud and Content Hub.
Content Hub
- Go Live Checklist
- Hypercare Strategy
- Identifying the Most Searched Terms on the Assets Page
- SSO on Content Hub
- Automatically set meta data on your entity on pre-commit
XM Cloud
- Go-Live checklist
- Enhancing search with documents
- Publishing Optimization, including updates to links in ๐๐ถ๐ฃ๐ญ๐ช๐ด๐ฉ๐ช๐ฏ๐จ ๐ต๐ฐ ๐๐ฅ๐จ๐ฆ
- Scope & Governance Framework approaches including updates to ๐๐ฐ๐ท๐ช๐ฏ๐จ ๐ต๐ฐ ๐๐ข๐ข๐, ๐๐ฆ๐ฒ๐ถ๐ช๐ณ๐ฆ๐ฎ๐ฆ๐ฏ๐ต๐ด ๐๐ข๐ต๐ฉ๐ฆ๐ณ๐ช๐ฏ๐จ, ๐๐ฐ๐ฏ๐ต๐ฆ๐ฏ๐ต ๐๐ถ๐ฅ๐ช๐ต, ๐๐ฐ๐ฏ๐ต๐ฆ๐ฏ๐ต ๐๐ช๐จ๐ณ๐ข๐ต๐ช๐ฐ๐ฏ and ๐๐ณ๐ฆ๐ฑ๐ข๐ณ๐ช๐ฏ๐จ ๐ง๐ฐ๐ณ ๐ข๐ฏ ๐๐ ๐๐ญ๐ฐ๐ถ๐ฅ ๐ฑ๐ณ๐ฐ๐ซ๐ฆ๐ค๐ต.
- Further ASP.NET Core updates including ๐๐ฆ๐ต๐ถ๐ฑ ๐๐ช๐ต๐ฆ๐ค๐ฐ๐ณ๐ฆ ๐๐ฐ๐ฏ๐ต๐ฆ๐ฏ๐ต ๐๐ฆ๐ณ๐ช๐ข๐ญ๐ช๐ป๐ข๐ต๐ช๐ฐ๐ฏ and ๐๐ถ๐ญ๐ต๐ช๐ด๐ช๐ต๐ฆ ๐๐ณ๐ค๐ฉ๐ช๐ต๐ฆ๐ค๐ต๐ถ๐ณ๐ฆ.
Content Hub
- Go Live Checklist
- Hypercare Strategy
- Identifying the Most Searched Terms on the Assets Page
- SSO on Content Hub
- Automatically set meta data on your entity on pre-commit
XM Cloud
- Go-Live checklist
- Enhancing search with documents
- Publishing Optimization, including updates to links in ๐๐ถ๐ฃ๐ญ๐ช๐ด๐ฉ๐ช๐ฏ๐จ ๐ต๐ฐ ๐๐ฅ๐จ๐ฆ
- Scope & Governance Framework approaches including updates to ๐๐ฐ๐ท๐ช๐ฏ๐จ ๐ต๐ฐ ๐๐ข๐ข๐, ๐๐ฆ๐ฒ๐ถ๐ช๐ณ๐ฆ๐ฎ๐ฆ๐ฏ๐ต๐ด ๐๐ข๐ต๐ฉ๐ฆ๐ณ๐ช๐ฏ๐จ, ๐๐ฐ๐ฏ๐ต๐ฆ๐ฏ๐ต ๐๐ถ๐ฅ๐ช๐ต, ๐๐ฐ๐ฏ๐ต๐ฆ๐ฏ๐ต ๐๐ช๐จ๐ณ๐ข๐ต๐ช๐ฐ๐ฏ and ๐๐ณ๐ฆ๐ฑ๐ข๐ณ๐ช๐ฏ๐จ ๐ง๐ฐ๐ณ ๐ข๐ฏ ๐๐ ๐๐ญ๐ฐ๐ถ๐ฅ ๐ฑ๐ณ๐ฐ๐ซ๐ฆ๐ค๐ต.
- Further ASP.NET Core updates including ๐๐ฆ๐ต๐ถ๐ฑ ๐๐ช๐ต๐ฆ๐ค๐ฐ๐ณ๐ฆ ๐๐ฐ๐ฏ๐ต๐ฆ๐ฏ๐ต ๐๐ฆ๐ณ๐ช๐ข๐ญ๐ช๐ป๐ข๐ต๐ช๐ฐ๐ฏ and ๐๐ถ๐ญ๐ต๐ช๐ด๐ช๐ต๐ฆ ๐๐ณ๐ค๐ฉ๐ช๐ต๐ฆ๐ค๐ต๐ถ๐ณ๐ฆ.
ASP.NET Core SDK now supports MetaData Editing mode in XM Cloud
You can now, when logged into the XM Cloud Pages app, use the editing host selector to change over and connect directly to a locally running instance of your head.
Read more: https://tinyurl.com/2s62epaf
You can now, when logged into the XM Cloud Pages app, use the editing host selector to change over and connect directly to a locally running instance of your head.
Read more: https://tinyurl.com/2s62epaf
1.6.858 base released featuring a very diverse range of fixes:
- In patch configuration file, you can now define the maximum number of items returned in paginated GraphQL queries with the setting name
- While configuring insert option rules for page branches, clicking
- Resolved a case-sensitive validation issue that prevented sitemap media items from regenerating after a site name change.
- The workflow state of the Home item no longer affects redirect results in Preview or Edge responses.
- The Navigation Contents Resolver now respects the Use Context Item setting, ensuring compatibility with Faster Publishing (Publishing V2).
- A Content Hub image configured as the background image of a Container now appears as expected on the canvas.
- The resolution of Redirect Map for Edge has been optimized to prevent SQL Server overload.
- The
- New configurable cache-clearing logic helps ensure caches are properly invalidated and field values are correctly resolved.
- GRPC resource exhaustion issue during publishing is fixed.
- In patch configuration file, you can now define the maximum number of items returned in paginated GraphQL queries with the setting name
GraphQL.DefaultPageSize.- While configuring insert option rules for page branches, clicking
specified now correctly opens the action setup process. - Resolved a case-sensitive validation issue that prevented sitemap media items from regenerating after a site name change.
- The workflow state of the Home item no longer affects redirect results in Preview or Edge responses.
- The Navigation Contents Resolver now respects the Use Context Item setting, ensuring compatibility with Faster Publishing (Publishing V2).
- A Content Hub image configured as the background image of a Container now appears as expected on the canvas.
- The resolution of Redirect Map for Edge has been optimized to prevent SQL Server overload.
- The
ItemPathsCache is now thread-safe, meaning it will no longer become corrupted and throw an exception during concurrent requests.- New configurable cache-clearing logic helps ensure caches are properly invalidated and field values are correctly resolved.
- GRPC resource exhaustion issue during publishing is fixed.
Sitecore Cloud SDK v0.5.2 got updates for search
It improves search capabilities with the new
To get started, locate the IDs of the Sitecore Search sources you want to return results from, and add them to the source attribute for the relevant widget items, such as those used to request search results, recommendation content, or suggestions.
References:
- https://tinyurl.com/32ww4whk
- https://tinyurl.com/4jds94z3
- https://tinyurl.com/ycy89u8h
- https://tinyurl.com/2hujazh4
It improves search capabilities with the new
sources attribute, which lets you add a list of source IDs when you request content from Sitecore Search. If you do this, results will only be retrieved from the sources you listed, which is especially useful when filtering search results in a multi-site setup.To get started, locate the IDs of the Sitecore Search sources you want to return results from, and add them to the source attribute for the relevant widget items, such as those used to request search results, recommendation content, or suggestions.
References:
- https://tinyurl.com/32ww4whk
- https://tinyurl.com/4jds94z3
- https://tinyurl.com/ycy89u8h
- https://tinyurl.com/2hujazh4
โค2