Squiz DXP

You used to be able to quickly link assets in Matrix 6 by adding the parent's asset ID via the linking screen. Now you can only use the New Location 'asset finder' tool to select new parents from the asset tree. This is a much slower/tedious process, especially when you have a very large/deep asset tree structure like we do. The ability to select assets is still used elsewhere in the system. Please can you bring it back for the linking screen? Thanks very much

We’d love to see support for language tagging in text fields. Right now, we’re forced to use WYSIWYG fields everywhere there is text because content may be written in either Te Reo Māori or English (or a mixture). This creates several challenges: * We can’t apply character limits or input validation. * Editors can paste in poorly formatted content (e.g. from Word), which breaks layout and styling, or they can create lists, headings etc. mid component. * We lose semantic clarity around which language is being used, which affects accessibility and screen reader support. Adding language tagging would help with: * Accessibility: Screen readers can correctly pronounce Te Reo Māori and English when language is tagged. * Cultural integrity: Ensures Te Reo Māori is treated as a distinct and respected language, not just styled text. * SEO: Improves search engine indexing and relevance for bilingual content. * Translation workflows: Makes it easier to identify and manage multilingual content. * Analytics: Enables tracking of language usage for reporting and planning. * Styling: Allows for language-specific formatting or layout adjustments. This would also allow us to move back to simpler, structured fields where appropriate, improving consistency and reducing formatting issues. Keen to hear if this is on the roadmap or if others are facing similar challenges!

Funnelback seems to only pick up spelling errors in one word of a multi word search term entered. Examples: ‘psycological saftey’ (both words misspelt) does not provide query alternatives, however ‘psycological’ entered on its own and offers expanded search correction. ‘knowlege hub’ when entered is not picked up as having any spelling errors, however when ‘knowledge’ is entered on its own Funnelback offers an expanded search correction. ‘bejavioural interview’ when entered is not picked up as having any spelling errors, however when ‘bejavioural’ is entered on its own Funnelback offers an expanded search correction. Can Funnelback be improved to allowing it pick up spelling errors when more than one word is entered into the search?

I've been building a proof of concept GOV.UK Service website and have used Squiz's prebuilt GOV.UK DXP components. As I have been doing this, I've noticed some differences with the GOV.UK Design System and the ones available as pre-built components. What is Squiz's roadmap for these components? Are there any plans to update or develop more in line with the documented GOV.UK Frontend Design System? What options are there for me to be able to extend or contribute towards the existing DXP component set?

Summary: First raised by University of Newcastle "UoN are on a bit of a mission to improve site performance. One of the things Google recommends is using the latest ‘webp’ format for images. I understand our techs support .webp images which is great. The issue that customer will have though with their dispersed publishing model (over 400 web publishers in the uni) is that they won’t have the tools to save images off in that format. Wondering on the off change whether anything has been considered at around having the ability to convert JPGs (or PNGS) to the Webp format via the CMS upload process?"

Source: https://jira.squiz.net/browse/SUPPORT-423318 Summary: First raised by Queensland Health Content on why this is impacts QH from a business PoV is that when they go to review aged content (typically not updated in 12 months) the first piece of info they need is who edited the page. Now this info would come from the asset log screen, but from this ticket is looks like when the asset is over 12 months old the page = 504 gateway timeout

The Data Search Tool in Matrix is a great way to track down any occurrences of a string of text (even HTML attributes or metadata values), but it forces you to browse the results within the tool. You can't share the results (aside from explaining the search terms/parameters used so it can be repeated, and you'd need to keep the results tab open and have another if you need to go through a lot of them. You can copy the results, but you get things like the buttons and icons for finding in the asset tree, etc. so it's not useful for reference outside of the Matrix UI. Ideally, there would be a function to export to CSV, Excel or PDF (as these are the most useful for editors, compared to developers).

We need a report generator tool to create a list of orphaned assets (including documents like pdf, csv, docx) across the system or to each root node given. By orphaned asset I mean assets that are never referenced across the system. It is equivalent when you go to a given asset's linking screen, then References, and generate a report. If zero reference is back, this can be counted as an orphan asset. This is different from Orphaned asset tool available under Maintenance tab.

As a Funnelback analyst, I want to see complete lists of keywords and clicks, so that I can make content SEO recommendations based on the full picture. Currently only the top 200 items are available in analytics, meaning our reporting obtained via Funnelback is missing common terms and clicks.

We would like to use Google reCAPTCHA v3, as the version you support currently (Google reCAPTCHA v2) can’t meet our public sector accessibility standards.