I fooled I bit around with GA 5 and have some thoughts on it. I know, a few things were already there in GA4, but I only took checked them out these days.
Bad bugs
The first thing I did was to check if these two issues were resolved:
https://issues.liferay.com/browse/LPS-118241
https://issues.liferay.com/browse/LPS-118242
These are really showstoppers and should be addressed before DXP is released. When you add an editable to an existing fragment and propagate it, the editor breaks. Always. And badly. If this isn't fixed, fragments can simply not be used since you can never extend them without breaking all existing pages.
General fragment behavior
It feels again better. I can't quantify it, but it feels smoother (maybe it's the fragment configuraton change, maybe there are general improvements).
Fragment Configuration
A good change. The cog for configuration was a bit clumsy and this is simply better.
What I would love to see is my own customized edit option, to add my own fields there. It would allow me to e.g. add a "people fragment" and the editor could select a user in the configuration or when double clicking. I would obviously have to implement the select button and the dialog that returns the field value, but it would be tremendously helpful.
I have already created a feature request, that tries to solve the same usecase, but in a different way
https://issues.liferay.com/browse/LPS-115570
Page Structure Tree
A minor thing about the page tree:
I believe, it would be helpful to add more information to the tree. It isn't obvious what is what, what is a container, what is a field, what can be removed, what can be mapped, what is already mapped. It could also be interesting to show, which fields are already translated. Currently you know that e.g. 17 of 18 are translated, but it isn't immediately obivous which one might be missing.
Collection display
Very, very nice and useful.
An option to have an "Add item" button inline would be nice. Otherwise the usability is only nice with collection pages. Another option would be to implement an "Add Webcontent" fragment (a button or something) that allows me to configure, which types can be added. Then I could place that button where ever I want (Assuming that there are two editor roles, one power editor who adds the button, one lesser editor who just adds content)
Collection pages
I am not sure about collection pages and they are a bit buggy.
a) I had a hard time finding the + button, had I not known there is one. My expectation was that it would be on the right side, not on the left, since all other actions are on the right. (Obviously a minor issue and a matter of opinion, but I still had to search for it)
b) I can delete the collection display. Since this is a collection page, why can I delete the collection on the page? Of course, I could add a new collection and configure it to use the same list. But this is still somewhat weird.
c) Worse: Deleting the collection breaks the page --> Obviously a bug ...
I would like this better if there was no special page type and adding a collection display would simply make the add button available. (It could simply register it using Javascript in the top menu. I did something like that for a customer a while ago, the applications on the page simply called "setMenuItems(json)" and added items to the top menu.)
I think, such an approach would be more resilient too. If the collection display is deleted, the add button vanishes. If the collection is deleted, the collection display becomes empty. No big deal, the page is not affected.
Showing global categories
Very nice. Some of my clients always forget where those pesky categories are because they always forget about global. This is better in general with the new main menu,but this helps too. It would be useful to have some link or something there that allows the user to switch to the global site to add/edit categories.
The help link currently doesn't work and ends in a 404:
https://learn.liferay.com/dxp/7.x/en/content-authoring-and-management/tags_and_categories/user-guide/defining-categories-and-vocabularies-for-content.htmlRedirection
A useful module, two things though:
Inserting spaces in the url and saving adds http:// to the url and breaks it
https://www.test.com/xxx xxx --- is changed to --> http://https://www.test.com/xxx xxx
And invalid urls like:
http://https//www.%20test.com/xxx%20saasas/
https//www . test . c om/
https://www.test.com:1234:123/
are accepted without complaint.
Also, relative urls would be nice. Why can't I redirect from /aa to /bb? Why do I have to enter the hostname?Btw.: While 301 redirects are certainly necessary, most people don't understand the consequences. So, a little bit of warning, maybe in that info box, that 301 should be used with caution (since they are permanent), could be helpful.
Image Fragment Entry Processors
I have implemented my own entry processors now and it was a bit of a headache since they are not too well documented, there is just one blog post from Pavel about it. I mostly used the code in github to guide me.
Why did I need this?
a) I want to know in fragment/freemarker if I am in EDIT or VIEW mode. The current method in the standard fragments, checking a style class on body, is really ghastly and only works in Javascript.
The feature request about the mode is here:
https://issues.liferay.com/browse/LPS-115828
b) I need the image id in freemarker. I need to resize it to deliver an optimized image (I know, the feature is in the works, but since the work hasn't started and the issue isn't that trivial in the fully generic case, I believe it will take a while) and add some metadata like copyright information to the page.
I have posted a few thoughts about that a while ago:
https://liferay.dev/forums/-/message_boards/message/119645413
Well, in general, it is nice to see things improve.
