Mosaic to Fresco Component Comparison Guide
This page explains how content widgets and certain functionality from the old Mosaic platform (Drupal 7) map to components in the new Fresco platform (Drupal 10). Its purpose is to provide clarity to web editors, site owners, and migration coordinators about how content will appear and behave after migration from Mosaic to Fresco.
Fresco is an evolving platform that will undergo iterative improvements responding to user needs and feedback. While this guide reflects the current state of the system, features and functionality are expected to continue developing over time.
Navigating this page:
Section 1 (the Quick Reference Summary) provides a summary of how Mosaic features correspond to Fresco components - what has changed, what’s new, and what has been removed or replaced.
Section 2 provides detailed information on each widget or feature, including recommended actions to prepare for migration.
This page does not cover technical implementation steps, HTML examples, or website publishing instructions.
Quick Reference Summary
Mosaic Widget | Fresco Component (if any) | Status | Key Notes |
Accordion | Accordion | Supported | Auto-migrates with WYSIWYG content converted to Text Component |
Accordion (Advanced) | Accordion | Changed | Migrates if the nested widgets are supported; will not currently allow nested accordions/tabs |
Background Images | – | Currently Removed | Background visuals not currently supported |
Banners | Banner | Changed | Layouts adjusted; video support removed |
Carousels | Listing / Selected Content / Card | Replaced | Migrates to Cards for accessibility |
Custom CSS & JS | – | Currently Removed | Custom code not currently supported |
Custom Domains | – | Supported (limited) | Max two custom domains per site |
Dropdown List | – | Currently Removed | No current equivalent component |
Footers | Footer | Changed | Standardised three-section layout. Requires manual creation post-migration. |
Forms | – | Currently Removed | Use external form tools (e.g. MS Forms) |
Grids | Listing / Selected Content / Card | Replaced | Split into three components by source type |
Headers | Header | Supported | Requires manual creation post-migration |
Image Gallery (Tiles & Featured) | Media Gallery | Supported | Max 15 images per gallery |
Lists | Listing / Selected Content / Card | Replaced | Same mapping logic as Grid |
Menus | Menu | Supported | Auto-migrates; review links after migration |
Metadata Display | – | Supported | Migrates into Reusable Content |
Reusable Content | Reusable Content | Supported | Migrates if nested widgets are supported |
Section Search | – | Unknown | Pending future review |
Share on Social Media | – | Currently Removed | Not currently supported |
Shared Content | Static Fresco Content | Currently Unsupported | Content migrates to Fresco but loses its dynamic link to the source. |
Sidebar Navigation | – | Currently Removed | Functionality not currently supported |
Simple Feedback Form | – | Currently Removed | Not currently on roadmap |
Slideshow | – | Supported | Content migrates, but no autoplay or automatic looping functionality |
Social Media Links | Icon Component | Supported | Not migrated, replacement component available. |
Symplectic Publications | Symplectic App (in development) | Planned | Integration under review |
| Tabs | Tabs | Supported | Auto-migrates with WYSIWYG content converted to Text Component; Icons within tab titles currently removed |
| Tabs (Advanced) | Tabs | Changed | Migrates if nested widgets are supported; will not allow nested accordions/tabs |
Taxonomy Terms Display | – | Supported | Pending confirmation |
Users | – | Changed | Only Site Owner migrated; migration team add migration contact before handover for review |
Vacancy Listing (CoreHR) | Embed Component | Unknown | Pending development |
Videos | Video Component | Changed | Must use externally hosted videos |
Web Application | Embed Component | Unknown | Pending development |
Widget Titles | Heading Component | Supported | Auto-migrates as H2 above component |
WYSIWYG (Text Editor) | Text Component | Changed | Toolbar simplified; custom code not currently supported |
Detailed Component Reference
This section provides a deeper look at each widget or feature, detailing:
- Status – Supported / Changed / Replaced / Removed
- What’s new – Key improvements in Fresco
- What’s changed – Differences in behaviour or layout
- What’s missing – Features not carried forward
- Recommended action – Steps for editors or site owners
Status: Supported
What’s new:
- Cleaner presentation and improved accessibility.
- Migrated content handled via Text Components inside an Accordion Component.
What’s changed:
- Accordion content migrates into Text Components instead of embedded WYSIWYG.
- Structural markup and ARIA attributes updated for modern standards.
What's currently missing:
- WYSIWYG toolbar changes.
- Currently no Expand All option.
Recommended action:
- Check each accordion post-migration to confirm section titles and content appear correctly. Review any formatting carried from WYSIWYG content.
Status: Changed
What’s new:
- Advanced Accordions migrate to standard Accordions in Fresco.
- Any supported Mosaic widgets inside them will migrate automatically if those widgets are set to auto-migrate.
What’s changed:
- Fresco does not currently support placing Tabs or Accordions inside an Accordion.
What's currently missing:
- Ability to nest Accordions or Tabs inside another Accordion.
- Currently no Expand All option.
Recommended action:
- Simplify Advanced Accordions in Mosaic before migration.
- Move any nested Accordion or Tab widgets outside the Accordion before migration.
Status: Currently Removed
What’s new:
- Background images from Mosaic are added to the Fresco Media Library so they remain available for reuse.
What’s changed:
- Fresco does not currently allow for the displaying of background images as part of page layouts or components.
What's currently missing:
- Ability to assign or display images as background visuals behind content.
Recommended action:
- Remove or replace background images in Mosaic before migration.
- Reintroduce them in Fresco using visible Media or Banner Components if needed for layout or visual effect.
Status: Replaced
What’s new:
- Fresco replaces Carousel functionality with Listing, Selected Content, and Card components.
- This approach removes auto-scrolling behaviour and aligns with accessibility standards.
- These alternatives maintain the same underlying content but use modern, accessible presentation styles.
What’s changed:
- Currently no dedicated Carousel component exists in Fresco.
- Carousels using:
- Filtered content source migrates to a Listing Component.
- Selected content source migrates to a Selected Content Component within a Fixed Grid.
- Static content source migrates to Card Components within a Fixed Grid.
- Pagination is added automatically where content exceeds layout limits:
- Portrait-style items in Grid layouts migrate into a four-item-per-row format.
- Landscape-style items migrate into a one-item-per-row format.
- Tertiary text fields are not currently supported.
- The visual design of Fresco Card layouts differs from the original Mosaic Carousel layouts, so migrated content will not appear identical.
What's currently missing:
- Carousel scrolling and rotation behaviour.
- Feed-based Carousels, as the Feed source option is not currently in development.
Recommended action:
- After migration, review all converted Carousels to check layout and visual presentation (Portrait vs. Landscape) and item-per-row count are appropriate for the content.
- Adjust layouts as needed to best fit the Fresco design system.
Status: Currently Removed
What’s new:
- Fresco enforces a consistent and accessible design system with currently no support for site-level custom code.
What’s changed:
- Any custom CSS or JavaScript added in Mosaic - whether in the footer, embedded in WYSIWYG content, or elsewhere - will currently no longer work after migration.
- Such code will appear as plain text within the migrated page content.
What's currently missing:
- Ability to apply site-specific styling or functionality through custom CSS or JavaScript.
Recommended action:
- Remove all custom CSS and JavaScript from Mosaic before migration.
- Where extra functionality is essential, you will be able to raise a feature request with the Fresco team for possible inclusion in future releases.
Status: Supported (limited)
What’s new:
- Fresco supports custom domains for migrated sites, with a limit of two per site.
What’s changed:
- Sites with more than two custom domains in Mosaic must select which two to retain on Fresco.
What's currently missing:
- Ability to assign more than two custom domains to a single site.
Recommended action:
- Before go-live, confirm which two domains should be retained on Fresco.
- Update any references, redirects, or external links that rely on domains no longer in use.
Status: Currently Removed
What’s new:
- None directly but Listing Components in Fresco include built-in filtering options for dynamic content, which provide a limited alternative to the Mosaic Dropdown List widget behaviour.
What’s changed:
- The Dropdown List widget from Mosaic currently has no direct replacement in Fresco.
What's currently missing:
- Ability to manually create dropdown lists for in-page-navigation or content filtering.
Recommended action:
- Restructure any Mosaic pages using Dropdown Lists before migration.
- Where filtering is required on Fresco, use the built-in filter options available within Fresco’s Listing Components.
Status: Removed
What’s new:
- Fresco does not include built-in form functionality but supports integrating external forms, such as Microsoft Forms or other approved tools.
- Microsoft Forms can now be embedded directly into Fresco pages using the Embed Component, once the Microsoft Forms embed service has been enabled for the site.
- External forms can also be linked from Fresco pages using hyperlinks or Button Components.
What’s changed:
- Mosaic form widgets do not migrate and cannot be recreated natively within Fresco.
- All existing forms must be rebuilt using an external platform, such as Microsoft Forms, and then linked or embedded into Fresco pages.
- Microsoft Forms is now available as a managed embed service within Fresco. A Site Owner or Site Administrator must enable the service before editors can use it.
What's currently missing:
- Native form builder within the CMS.
- Direct form submission and response management within Fresco.
Recommended action:
- Identify any existing Mosaic forms before migration.
- Rebuild these using Microsoft Forms or another approved external platform.
- Where possible, add an additional contributor to externally managed forms to ensure continuity of management.
- Integrate forms into Fresco using hyperlinks, Button Components or the Embed Component.
- For Microsoft Forms, ensure the embed service has been enabled on the site before attempting to embed a form.
- Test all forms after migration to confirm they display correctly and submissions work as expected.
Status: Replaced
What’s new:
- Fresco separates Mosaic’s Grid functionality into three dedicated components based on content source:
- Filtered/Dynamic source → Listing Component.
- Selected source → Selected Content Component.
- Static source → Card Components within a Tile Grid.
- This structure provides clearer functionality and greater consistency across content types.
- Listing and Selected Content Components offer five standardised display styles: Portrait Image, Portrait Text Only, Landscape Image, Landscape Thumbnail and Landscape Text Only.
- Portrait listings support up to five items per row, while Landscape listings display one item per row.
What’s changed:
- Grids no longer exist as a single component in Fresco.
- Dynamic (filtered) and Selected Grids now migrate automatically to their corresponding Fresco components.
- During migration, Mosaic display styles are mapped to the closest Fresco equivalent.
- Dynamic Grid migration preserves content type filters, taxonomy filters, sorting options, display styles, items per row and pagination settings.
- Portrait-style layouts support configurable items per row, up to a maximum of five, rather than a fixed four-item layout.
- Landscape-style listings display one item per row.
- The design, spacing and presentation of Fresco layouts may differ visually from their Mosaic equivalents.
What's currently missing:
- Mosaic’s rollover effects and certain visual layout styles.
- A single Grid Component that combines all three content source types.
Recommended action:
- Review each migrated Grid after migration to confirm that the layout, content source, filtering and display style are correct.
- Check that the expected content items appear, particularly in Selected Content Components.
- Use the appropriate component (Listing, Selected Content or Card within a Tile Grid) when recreating or adjusting Mosaic Grid functionality.
- Check the number of items displayed per row and adjust the layout settings where necessary.
- Review Grid layouts on desktop and mobile devices to ensure content displays correctly.
Status: New
What’s new:
- Fresco introduces a dedicated Header Component with three layout types:
- Standard Header – the default, general-purpose layout for most sites.
- Department Header – designed for departmental websites, with University branding options.
- Microsite Header – designed for smaller sub-sites requiring a distinct identity while remaining connected to a parent site.
- Department and Microsite headers can use approved University of Oxford brand colours, including additional departmental and institutional colours now available through Appearance > Theme. Colour selection is managed at site level rather than within the Header Component.
- The Header includes:
- A Header Title field (usually the site name), with a maximum of 118 characters.
- An optional Site Subtitle field (maximum 128 characters), displayed beneath the site title on screens 768px wide and above.
- Option to display or hide the University crest and select its shape.
- Option to add a custom site logo alongside the University logo.
- Configurable University crest link and link text.
- Assignable main navigation menu (migrated from Mosaic).
- Optional Quick Links menu, which can include internal or external links.
- Option to show or hide the search button, with an optional introductory text field displayed above the search tool.
- Ability to create additional headers for specific pages requiring different branding or navigation.
What’s changed:
- Mosaic did not have a distinct Header widget; header elements were managed through theming or menu configuration.
- Navigation menus migrate automatically but must be manually assigned to the new Header Component after migration.
- Header configuration is managed through Settings > Header and Footer.
- Department and Microsite header colours are controlled through the site-wide colour theme, which also affects other elements across the website.
- The Standard Header does not change colour when the site-wide theme is changed.
- Additional Header Components can be created and assigned to individual pages, overriding the default site header.
What's currently missing:
- Ability to configure header colours independently from the site-wide colour theme.
- Fully custom header colour selection directly within the Header Component.
Recommended action:
- After migration, assign the migrated navigation menu to the Header Component.
- Configure the appropriate layout type (Standard, Department or Microsite) and select the required site-wide theme colour where applicable.
- Review the Header Title, optional Site Subtitle, University crest visibility and custom site logo.
- Configure Quick Links and search overlay settings to meet the site's requirements.
- Check that navigation menus and links display and function correctly.
- Review the Header on desktop and mobile devices to ensure branding, navigation and search functionality display correctly.
Status: Changed
What’s new:
- Fresco combines the two Mosaic Image Gallery widgets into a single Media Gallery Component.
- Each Media Gallery can display up to 15 images per instance.
- All images from Mosaic are migrated into Fresco’s Media Library, ensuring that images beyond the 15-image display limit remain available.
- Media Galleries support image navigation and a lightbox for viewing individual images.
- Image captions and attributions now display beneath images with an information ('i') icon when populated.
What’s changed:
- Both ‘Image Gallery – Tiles’ and ‘Image Gallery – Featured Image’ now migrate automatically into the unified Media Gallery Component.
- Any Mosaic gallery containing more than 15 images will only include the first 15 in the migrated Media Gallery.
- Gallery titles from Mosaic are preserved during migration and displayed as H2 headings.
- Image captions and attributions migrate from Mosaic and are displayed beneath images rather than being restricted to the lightbox.
- Images can be reordered within the Media Gallery using drag-and-drop or editable order numbers.
- The layout and styling differ from Mosaic’s original presentation.
What's currently missing:
- Ability to display more than 15 images within a single Media Gallery.
- A documented option to hide captions independently within the Media Gallery Component.
Recommended action:
- Review each migrated Media Gallery to confirm that images, titles, captions and attributions display correctly.
- For galleries exceeding 15 images, create additional Media Gallery Components after migration and add the remaining images from the Media Library.
- Check the order of images and rearrange them where necessary.
- Review gallery layouts on desktop and mobile devices to ensure images display correctly.
Status: Changed
What’s new:
- Fresco supports internal linking through page references, allowing editors to link to existing pages without manually entering a full URL.
- Links created using Mosaic's system link tool are automatically corrected during migration, including supported node-based references.
- Relative links (e.g. /about/research) are supported and recommended for internal site navigation.
- Fresco supports URL redirects, including redirects from additional Mosaic URL aliases to the primary Fresco page alias.
What’s changed:
- Links created in Mosaic using full URLs (for example, including the .web.ox.ac.uk domain) are not automatically rewritten during migration.
- These links may continue to point to the old Mosaic website rather than directly to the new Fresco site.
- Relative links generally continue to work after migration, provided the corresponding page paths remain unchanged.
- Internal links created using Mosaic's system link tool are corrected automatically by the migration process.
- Manually entered links containing node IDs (e.g. /node/123) may break after migration because node IDs change in Fresco.
- A temporary redirect from the old Mosaic domain (.web.ox.ac.uk) to the new Fresco domain (.site.ox.ac.uk) is provided for approximately four months after go-live, where page paths match.
- Mosaic pages with multiple URL aliases migrate with one primary alias, while additional aliases are converted into redirects.
What's currently missing:
- Automatic correction of hardcoded full URLs that reference Mosaic pages.
- Automatic correction of manually entered links containing old Mosaic node IDs.
- Automatic migration of existing Mosaic 1:1 redirect rules, which must be recreated in Fresco.
- Bulk redirect management directly within the Fresco CMS.
Recommended action:
- Before migration, review your site for links containing full Mosaic URLs and replace them with relative links or page references where possible.
- Identify manually entered links containing node IDs (e.g. /node/123) and update them to use the correct page paths.
- For sites using custom domains, use relative links to ensure internal navigation works on both Mosaic and Fresco during the migration review period.
- After migration, test internal navigation and page links to confirm they point to the correct Fresco pages.
- Review migrated menu links for any remaining references to the old .web.ox.ac.uk domain.
- Check existing redirect requirements and recreate any Mosaic 1:1 redirects that are still needed.
- Update external references, bookmarks and published materials to use the new Fresco URLs before temporary redirects expire.
Status: Replaced
What’s new:
- Fresco combines Mosaic’s List and Grid widgets into a consistent set of three components, depending on content source:
- Filtered/Dynamic source → Listing Component
- Selected source → Selected Content Component
- Static source → Card Component
- This structure provides clearer control over how content is sourced and displayed.
What’s changed:
- Lists no longer exist as a single widget in Fresco.
- Layouts from Mosaic are mapped to the nearest Fresco equivalent (e.g. Row and Card layouts → Landscape or Portrait Image/Text formats).
- Portrait-style items migrate into a four-item-per-row layout.
- Landscape-style items migrate into a one-item-per-row layout.
- The overall appearance and spacing differ visually from Mosaic layouts.
What's currently missing:
- Certain older Mosaic layout styles such as “Row with separator” or “Breaker” currently have no exact visual match.
Recommended action:
- After migration, review each converted List to ensure layout and content presentation are correct.
- Use the Listing, Selected Content, or Card component that best suits each content type.
- Adjust layout or grouping as needed to maintain a clear, accessible presentation consistent with the new Fresco design.
Status: Changed
What’s new:
- Fresco introduces a configurable Metadata Component that allows editors to select which metadata fields to display.
- Available fields include: Page title, author, location, publication date, email address, event start date, event end date, event date custom, event presenter, phone number, URL, address, affiliation, role, job title, bio, social channels, listing title, listing text, listing image and listing link.
- Each Metadata Component displays one selected field, allowing editors to control which information appears.
- Editors can configure optional prefixes (e.g. "Job title:") and icons to accompany metadata values.
- Date metadata supports configurable display formats, including custom date formatting to show weekdays and times.
- This replaces Mosaic’s fixed metadata display, providing greater control over how information is presented across different content types.
What’s changed:
- In Mosaic, metadata fields were displayed together in a single widget with limited customisation.
- In Fresco, each field is represented by its own Metadata Component instance.
- During migration, Mosaic metadata displays are converted into Reusable Content instances containing multiple Metadata Components to replicate the grouped view.
- Metadata Components within Reusable Content can be edited centrally, with changes reflected across all pages using that Reusable Content item.
- Editors can adjust individual metadata fields, including their display settings, prefixes and date formats.
- Metadata fields that have no content may leave visible gaps and require the corresponding component instance to be removed.
What's currently missing:
- Ability to display multiple metadata fields within a single Metadata Component instance. This is planned for a future update but has not yet been released.
- Automatic removal of empty metadata fields to prevent gaps in the displayed content.
- Full reliability across all metadata field types, with some known issues affecting Location, Job Title, Bio and Event Presenter displays.
Recommended action:
- After migration, check that all expected metadata fields display correctly, particularly on Article, Event, Person and Location pages.
- Where multiple fields are required, group individual Metadata Components within a Reusable Content item.
- Review migrated Reusable Content to ensure all required metadata fields are enabled and correctly configured.
- Remove unused or empty Metadata Component instances where they create unwanted gaps.
- Configure prefixes, icons and date formatting where appropriate to improve the presentation of metadata.
- Check changes to shared Reusable Content carefully, as updates will affect all pages using that item.
- Be aware that future platform updates may introduce multiple field selections within a single Metadata Component, but this functionality is not currently available.
Status: Changed
What’s new:
- Fresco sites are assigned a new address format: sitename.site.ox.ac.uk, replacing the standard Mosaic address format (sitename.web.ox.ac.uk).
- A temporary redirect is put in place from the old Mosaic domain to the new Fresco address following the go-live switchover.
- These redirects remain active for approximately four months after go-live, allowing visitors using the old Mosaic address to reach the new Fresco site.
- Fresco provides search engine indexing controls through Settings > Site launch, allowing Site Owners to enable indexing once the site is live.
- Sites using custom domains can configure a preferred primary domain for search engines, ensuring canonical URLs reference the chosen domain.
What’s changed:
- Once the temporary redirect period ends, the old Mosaic URL will no longer redirect to Fresco and will display a "page not found" error.
- Fresco supports one primary URL alias per page. Additional aliases from Mosaic are automatically converted into redirects to the primary alias.
- Existing 1:1 redirect rules from Mosaic do not migrate automatically and must be recreated in Fresco.
- Search engine indexing is managed separately from making the website publicly accessible and must be enabled after the migration switchover.
- Fresco supports a maximum of two custom domains per site.
What's currently missing:
- Automatic migration of existing Mosaic 1:1 redirect rules.
- Bulk redirect management directly within the Fresco CMS.
- Permanent redirects from the old Mosaic domain after the approximately four-month temporary redirect period.
Recommended action:
- Communicate the new Fresco URL to users and stakeholders before the temporary redirect period expires.
- Update bookmarks, printed materials, external websites and third-party links that reference the old Mosaic address.
- Ensure external systems or partners referencing the site switch to the new .site.ox.ac.uk domain or the site's retained custom domain.
- Review existing Mosaic redirects and recreate any necessary 1:1 redirects in Fresco.
- After migration, test key URLs and navigation links to confirm redirects work correctly.
- Once the Fresco site is live and the migration switchover is complete, enable search engine indexing through Settings > Site launch.
- For sites using custom domains, confirm the preferred primary domain and review the associated search engine settings.
Status: Supported
What’s new:
- Fresco retains the Reusable Content feature, allowing content to be created once and displayed across multiple pages.
- Supported Mosaic widgets contained within Reusable Content migrate automatically into their corresponding Fresco Components.
- Reusable Content can now be added directly as a first-level section on a page, without needing to enable it in component settings.
- Fresco provides a dedicated Reusable Content management area under Content > Reusable Content, where editors can create, edit and manage shared content items.
- The management screen includes a usage count, allowing editors to see how many pages use each Reusable Content item.
What’s changed:
- The structure and terminology remain largely the same, but Fresco manages Reusable Content through its component-based system rather than Mosaic widgets.
- Reusable Content can be inserted directly into a page section or added as a component within supported layouts.
- Changes made to a Reusable Content item are reflected across all pages that reference it, reducing the need for repeated updates.
- During migration, supported nested widgets are converted into their Fresco equivalents.
- Unsupported nested widgets may not migrate correctly and require manual review or replacement.
- Mosaic Metadata Displays are also migrated into Reusable Content items containing individual Metadata Components.
What's currently missing:
- Automatic migration of unsupported Mosaic widgets contained within Reusable Content.
- No major gaps in the core Reusable Content functionality are documented in the Knowledge Base.
Recommended action:
- After migration, review all Reusable Content instances to confirm that their components and content have migrated correctly.
- Check that Reusable Content appears in the correct locations and displays as expected on all pages where it is used.
- Identify any unsupported or missing nested components and recreate them using the appropriate Fresco Components where possible.
- Continue to use Reusable Content in Fresco to manage shared information centrally and reduce duplication across pages.
- Use the Reusable Content management screen to review existing items and their usage across the site.
- When editing Reusable Content, check that changes are appropriate for every page where the item appears.
Status: Not Available
What’s new:
- Fresco does not include a dedicated Section Search Component.
- The global site search, available through the Header Component, provides an alternative for searching content across the website.
What’s changed:
- The Section Search widget from Mosaic is not available in Fresco and does not migrate.
- Section Search is not currently planned for development in the near future.
- Unlike Mosaic's Section Search, Fresco's global search searches across the site rather than restricting results to a specific section.
What's currently missing:
- Dedicated Section Search functionality within Fresco.
- Ability to restrict the standard site search to a specific section of the website.
Recommended action:
- If your Mosaic site currently uses the Section Search widget, review whether this functionality is still required before migration.
- Use Fresco's global site search through the Header Component as the recommended alternative.
- Where appropriate, review the site's navigation structure and consider using menus or the Local Navigation Component to help visitors find content within specific sections.
- If section-specific search is essential, raise the requirement with the Fresco Migration Support Team for further consideration.
Status: Removed
What’s new:
- Fresco does not include a dedicated Simple Feedback Form Component.
- External feedback forms, such as Microsoft Forms, can be linked to or embedded within Fresco pages using the Embed Component.
- Microsoft Forms embedding is now available as a managed service, which must be enabled for the site before use.
What’s changed:
- The Simple Feedback Form widget from Mosaic, which provided a basic “Was this page useful?” Yes/No interaction, is not supported in Fresco and does not migrate.
- The Simple Feedback Form is not currently included on the Fresco development roadmap.
- Feedback collection must be managed through an external platform rather than directly within Fresco.
What’s missing:
- Built-in page-level feedback functionality.
- A dedicated replacement for Mosaic's Simple Feedback Form widget.
- Native feedback submission and response management within Fresco.
Recommended action:
- Remove the Simple Feedback Form widget from Mosaic before migration.
- If feedback collection is required, consider creating a short external feedback form using Microsoft Forms or another approved platform.
- Link to the feedback form from the relevant Fresco page or embed it using the Embed Component.
- If using Microsoft Forms, ensure the managed embed service has been enabled by a Site Owner or Site Administrator.
- Test the feedback form after migration to confirm that it displays correctly and submissions work as expected.
Status: Supported
What’s new:
- Fresco introduces a dedicated Slideshow Component, replacing the Mosaic Slideshow widget.
- Static and Selected Content slideshows from Mosaic now migrate automatically into Fresco.
- Fresco supports two slide types:
- Static slides – created using Banner Components.
- Selected Content slides – referencing existing pages and displaying them using Banner layouts.
- Slideshows support manual navigation using previous and next controls, pagination dots and swipe gestures.
- Editors can configure an accessible title to help screen-reader users identify the slideshow.
- Slide indicator dots can be enabled or disabled through the Show pagination setting.
What’s changed:
- Fresco does not support autoplay or automatic looping. This is a deliberate accessibility improvement that removes automatic slide transitions.
- Fresco slideshows require a minimum of two and allow a maximum of six slides.
- During migration, only the first six slides from a Mosaic slideshow are carried over. Additional slides are not migrated.
- Static Mosaic slideshows migrate into Fresco Slideshow Components containing Banner Components.
- Selected Content slideshows migrate into Fresco Slideshow Components containing Selected Content Components, using the appropriate Banner display styles.
- Dynamic (filtered) slideshows that automatically update based on taxonomy rules are not supported as functioning Fresco slideshows and must be recreated manually.
- Mosaic slideshow properties such as autoplay, looping, slide duration and top/bottom margins are not carried over.
- Slides cannot be reordered after creation, so the sequence must be planned carefully.
What's currently missing:
- Autoplay and automatic looping functionality.
- Ability to configure the duration between slides.
- Ability to reorder slides after they have been created.
- Support for more than six slides within a single Slideshow Component.
- Dynamic (filtered) slideshows that automatically update based on taxonomy rules.
- Support for Quotation Components within slideshows.
- Consistent slide heights when combining different Banner layouts within the same slideshow.
Recommended action:
- Before migration, review any Mosaic slideshows containing more than six slides and identify which content should be retained or recreated separately.
- Review migrated slideshows to confirm that all expected slides, images, text and links display correctly.
- For dynamic (filtered) slideshows, manually recreate the required content using Banner or Selected Content slides.
- If a Mosaic slideshow had slide indicators disabled, check the migrated version and manually switch off Show pagination if necessary.
- Plan the slide sequence carefully before creating new slideshows, as slides cannot currently be reordered.
- Prioritise the most important content in the first one or two slides.
- Where possible, use consistent Banner layouts to avoid changes in slideshow height between slides.
- Configure a meaningful accessible title for each slideshow.
- Test slideshows on desktop and mobile devices to ensure navigation, pagination and content display correctly.
Status: Supported
What’s new:
- Fresco introduces a dedicated Symplectic Publications Component, replacing the Mosaic Symplectic Publications integration.
- The component is now available to all Fresco editor roles and can be added to any page type.
- Existing Mosaic Symplectic Publications widgets migrate automatically into Fresco.
- The component displays publications for one or more specified authors, using their Oxford SSO identifiers.
- Editors can configure publication filters, including publication type, author, favourite publications and publication series.
- Visitors can filter publications by subject, keywords, author, publication year, publication type and other enabled filtering options.
- Editors can configure the number of publications displayed per page, pagination and display options.
- Clicking a publication opens a pop-up displaying additional information, such as the abstract, DOI and publication details.
- The component automatically excludes publications marked as private or internal and inherits the site's Fresco theme colours.
What’s changed:
- The Symplectic Publications integration is no longer in development and is now fully released for editors.
- Existing Mosaic Symplectic Publications widgets migrate automatically into the corresponding Fresco Component, including their author settings.
- Editors no longer need to recreate the integration manually following a standard successful migration.
- Publication listings can be configured with additional filtering, pagination and display options.
- Symplectic Publications can also be displayed within Tabs as well as standard page layouts.
- Publication information is retrieved through the Symplectic integration rather than being maintained manually within Fresco.
What's currently missing:
- No major gaps in the core Symplectic Publications functionality are documented in the Knowledge Base.
- Some migration scenarios may still require manual correction, particularly for sites migrated before improvements to the handling of multiple author SSO identifiers.
Recommended action:
- Before migration, identify any existing Symplectic Publications widgets and record the author SSO identifiers used.
- Sites using Symplectic Publications no longer need to delay migration solely because the integration is unavailable.
- After migration, review the Symplectic Publications Component to confirm that author identifiers and publication listings have migrated correctly.
- Where multiple author SSO identifiers are used, check that each identifier appears as a separate entry.
- Verify that the expected publications display correctly and that private or internal publications are excluded.
- Review publication filters, pagination and display settings to ensure they meet the site's requirements.
- Check the component on desktop and mobile devices to ensure publication listings and pop-up details display correctly.
Status: Supported
What’s new:
- Tabs migrate automatically with all sections and titles retained.
- Content within each tab is converted from WYSIWYG to Text Components.
What’s changed:
- Icons within tab section titles are not supported in Fresco.
- Any formatting or features not supported in the new Text Component toolbar will be adjusted automatically.
What’s missing:
- Icon support within tab titles.
Recommended action:
- Review tab content after migration to confirm all text and formatting display correctly.
- Remove or simplify any icons in tab titles in Mosaic before migration.
Status: Changed
What’s new:
- Advanced Tabs migrate to standard Tabs in Fresco.
- Supported Mosaic widgets placed inside them will migrate automatically if those widgets are also set to auto-migrate.
What’s changed:
- Fresco does not support placing Tabs or Accordions inside another Tabs component.
- Unsupported nested content will not migrate.
What’s missing:
- Ability to nest Tabs or Accordions within other Tabs.
Recommended action:
- Simplify Advanced Tabs in Mosaic before migration.
- Move any nested Tabs or Accordions outside the Tabs component.
- Recreate necessary content manually in Fresco using supported components.
Status: Supported
What’s new:
- Fresco maintains support for taxonomy terms, allowing them to be displayed and applied across similar areas as in Mosaic.
- The underlying structure has been updated for consistency with Fresco’s component model and improved data handling.
What’s changed:
- Migration is largely like-for-like, though there may be some areas where taxonomy application is still being reviewed or extended.
- Any future changes will expand where taxonomy terms can be applied within components or content types.
What's currently missing:
- None identified, although a few use cases for taxonomy application are still under review.
Recommended action:
- After migration, confirm that all taxonomy terms display correctly and remain associated with the right content.
- Report any missing or unexpected taxonomy applications to the Fresco team (or Migration Team if you’re site is not yet ‘live’) so they can assess and address them in future updates.
Status: Changed
What’s new:
- Fresco introduces a revised user management system aligned with updated platform permissions and roles.
What’s changed:
- Only the Site Owner account from each Mosaic site is migrated automatically.
- If a Migration Contact is defined, that user will also be given an account on the Fresco site.
- Other Mosaic user accounts will not migrate and will need to be recreated manually in Fresco if required.
What's currently missing:
- Automatic migration of all user accounts and their individual permissions.
Recommended action:
- Before migration, identify which users should have access to your Fresco site.
- After migration, manually add any required users and assign appropriate roles.
- Confirm Site Owner and Migration Contact details are accurate ahead of migration to avoid access issues.
Status: Unknown
What’s new:
- The future approach to handling vacancy listings in Fresco is still being considered.
What’s changed:
- The existing CoreHR-based Vacancy Listing widget will likely not migrate automatically.
- It is not yet confirmed whether a replacement application or component will be developed.
What's currently missing:
- Confirmed solution for managing or displaying vacancy listings in Fresco.
Recommended action:
- Monitor programme updates for guidance on how vacancies should be managed in Fresco once a decision is made.
Status: Changed
What’s new:
- Fresco introduces a Video Component that embeds externally hosted videos.
- Supported platforms include YouTube, Vimeo, and Microsoft Stream.
- Videos are managed through an internal library of externally hosted content, providing consistency across sites.
What’s changed:
- Locally hosted videos from Mosaic will not migrate.
- Videos must now be uploaded to an external hosting service and linked into Fresco using the Video Component’s URL field.
What's currently missing:
- Ability to host video files directly within the CMS.
Recommended action:
- Before migration, upload all Mosaic video files to an approved external hosting platform.
- Record or note the new video URLs for easy re-linking in Fresco.
- After migration, recreate video placements using the Video Component, selecting from your hosted video library.
Status: Changed
What’s new:
- Fresco supports embedded third-party integrations through the Embed Component, subject to approval and security review.
- This provides a controlled and consistent way to display external tools such as Cosy or SDS Figshare.
What’s changed:
- Web applications and integrations used on Mosaic will not migrate automatically.
- Each integration must be reconfigured manually after migration.
- Some integrations may require redevelopment or explicit approval before being embedded in Fresco.
What's currently missing:
- Automatic migration or preconfigured support for third-party web applications.
Recommended action:
- Identify any existing Mosaic web application integrations before migration.
- Notify the Fresco team of your integration requirements early so they can review compatibility and security.
- After migration, use the Embed Component or a newly developed equivalent to reintroduce approved integrations.
Status: Supported
What’s new:
- During migration, each Mosaic widget title is automatically converted into a Heading Component in Fresco.
- The heading text is populated with the original widget title and assigned H2 style by default.
- The new Heading Component is placed directly above the corresponding migrated component.
What’s changed:
- Widget titles are now handled as standalone components rather than fields within each widget.
- Editors can independently reposition, retag, or remove these headings as needed.
What's currently missing:
- None. The title information and functionality are fully preserved in the new structure.
Recommended action:
- After migration, review all automatically generated Heading Components to ensure the hierarchy and placement makes sense within each page.
- Adjust heading levels or remove unnecessary titles to maintain clear content structure and accessibility.
Status: Changed
What’s new:
- Fresco replaces the Mosaic WYSIWYG widget with a simplified Text Component.
- Images previously added within Mosaic WYSIWYG content are now migrated into the Text Component but should be removed and handled separately through the Image Component for better consistency during your migration clean-up.
- The editor has been streamlined to focus on accessible, supported formatting tools.
What’s changed:
- Fresco does not currently support custom code, scripts, or HTML editing. Any such content from Mosaic will appear as plain text.
- The toolbar has been simplified. Many options have been removed or replaced by dedicated components (e.g. Icon, Quote, Embed, Video).
- Several layout and style features are now handled through structured components instead of inline editing.
- Image display options have changed, with new standardised size mappings:
Mosaic Sizes | Mapped to Fresco | Width (px) | Height (px) |
small / medium / ratio_4_3 | Small 4:3 | 293 | 220 |
small_square / medium_square / thumbnail | Small Square | 220 | 220 |
large / default | Medium 4:3 | 667 | 500 |
large_square | Medium Square | 500 | 500 |
ratio_6_4 | Small 16:9 | 391 | 220 |
What's currently missing:
- HTML “Source” editing.
- Snippets, Layouts, and other advanced controls.
- Custom styles, highlights, or inline icons.
- Embedded iframes (replaced by dedicated Embed or Video components).
Recommended action:
- Remove any custom code within Mosaic WYSIWYG areas, as it will not render in Fresco.
- Use structured components for features that were previously handled within WYSIWYG, such as quotes, videos, and icons.
- After migration, review all text formatting and inline images to confirm they display correctly using the new Text Component styling.
Status: Supported (replacement available)
What’s new:
What’s changed:
What's currently missing:
Recommended action: