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.
- 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: Currently Removed
What’s new:
- Fresco does not currently include built-in form functionality but supports embedding external forms such as Microsoft Forms or other approved tools.
What’s changed:
- Mosaic form widgets will not currently migrate and cannot be recreated natively within Fresco.
- All existing forms must be rebuilt externally and then linked or embedded into Fresco pages.
What's currently missing:
- Native form builder within the CMS.
- Direct data handling or submission management inside Fresco.
Recommended action:
- Identify any existing Mosaic forms before migration.
- Rebuild these using Microsoft Forms or another approved platform.
- Integrate them into Fresco using hyperlinks or the Embed component (when available).
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 Component
- This structure provides clearer purpose and consistency between content types.
What’s changed:
- Grids no longer exist as a single component in Fresco.
- Layouts from Mosaic are mapped to the closest Fresco equivalent (e.g. Tile and Card layouts to Portrait or Landscape Image/Text formats).
- 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.
- The design and spacing of Fresco layouts may differ visually from Mosaic equivalents.
What's currently missing:
- Mosaic’s rollover effects and certain visual layout styles.
Recommended action:
- Review each migrated Grid after migration to confirm that layout, content source, and presentation display as expected.
- Use the appropriate component (Listing, Selected Content, or Card) to recreate Mosaic Grid functionality.
Status: New
What’s new:
- Fresco introduces a dedicated Header Component with three layout types:
- Standard Header – for most sites.
- Department Header – includes departmental branding options.
- Microsite Header – for smaller or standalone sites.
- Departments and microsites can select from approved University of Oxford brand colours, with plans to expand or allow custom colour requests in future.
- The Header includes:
- A Header Title field (usually the site name).
- Option to display or hide the University crest.
- 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 intro text field displayed in the search overlay.
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 post-migration.
What's currently missing:
- None. This is a new feature introduced in Fresco.
Recommended action:
- After migration, assign your migrated menu instance to the Header Component.
- Configure layout type (Standard, Department, or Microsite) and select colour options.
- Review crest visibility, quick links, and search overlay settings to ensure they meet your site’s needs.
Status: Changed
What’s new:
- Fresco combines the two Mosaic Image Gallery widgets into a single Media Gallery Component.
- Currently each Media Gallery can only display up to 15 images per instance.
- All images from Mosaic are migrated into Fresco’s Media Library, ensuring no files are lost even if they exceed the display limit.
What’s changed:
- Both ‘Image Gallery – Tiles’ and ‘Image Gallery – Featured Image’ now migrate into the same unified component.
- Any Mosaic gallery containing more than 15 images will only display the first 15 after migration.
- The layout and styling differ slightly from Mosaic’s original presentation.
What's currently missing:
- Ability to display more than 15 images within a single Media Gallery.
- Image captions are not visible within the component until you click on an image to open a lightbox.
Recommended action:
- For galleries exceeding 15 images, split them into multiple Media Gallery Components before or after migration.
Status: Changed
What’s new:
- Fresco supports the same approach to linking as Mosaic, where internal links can be created by referencing a page rather than typing a full path.
- This ensures links remain accurate after migration if they were originally set using the page reference (node) method.
What’s changed:
- Links created in Mosaic using a full URL path (for example, including the full domain) will not automatically update during migration.
- These links will continue to point to the old Mosaic address rather than the new Fresco site.
- Only relative links (e.g. /about/research) will update automatically to the correct migrated page.
What's currently missing:
- Automatic correction for links that use full URLs to Mosaic pages.
Recommended action:
- Before migration, review your site for any links that use full Mosaic URLs and replace them with relative links where possible.
- After migration, test internal navigation to confirm that all links point to the correct Fresco pages.
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.
- This replaces Mosaic’s fixed metadata display, giving editors more control over which details appear on each page or content type.
What’s changed:
- In Mosaic, all metadata fields were shown together in one widget with no ability to customise.
- 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 same grouped view.
What's currently missing:
- Ability to display multiple metadata fields within a single component instance (planned for a future update).
Recommended action:
- After migration, check that all expected metadata fields display correctly.
- On Fresco, where multiple fields are needed, group them within a Reusable Content instance.
- Keep in mind that future platform updates aim to allow multiple field selections within a single Metadata Component, with field mapping options by content type (e.g. Page, Event, Article, Person).
Status: Changed
What’s new:
- Fresco sites are assigned a new address format: <sitename>.site.ox.ac.uk.
- A temporary redirect will be in place from the old Mosaic domain (<sitename>.web.ox.ac.uk) to the new Fresco address once the site is published.
- Search engines will be notified that the site has moved to help retain visibility.
What’s changed:
- After the temporary redirect period ends, the old Mosaic URL will break and will display a “page not found” error.
What's currently missing:
- No major functionality changes beyond the address structure.
Recommended action:
- Communicate your new Fresco URL to users and stakeholders before the temporary redirect expires.
- Update any bookmarks, printed materials, or third-party links that use the old Mosaic address.
- Ensure external systems or partners referencing your site switch to the new .site.ox.ac.uk domain.
Status: Supported
What’s new:
- Fresco retains the Reusable Content feature, allowing content to be created once and displayed in multiple places.
- Supported Mosaic widgets contained within Reusable Content will migrate automatically.
What’s changed:
- The structure and terminology remain largely the same, but Fresco handles reusable content through the new component-based system rather than widgets.
What's currently missing:
- None. Core functionality is maintained.
Recommended action:
- After migration, review any Reusable Content instances to confirm that all components have migrated correctly.
- Continue to use Reusable Content in Fresco to manage shared information centrally and reduce duplication across pages.
Status: Unknown
What’s new:
- None at present. There is currently no Section Search component in Fresco.
What’s changed:
- The Section Search widget from Mosaic is not currently being redeveloped for Fresco.
- Its future depends on whether the small number of sites that used it - primarily those with pages behind SSO - still require that functionality.
What's currently missing:
- Dedicated Section Search capability within Fresco.
Recommended action:
- If your Mosaic site currently uses the Section Search widget, assess whether this functionality is still needed.
- Where possible, replace it with standard search or navigation features in Fresco.
Status: Removed
What’s new:
- None. There is no equivalent feedback form component in Fresco currently.
What’s changed:
- The Simple Feedback Form widget, which provided a basic “Was this page useful?” Yes/No interaction, is not included in Fresco’s initial release and is not currently on the development roadmap.
What’s missing:
- Built-in page-level feedback functionality.
Recommended action:
- Remove the Simple Feedback Form widget from Mosaic before Migration.
- If feedback collection is required, consider linking to a short external form (e.g. Microsoft Forms).
Status: Supported
What’s new:
A Slideshow Component replaces the Mosaic Slideshow widget.
Existing slideshows will migrate in some form now the new component is available.
What’s changed:
Fresco has no autoplay or automatic looping functionality. This is a deliberate change to improve accessibility by removing auto-scrolling behaviour.
Fresco slideshows are limited to a minimum of two and a maximum of six slides. During migration, only the first six slides from a Mosaic widget are carried over; any additional slides are lost.
Fresco supports "Static" slides (built directly using Banners) and "Selected Content" slides (referencing existing pages).
It does not support dynamic (filtered) slideshows that update automatically based on taxonomy rules; these must be rebuilt manually in Fresco as either Banner or Selected Content slides
What's currently missing:
Specific properties such as duration between slides, automatic looping, and top/bottom margins are no longer available.
Recommended action:
If a Mosaic slideshow had indicators disabled, the migrated version may incorrectly enable them, so this will require a manual toggle-off.
Slides in Fresco cannot be reordered after they are created, so the sequence must be carefully planned before adding content.
Status: Planned
What’s new:
- A new Symplectic app is in development for Fresco, designed to provide seamless integration with the updated platform.
What’s changed:
- Existing Mosaic Symplectic Publications integrations are expected to migrate smoothly once the new app is available.
What’s missing:
- The Symplectic integration is not yet available in the current Fresco release.
Recommended action:
- If your existing Mosaic site uses Symplectic Publications, the Migration team will likely assign you to a tranche that occurs after the ability to migrate Symplectic Publications becomes available, so there is no action needed.
- If you would be happy to migrate your site prior to Symplectic Publications being able to migrate over, you will need to configure it again once it does become available.
- Monitor migration communications for updates on the rollout schedule and implementation details.
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: