Is there a future for Page Manager?

i want to use layout_builder for building page layouts.
But layout_builder has no smart way to determine context.
There are modules like http://drupal.org/project/context_stack and this issue 💬 Can context_stack be used with layout_builder to provide context for different layouts? Closed: outdated

Page manager has been a wonderful idea and especially in combination with layouts, it's really a very helpful tool for Drupal. Would be totally sad, if it was discontinued!

i agree @anybody, and would like to see it continue on

I am also very interested. the problem I have with Layout Builder is that it is not stored as configuration and pages you make have arbitrary real paths. you can set an alias path but drupal will pick up the real node path which is very problematic in transferring configuration from development environment to production.

I like the context awareness of page_manager and I hope it continues.
I would like to add add context to page_manager to recognize the switching of view modes.
It would be create to switch view modes based on criteria like date. I can show an event has passed view mode for a node which might have a link to the next upcoming event.

as far as I know Layout Builder also does not work with the Bootrap 3 Drupal module. While I'd like to move to 5, I don't really have the bandwidth.

Would love some feedback as to what to expect from Page Manager in the future. Will it continue, even in its current state?

We're currently migrating a massive site from D7->D10, and Page Manager played a critical role in the old site, it doesn't appear there are any alternatives for D10 (aside from the Page Manager module itself).

Also, we are currently sponsoring a variety of contrib work on modules we use, and would be happy to include Page Manager in that, if it is indeed planned to continue.

@jweirather I am not a maintainer here, but if you all could get involved in maintainership for this module, that would be amazing.

You may be able to get help/feedback from @gisle. He outlined the process to me here 📌 New co-maintainer Closed: duplicate

This → is another issue that might be relevant to you in that quest.

Keep up posted here!

I pinged @japerry and @joelpittet on Slack with the following message:

I am willing to (feel free to add me) temporary to co-maintain this project at least to bring the most import steps to be done and RTBCs to review an to be merged to move forward with a stable release. With the help of some other long term Drupal contributors and maintainers in that issue who are willing to help to solve the biggest issues to get it future ready I would be able to make it Drupal 10/11 ready. Because my time as founder and CEO of 3 companies is limited, I consider these co-operation with others as mandatory and additionally I will let employees of my companies work on it in their company time to support Drupal and the awesome Page Manager.

I fully understand and know by myself from the projects I maintain that one life is not enough to be everywhere everytime with the same intension and I hope I can help to jump in here to help. The reason: I agree with some comments made in this isse, that parts of the main feature set of page_manager are very relevant for the overall flexibility and future of Drupal and are not overlapping enough with other projects and some RTBCs are very important to make it working without flaws in D10 and D11.

Thanks for all the hard work on this project and a Happy belated global Drupal contribution day!

THANKS @dqd!

It would be amazing if your team and other dedicated users could pick this up. Please keep us posted here and let us know how we can help.

If slack proves a dead end, consider contacting @gisle. He outlined the process to me here:

https://www.drupal.org/project/acl/issues/3348765 📌 New co-maintainer Closed: duplicate

Primary issue here is very high expectations for 4.0 release

I bet the good idea is to triage issues and write-up roadmap a-la 🌱 Plan for Page Manager 8.x-4.0 release Active

+1 for @dqd he did a great jobs in many other contrib modules. Especially I know from https://www.drupal.org/project/datatables → !

Primary issue here is very high expectations for 4.0 release

Agreed. And we would do us all a favour in planning smarter and more realistic. Before not getting anything done for years it would be good to get something stable at very first.

I bet the good idea is to triage issues and write-up roadmap

Yes. Exactly. That's what I usually do when chiming in to support a projects survival. :) But sometimes an "emergency sub release" of long standing RTBCs, and flushing the issue queue from dust etc is required urgently. Especially when a roadmap is about 7 years old, hah. Just kidding.

+1 for @dqd he did a great jobs in many other contrib modules.

Thanks @Anybody :) very much appreciated compliment. And do not "hide your own light under a bushel". It is always the sum of the hard work of all together and so is your support! +1