Squiz DXP

User story: As a web editor, I need to change list type attributes to ensure policies display the correct list type (see https://developer.mozilla.org/en-US/docs/Web/HTML/Element/ol#attributes ) Issue/Opportunity: It is not possible to change list type attribute in the Matrix wysiwg editor. Changling list type requires using the source code editor, and the new list types do not render in the wysiwg view. Request: Support all HTML list type attribute values in the wysiwg editor, including choosing which type to use, and rendering this correctly in the wysiwyg editor.

It would be very helpful to have a "code" form field available in the "Advanced form fields" section. It would also be very helpful to be able to reference one or more CSS files for each form, not just a single CSS file for all forms, as is currently the case through the "Global CSS" setting in the "Form Settings" section of the "Organisational Settings" area of Advanced Forms. Both of these features could be restricted to users with "Forms Admin" privileges.

We are facing difficulties as we get more editors copying and pasting content from Word documents which include unclean, excess code. Other CMSes and even Dreamweaver had this fence at the top of the cliff, but Squiz Matrix is forcing us to use an ambulance at the bottom. Surely not best UX. Can we please get this feature added to the WYSIWYG?

Currently all editors can see and change all metadata applied to an asset. This can lead to a lot of metadata fields being visible to editors that aren’t even relevant to them (and in some cases they shouldn't be changing them). It would be great to be able to restrict particular fields, sections, or even entire schemas. In our design system template we have nested content areas that are set up when a site is created - it'd be great if these particular fields were only visible to (or at the very least editable by) system administrators. If we had more fine-tuned permissions control, then some users with write access might be able to see and edit some basic fields, but then users with admin access might see more advanced ones – and depending what user groups they are in they might see none, some, or all.

This was available in Funnelback 15 but doesn't exist in the DXP - we'd like to see a graph to show how crawl times vary over time, as this is very useful for troubleshooting crawl issues and also any underlying performance issues with our content management.

For a multi line text box, can the output include formatting like bold, bullet points, carriage returns because at the moment it comes as one unformatted paragraph.

We would like to have more control over how the image is positioned, for example an X, Y location on the image so we could ensure that the focal point on the image would always be in the correct place, no matter the width of the page. This also has cultural implications, as it breaks tikanga to cover over someones head or cut someones head out of a picture. As you can expect this is especially important on a homepage. We are currently able to position (or pin) the image to the top, center, left bottom, right center etc. and are getting around this by having 3 images, for mobile/tablet/desktop. However, there are times when the focal point of the image is too far left or right even within these.

We have various user roles in DXP at the moment. Having the concept of teams and resources assigned to these teams will allow organizations to have more control and assign more granular access to any resources in the DXP, i.e. sites, search instances etc. This is especially important for organizations with complex structures utilizing multiple capabilities of the DXP, with many people working on numerous projects simultaneously.

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).

The "Find in asset tree" (binoculars) function tells you how many locations the asset is in, but describes them as "parents", so if an asset has one parent which exists in two locations, the binoculars tells you "This asset is linked to 2 parents", which seems like an incorrect use of that term.