Ask Questions and Find Answers

Hey Christoph,As always I appreciate your feedback. Please find my answers point by point below:>  I did create a new content page and then noticed that it isn't shown in the navigation menu. That bugged me quite a bit. I even looked into the code to understand what's going on. Unpublished pages are simply hidden from the navigation menu.
> 1) While I am unsure if the navigation menu behavior is sound, the main issue is the status of the content page. What is the state? Is it published? Is there a draft? Therefore I propose to add a clear status indicator to content pages.
https://issues.liferay.com/browse/LPS-103125Thanks, I've replied to it

> 2) Creating that issue was quite a pain. Boy, issues.liferay.com is slow. Actually I didn't create an issue at the very moment I am writing this line, I have only managed to click the "Create" button so far. 
Yeah, we are aware of it. We should make sending suggestions much easier.

> 3) Widget templates: I tried to change a navigation template to check if some flag (browsable, hidden, ...) hides the navitem and noticed that the standard templates are "gone". Not really a big deal for me, I went to github and copied an ftl from there. But new users are certainly lost here.
I need to research this one.

> 4) Manage Templates does not work correctly.  See screenshot Navigation_Config and Manage Templates. The list is simply empty. But after clicking "+" and adding a template (in this case test2), they are shown. https://issues.liferay.com/browse/LPS-103126
Thanks for reporting it, the team is working on it already.

> 5) Improve the page finder dropdown: I hate the UX here. Why can't I just click there and start typing? Why do I have to open the dropdown and then click into some input field? Why is there even a dropdown? (Future use?) Please rethink that thing.
We are on it. See https://issues.liferay.com/browse/LPS-102544 for a description of the new solution. There is also a link to a mockup in the first comment.

> 6)  Actually: The page finder is just a tiny part of it. By itself it is well, not great, but okish. But the whole experience of adding and managing pages is NOT fun. Adding 5 children to a page is like Urks. I have to switch to the page administration, find the current page there. When I add a page there, it is instantly opened. I must again to switch to the page administration, find the parent page, add the next page, ...
Agreed. See https://issues.liferay.com/browse/LPS-103104
> Well, let me stop here. I think, I have made it clear in various posts how much I dislike the current navigation management "concept". No need to talk about it again, I am sure you have already thought about it as well.
Please, keep the feedback coming. We listen and value it. It may take us some time to find a solution, since we have to juggle different needs from different use cases and also competing priorities. Regarding your feedback in this post, I think we are very close to solving all items

Hi Christoph,Widget templates are still available on the Global site. Maybe it makes sense to inherit them as we do with the Fragment Collections now.Thanks!

Concur with the templates issue. In 7.0 I could edit the default breadcrumb ADT, no I don't see any "Widget Templates" in the Global Site. I had to duplicate the breadcrumb template to edit it and ignore that Liferay even had one.

The Felling Of The Tree  ... Sorry but this was the biggest mistake I've ever seen in technology. "It's worth noting that this was possible in Liferay 7.0, when the pages administration was embedded within the left product menu. Feedback from users shows that this capability was useful and is now missed."
 
I understand the slow loading issue, but since the management part of that has been sent off to the miller columns, the tree no longer needs to have menus and drag and drop or management features. All that's needed is a series of hyperlinks. What's holding us back from having a "Navigation" menu item that drops down a tree structure that is lazy loaded as the user scrolls? I really understand the performance issue but I don't understand why a JSON file of the page structure (a site map) can't be lazy loaded?

Technology out there suggests that assumption that a web browser cannot load a lot of content is not correct. It was correct in 1997, but with modern javascript lazy loading and infinite scrolling are things that exist and can be coded. Our users are about to be stuck with this decision and if we go with 7.2 we won't be upgrading to 7.3 for a very long time. So you can say yeah it's there in 7.3 but to us 7.3 doesn't and won't exist (unless we wait another year).

I can't see where users are being invited to try the new navigation menu in the product menu in a focused way that can give you feedback? It seems to be "hold on we're working on it" we get it back and it's like, no really that's not what the issue was. There's still a disconnect and we need that menu back ASAP. When did it get removed 2018? When do we get it back 2020?

Global fragments. I can't realistically do any of my own fragments until there's a way to have fragments listed in the Global site.
Because the miller columns are so important ... In 7.2 Fixpack 2 I can't drag child pages "back up a level". It feels like the children are stuck where they are dropped. Also multiple children still cannot be moved at the same time and when I try the active states get all messed up and pages I haven't even selected turn blue.