My thoughts about D8 porting

I think if you can build a "Site builders way" generic enough to use it with other frameworks that will be great. Something that it can easily carry bootstrap or foundation any other framework. A see a really good potential for a project that it take site builders can generate any type of layout.

Thank you for this awesome module. Yes, customization via UI in D8 would be great and appreciated by us non-techies and I'm sure the community as a whole. This would also align and support Dries' vision of Drupal being more user-friendly for the non-technical users. A port to D8 would be appreciated by the community.

+1 for the site builders way.
Personally, I'm quite happy developing custom layouts, but there is a big number of use cases when the UI layout builder is needed

I say yes to the site builders way. Where I work the layouts were custom. I personally just like the bootstrap style options when editing the panel. It gave me the ability to create truly responsive pages at multiple breakpoints by selecting col-widths and offsets. I'm not seeing the "Settings Gear" on the panels region anymore in Drupal 8. So if you could somehow port the ability to adjust the regions styles settings that would be awesome. (Dropdowns or field to input classes)

+1 for porting to D8

I'm also interested in seeing this ported!

@mrded: I know how you feel with this and I have this inner discussion about the "developers way" and the other way all the time with myself, with tendency to the developers way. Like you. And I would like to point you to something I've often wiped away for one thought but it returned suddently for another: theme independent context. The site builders way is not only a lazy way to work around the developers way, it also enables to use certain "looks" outside of single groups of templates and themes in context based situations, where a possible chance is there, that it affects more than one theme (or more than one boostrap subtheme, e.g. edit node). And templates are first of theme based and to have them theme independent, they become module based. If you would like to have theme independent templates, In this case, you require additional modules again to be written and updated all the time by yourself, if you go the "developers way". Especially in the D8 and 9 release cycles, where many things change even between 8.2 and 8.3, this can become a very resource hungry work without the focused help in contrib area.

I had this discussion already on other places and I would like to advocate for a higher D8 adaption rate by showing the user that it won't be an endless story to keep up with Drupal 8 core. We only can achieve that by focusing our efforts on project extensions used by many and contributed to by many. So yes, I think contrib layout modules like this one will be nessesary for the eco system and to prevent reinventing the wheel for every second web project or Bootstrap subtheme build with Drupal.

But maybe I miss something which breaks my logic and my stated arguments from the glimps I used to chime in.

@mrded: sad to hear that you moved slidely away from Drupal. I hope it was not reasoned by the new underlying framework ;) or the new JS hype ;-) If so, I am pretty sure, you will come back to the big grand pa :)) ... until then, let me co-maintain to clean up the issue queue and to push the port forward. I can't promise to keep up with it all the time (after) or to invent any new features, but I always try to help when I see that help is needed and so I helped to get link module ready for D7 and for D8 core port and for other contrib projects when it came to a temporary stop or the issue queue started to overflow. I think this module should keep in movement and I will make some house keeping, patch reviewing, committing, and such awakening parts and some PR for the D8 port in respect of your project goals and we will see if this "kick" will help it.

PS: But thanks for coming back to report. This is not always taken for granted. Greetings from Berlin.

You're welcome.

But please, do not implement every each feature people ask. Keep the code clean and simple, otherwise you will have to maintain and support all those features.

Please re-read:

I can't promise to keep up with it all the time (after) or to invent any new features, but I always try to help when I see that help is needed and [...] I will make some house keeping, patch reviewing, committing, and such awakening parts and some PR for the D8 port in respect of your project goals and we will see if this "kick" will help it.

:) Trust me, as a CEO and project lead of a company supporting Open Source projects now over a decade (including Debian, Drupal and others) there is no guidance regarding this required. ;-) I fully agree on this with you and I am advocate of the concept of modularity and feature overflow prevention since ages. But thanks for your well-intentioned suggestion. ;-) Greetings from Berlin.

NOTE: There is possibly some conversation required:

This project is the combination of the Drupal 7 Display Suite Bootstrap Layouts and Panels Bootstrap Layouts modules for Drupal 8.

https://www.drupal.org/project/bootstrap_layouts

After we have compared code base and clarified if we stay/agree as a seperated version for Panels only, we should consider unique features. Apart from that: Can anyone report if there has been any conversation done with @mrded regarding this newer overlapping module?

First thing which came in my mind immediately at a first glimpse: Why not asking over there to rather provide an "API" with base Bootstrap markup rewrite and common classes etc, and the 2 additional modules for DS and Panels can hook into it. This way we keep it clean and modular and future proof with well used resources. The API should have a switch between using own bootstrap library or library from installed Bootstrap theme. And so on. But this is only a thought to keep in the notes here.

Hi guys,

I developed a module which does exactly what you guys mentioned above.
Take a look and let me know if you are missing any features!

This Drupal 8 "Layout Builder" module can be used to create/manage reusable layouts, which can be used in Display Suite, Panels & the Drupal Core Layout Builder.

https://www.drupal.org/project/dynamic_layouts