Sitecore slipped out a small batch of Content Hub changes on April 3, 2026. None of these look like a massive platform reset, but a couple of them are worth paying attention to if you manage imports, metadata quality, or day-to-day admin friction.
The short version: Content Hub added AI-assisted alt text generation at the field level, made backup packages automatic for all import jobs, and shipped a useful set of resolved issues.
What Changed
AI-assisted Field-level Text Generation
This one is narrow, but potentially useful!
Sitecore says you can now use AI to generate alt text for images, but only for the SC.Asset.AltTextfield on the asset definition.
Why it matters:
- Better alt text can improve accessibility
- It can also help with SEO if the generated text is actually accurate
- It reduces some of the repetitive manual effort around image metadata
Who should care:
- DAM administrators
- Content teams managing large image libraries
- Anyone trying to improve accessibility without making asset entry even slower
The obvious watch-out is quality control. AI-generated alt text can be helpful, but it can also be wrong, vague, or strangely overconfident. If you rely on alt text for compliance or real accessibility outcomes, this should probably be treated as a starting point, not a final answer.
Automatic Backup Packages for all Import Jobs
This is the most practical change in the bunch.
Sitecore now automatically creates backup packages for all import jobs. Before this, backup packages were only created when the source and target environments were on different Content Hub versions.
Why it matters:
- Recovery is more predictable
- Import operations get a more consistent safety net
- Teams no longer have to remember the old version-mismatch condition to know whether a backup exists
Who should care:
- Platform owners
- Developers moving configuration or content between environments
- Admins responsible for rollback and change control
The main thing to watch is operational overhead. Sitecore’s note does not say much about storage impact, retention behaviour, or whether there are any cases where this backup generation changes import timing. That does not make it a bad feature. It just means you should confirm how it behaves in your tenant before assuming it is free.
Resolved Issues Worth Noting
The April 3 resolved issues entry is a mixed bag, but a few fixes stand out because they remove annoying edge cases.
Notable fixes include:
- Validation errors now appear when someone tries to add an entity to its own taxonomy relation where that relation should not allow it
- Custom option list facets now show the configured value or label instead of an internal identifier
- Serialization now preserves the
Allow_Updates: falsesetting correctly for entity definitions - Re-importing a package from the same tenant no longer changes certain date format settings and creates false modified-state noise
- Duplicate detection handling for asset master file changes was fixed when non-master files are excluded
- Everyone now has read permissions on the Visualization setting so colour settings are selectable
Why this matters:
- Admin and authoring screens should be a bit less confusing
- Serialization behaviour becomes more trustworthy
- Import and package workflows should generate less fake churn
- Some tenant configuration edge cases should be less fragile
Who should care:
- Solution architects
- Content Hub admins
- Teams using serialization and package-based movement between environments
- Anyone who has been burned by import weirdness or noisy configuration drift
The Practical Takeaway
If you only care about one item here, make it the import backup change. That is the clearest operational improvement.
The AI alt text feature is interesting, but it is still the sort of feature that needs human judgement around it. Useful? Probably. Fully trustworthy? Not yet.
The resolved issues list is not all that flashy, but this is the kind of maintenance work that usually matters more than the headline features. Fewer false changes, clearer labels, and better guardrails are all good things.
A seasoned Senior Solutions Architect with 20 years of experience in technology design and implementation. Renowned for innovative solutions and strategic insights, he excels in driving complex projects to success. Outside work, he is a passionate fisherman and fish keeper, specializing in planted tanks.