Minor Changes
-
Add
sitecore-tools project experimental listto show the experimental features available in the current Content SDK app. (e1d0156)
The command reads the app's framework package (@sitecore-content-sdk/nextjsor@sitecore-content-sdk/angular) and prints each feature with its enabled status. Framework packages now exportexperimentalFeaturesCatalogfrom their/experimentalentry. -
Schema.org & JSON-LD Support (b858df1)
-
minor
@sitecore-content-sdk/contentdependency update:-
[angular] Metadata, Open Graph and Schema.org & JSON-LD Support
-
@sitecore-content-sdk/content:resolvePageMetadataFields(withPageMetadataRouteFields/ResolvedPageMetadataFields) moved from@sitecore-content-sdk/nextjsto@sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules.@sitecore-content-sdk/nextjskeeps re-exportingPageMetadataRouteFields. -
@sitecore-content-sdk/angular: addedPageMetadataService+<sc-page-meta-tags [route]>(<title>, metadata and Open Graph<meta>tags via Angular'sTitle/Metaservices) andJsonLdSchemaService+<sc-json-ld-schema [page]>(a single<script type="application/ld+json">in<head>, normal mode only). Re-exported thePageMetadataFields,MetadataFields,OpenGraphFields,OpenGraphImageField(Value)andPageMetadataRouteFieldstypes. -
Angular template:
LayoutComponentrenders both components;RouteFieldsextendsPageMetadataFields. (c7801c3)- Avoid throwing errors in scClient calls when context ID in browser is missing.
- Replaces the GraphQL client used by scClient with no-op fallback in browser context, when public content ID is missing, preventing
getPage(),getDictionary()and other GraphQL-bound method from throwing. - Adds a guard into
getHeadLinks()call to return empty results when client context ID is missing, instead of throwing an error. - Client Context ID becomes required for rendering head links. (5184ea7)
-
-
minor
@sitecore-content-sdk/reactdependency update:- Schema.org & JSON-LD Support (b858df1)
Patch Changes
-
[angular] Metadata, Open Graph and Schema.org & JSON-LD Support (c7801c3)
@sitecore-content-sdk/content:resolvePageMetadataFields(withPageMetadataRouteFields/ResolvedPageMetadataFields) moved from@sitecore-content-sdk/nextjsto@sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules.@sitecore-content-sdk/nextjskeeps re-exportingPageMetadataRouteFields.@sitecore-content-sdk/angular: addedPageMetadataService+<sc-page-meta-tags [route]>(<title>, metadata and Open Graph<meta>tags via Angular'sTitle/Metaservices) andJsonLdSchemaService+<sc-json-ld-schema [page]>(a single<script type="application/ld+json">in<head>, normal mode only). Re-exported thePageMetadataFields,MetadataFields,OpenGraphFields,OpenGraphImageField(Value)andPageMetadataRouteFieldstypes.- Angular template:
LayoutComponentrenders both components;RouteFieldsextendsPageMetadataFields.
-
Fix App Router redirect-map rules not matching locale-prefixed paths.
RedirectsProxynow removes the request locale from the path before matching, so a rule like^/page$matches/page,/en/pageand/da/page, even when that locale isn't listed inredirects.locales. A target locale taken from a regex capture keeps its configured casing (for exampleen-CA). (96d3617) -
Added
getPathnamehelper toProxyBase. UpdatedLocaleProxy,MultisiteProxyandPersonalizeProxyto use this helper. (2b0c7c2) -
Merge the
stylepassed toImageandNextImageover the default empty image placeholder's inline styles, so the 48px minimum size can be overridden. (f70de24) -
Honor custom
modifyComponentPropscallbacks in the Next.jsPlaceholderafter injecting component data. Use rendering UIDs for placeholder component and error boundary keys, falling back to the layout component name and index when no UID is available. (643022e) -
MultisiteProxynow resolves the site from the unprefixedsitequery string parameter only for draft mode App Router requests, so third-party requests containing?site=...no longer override the resolved site or overwrite thesc_sitecookie. (d6b8d75)If you need to force the site via query string, use the
sc_siteparameter (the supported one) instead ofsite. Site resolution in editing is unaffected. -
Enable Turbopack support for the component props loader in the Next.js Pages Router template, so
getComponentServerPropsis stripped from client bundles. Also fix the loader's package export path and make the webpack rule work on all platforms. (f0d8e2f) -
Expose
buildSitecoreItemCacheTagsince it is common to want cache GraphQL responses from Sitecore for a page and have them revalidate on publish. (aafdea4) -
Fix
403 Forbiddenforpublicfolder static files (e.g..svg,.woff2) in Pages Builder editing mode.PreviewProxynow skips known static asset extensions, and the templateproxy.tsmatcher excludes them. (39e7906)