We've refined how users discover and install Marketplace fragments from inside the Page Builder. Browsing, previewing, and installing partner and community fragments now feel native to the editing flow—fewer clicks, clearer discovery, and less context switching between the editor and the Marketplace. Native, already-installed, and Marketplace-available fragments now live side by side in the same experience.

Key Benefits:

• Faster discovery and installation of Marketplace fragments without breaking the editing flow.

• Clearer distinction between native, installed, and Marketplace-available fragments, so builders pick the right one at a glance.

• Less context-switching: everything happens inside the Page Builder instead of jumping to the Marketplace and back.

This release rounds out the Pages Management APIs with new endpoints, broader page-type coverage, and refinements to how references and scopes are handled. The updates close long-standing gaps — supporting more page types end-to-end, expanding the catalog of page elements and fragments exposed through the API, and hardening the data architecture around scopes and secure references. The result is more reliable imports, exports, and staging across every site component.

Key Benefits:

• Broader API coverage: every page type is now supported end-to-end, not just the subset covered before.

• Fewer surprises in staging: scope-aware identifiers catch missing references and deleted assets before they break the live site.

• Consistent behavior across sites, staged environments, and imported content — the API no longer behaves differently depending on the page type.

CMS administrators can now modify content structures and their repeatable fields after publication — adjusting field configurations, nesting order, and repeatable settings without deleting existing content. Teams iterate on their data models as business needs shift, and all previously published entries stay intact.

Key Benefits:

• Refine your content model based on real-world usage instead of locking in every decision up front.

• Skip the "delete everything and rebuild" cycle when requirements change — existing entries come along for the ride.

• CMS admins adjust structures directly, without pulling in developers or database work for every tweak.

Data modelers can now define Link Content fields that let content creators select existing entries from other objects—single or multiple—instead of retyping the same values across entries. The CMS moves from isolated documents to a connected data model, so information like vendor names, categories, or authors stays consistent across every publication.

Key Benefits:

• Eliminate typos and inconsistencies by picking existing entries instead of re-entering text.

• Reuse the same author, category, or vendor across hundreds of entries—update it once and it propagates everywhere.

• Support both single and multi-select relationships, from "one author per article" to "many products per campaign.”