Sitecore/content-sdk @sitecore-content-sdk/angular@1.1.0

on GitHub

Minor Changes

• [angular] llms.txt Support (c7801c3)

  Added createLlmsTxtMiddleware({ client, sites }), an Express handler serving the llms.txt content managed via SitecoreAI for the site resolved by host name. The Angular template mounts it at /llms.txt.

• [angular] Metadata, Open Graph and Schema.org & JSON-LD Support (c7801c3)

  • @sitecore-content-sdk/content: resolvePageMetadataFields (with PageMetadataRouteFields / ResolvedPageMetadataFields) moved from @sitecore-content-sdk/nextjs to @sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules. @sitecore-content-sdk/nextjs keeps re-exporting PageMetadataRouteFields.
  • @sitecore-content-sdk/angular: added PageMetadataService + <sc-page-meta-tags [route]> (<title>, metadata and Open Graph <meta> tags via Angular's Title/Meta services) and JsonLdSchemaService + <sc-json-ld-schema [page]> (a single <script type="application/ld+json"> in <head>, normal mode only). Re-exported the PageMetadataFields, MetadataFields, OpenGraphFields, OpenGraphImageField(Value) and PageMetadataRouteFields types.
  • Angular template: LayoutComponent renders both components; RouteFields extends PageMetadataFields.

• Add sitecore-tools project experimental list to show the experimental features available in the current Content SDK app. (e1d0156)
  The command reads the app's framework package (@sitecore-content-sdk/nextjs or @sitecore-content-sdk/angular) and prints each feature with its enabled status. Framework packages now export experimentalFeaturesCatalog from their /experimental entry.

• minor @sitecore-content-sdk/content dependency update:

  • [angular] Metadata, Open Graph and Schema.org & JSON-LD Support

  • @sitecore-content-sdk/content: resolvePageMetadataFields (with PageMetadataRouteFields / ResolvedPageMetadataFields) moved from @sitecore-content-sdk/nextjs to @sitecore-content-sdk/content/layout, so every framework shares the same field-to-tag rules. @sitecore-content-sdk/nextjs keeps re-exporting PageMetadataRouteFields.

  • @sitecore-content-sdk/angular: added PageMetadataService + <sc-page-meta-tags [route]> (<title>, metadata and Open Graph <meta> tags via Angular's Title/Meta services) and JsonLdSchemaService + <sc-json-ld-schema [page]> (a single <script type="application/ld+json"> in <head>, normal mode only). Re-exported the PageMetadataFields, MetadataFields, OpenGraphFields, OpenGraphImageField(Value) and PageMetadataRouteFields types.

  • Angular template: LayoutComponent renders both components; RouteFields extends PageMetadataFields. (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)
  • Apply rewriteMediaUrls to SitecoreClient.getData results so custom Experience Edge hostnames are rewritten in component GraphQL data. (5509bcd)
  • Schema.org & JSON-LD Support (b858df1)

Patch Changes

• Expose buildSitecoreItemCacheTag since it is common to want cache GraphQL responses from Sitecore for a page. (aafdea4)

• <sc-placeholder-metadata> now renders with display: contents, so components inside a placeholder lay out correctly in flex and grid containers in editing mode. (0356f0f)

  The wrapper element that emits the Sitecore chrome markers had no styles and therefore rendered as display: inline. Inside a flex or grid parent, the wrapper became the flex/grid item instead of the component, so the component's own layout styles (e.g. display: block, flex sizing) no longer applied to the parent layout and the page looked different in the Pages editor than in the published site.