Squiz DXP

Source: https://squizmap.squiz.net/matrix/12589 Votes: 19 Thoughts: Looks like a high value enhancement as there's good demand for it -- Summary: A feature that would greatly help with extending the metadata functionality and making it even more powerful would be repeatable metadata sections. The idea being that a schema would have a section that is defined as repeatable, and the schema would be copied any number of times and filled with relevant data.

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

It would be very useful to be able to define a first class content type in the CMS. Currently in Matrix we do this with a standard page, a metadata schema, a paint layout and maybe a custom design. These aspects all need to be managed separately meaning lots of room for error. There's also no good simple end point for headless CMS capabilities. If we had a concept of first class 'content types' in the CMS, that allowed content modelling, default templates, and a built in way to use it via API, it would be very useful to better model the kinds of structured content Squiz customers need to manage.

Short version: A set of configuration values for cache management should be a first class citizen, which can be applied to assets in the same way paint layouts or designs can. Long version: There are multiple levels of caching happening in any Matrix install, some of them configurable, some not. Eg. > OS filesystem cache (not configurable within Matrix) > Dejavu (on/off toggle only, not configurable within Matrix) > Matrix cache (configurable) > Proxy/Accelerator cache (configurable) > Browser cache (configurable) The current cache configuration UX quickly become impenetrable when configuring a site even with modest complexity. This situation is only going to get worse when we're using Trinity more. By reworking cache configuration as a first class citizen (ie, an Asset), we can reduce the complexity of the UX markedly and help both us and our customers achieve their desired outcome. The idea is to create a cache settings screen (probably not an entire screen, perhaps just belongs on the existing settings screen for an asset) that allows applying a cache configuration to an asset, optionally cascading the configuration. Further detail here: - https://squizmap.squiz.net/matrix/12194

Currently the WYSIWYG editor doesn't style elements the same as the published site (e.g headings, body copy fonts etc). Also our editors have requested small tweaks to aid content creation, such as underlining text with lang attributes, correcting list type styling to match html etc. Current workaround is via a user specific CSS file/browser add-on. However having a WYSIWYG specific CSS file in the repo or something similar would be more useful.

It would be nice if we have an easy way to include an advanced table onto page which allows for things like: * Sorting - Clicking on the headings will sort the entries based on that criteria. * Easily specify the columns and headings. * Choose where the data comes from (both manual or from some API). * Choose the number of rows to display. * Paginate data if the table gets too big. * Controls to go to first page, last page and show the number of results in total. * Choose from a set of predefined themes.

PDFs are currently indexed with their name eg. special-consideration-form.pdf. Suggest indexing these results with spaces rather than hyphens, so when "special consideration form" is searched, the correct result will be returned. Current workaround is to use external metadata and manually write the user friendly name in the metadata (or edit the PDF metadata directly)

Windcave is extremely popular here in NZ, and we note there is a Windcave provider in Matrix currently. I don't believe this would be too difficult to add, and would be really useful for us over in NZ! Obviously Advanced Forms is pretty hot off the press so this may be on your radar already, but I figured I'd chuck it in here too.

Bulk management functions of curator rules such as: * delete * import * export to file (for mass updates)