Five Sitecore updates worth discussing: grounded AI content, broader field assistance, better alt text, Content Hub fixes, and a more connected product experience.
Sitecore shipped a mixed batch of updates in early September. The headline is AI, but the practical story is broader: Sitecore is trying to make trusted content easier to reuse, routine metadata easier to create, and its products feel less like separate tools bolted together.
Some of this is available now. One of the most interesting pieces is still early access.
Here’s what changed and what I’d watch before enabling anything broadly.
SitecoreAI DAM Can Now Ground AI Tools Through Scrunch
The biggest update is an early access integration between SitecoreAI DAM, also referred to as Sitecore Content Hub in the announcement, and Scrunch Knowledge Studio.
Knowledge Studio can turn approved DAM source documents into structured, AI-ready knowledge documents. Scrunch agents review drafts for sensitive content, factual errors, and conflicting information before a person approves them. Approved documents can then be used as grounding input for AI-optimized content.
The useful part is the connection to managed brand content. Product specifications, FAQs, and other approved material often live inside a DAM but remain invisible to public-web AI tools. This integration is intended to make that trusted material usable without pretending the open web is an accurate source of brand truth.
The basic workflow is:
- Connect SitecoreAI DAM to Scrunch.
- Select DAM source documents and generate a knowledge document.
- Review the generated document and the agent-raised issues.
- Approve it for use as grounding input.
- Refresh and regenerate it when the DAM sources change.
That last step is the one to watch-out for. Grounding content is only trustworthy if somebody owns its refresh cycle. A polished answer based on stale product information is still a wrong answer.
This capability is currently limited to selected Sitecore organizations. If it fits a real use case, contact your Sitecore account or partner manager about early access rather than designing a production workflow around assumed availability.
AI-assisted Generation Now Works Across Entity Types
Sitecore has extended AI-assisted content generation so it can be enabled for fields on any entity definition. It is no longer limited to a narrow set of content types.
That opens up useful options for teams with custom data models. Text-based fields can get targeted AI assistance where it actually reduces repetitive work instead of forcing every workflow into the same template.
The practical advice is to start with specific, reviewable fields. Pick places where the source context is clear and a person can quickly judge the result. Enabling AI everywhere because the switch exists is not a content strategy.
Alt Text Gets a More Focused Assist
Sitecore also added image-aware generation for Alt text fields. When configured, the feature analyses an image and drafts a relevant description.
This should help teams reduce blank alt fields and get accessibility work into the normal asset workflow. It is assistance, though, not automatic accessibility compliance.
Generated alt text still needs editorial review. Context matters: the same image may need a different description depending on how and why it appears on a page. Decorative images may not need descriptive alt text at all. Treat the generated result as a first draft.
Content Hub Received Five Practical Fixes
The September 4 resolved-issues note contains a handful of smaller changes:
- DateTimeOffset companion field values can now be retrieved from Experience Edge.
- Renaming a Stateflow should no longer time out because of an unnecessary relation load.
- Long state names and borders render more cleanly in the full State Flow viewer.
- Sidebar panels now use a centred chevron as the close control.
- Spacing between member groups has been improved when labels are hidden in full-page edit mode.
The first two are the ones most likely to matter operationally. If you built a workaround for the Experience Edge field issue or avoided Stateflow renames because of timeouts, this is a good time to retest that workflow before removing the workaround.
Sitecore is making the product family feel more connected
The September 8 SitecoreAI update describes background work to bring applications into a more consistent environment. Sitecore says the result includes a shared design system, familiar navigation patterns, one login, unified navigation, simpler onboarding, shared services, and more connected cross-product workflows.
The company also says users may feel as though nothing has changed. That’s probably the right outcome for platform plumbing: less friction without a dramatic migration moment.
Teams that work across several Sitecore products should care most. Consistent navigation and fewer context switches can make routine work easier, especially for occasional users who never built up deep muscle memory in every application.
Still, “one login” and “connected workflows” cover a lot of ground. Validate the actual experience across the applications and roles your team uses instead of assuming every boundary has disappeared.
The Practical Takeaway
This batch points in a sensible direction. Sitecore is widening AI assistance while putting more attention on trusted source content, accessibility metadata, and cross-product consistency.
The strongest idea here is not AI generation by itself. It is the attempt to connect generation to approved, maintained content and a review step. That is the difference between a useful workflow and a confident content machine making things up.
For most teams, the next steps are straightforward: identify one controlled AI-assisted field to pilot, keep a human in the review loop, retest any Content Hub workarounds affected by the fixes, and ask about Scrunch only if there is a clear grounding use case.
