Split from #1775302: Do a UX review of Breakpoint module
Related to #1696302: [meta] Blocks/Layouts everywhere
I created this issue so we can clarify how everything works together in the end, assuming all initiatives will make it to core. Apparently most people (including me) have problems understanding how everything will fit together.
This is what I understand from SCOTCH: page.tpl.php is going away and layouts are defined by core (php code, the layout module or something else).
In Drupal 7 the 'layout' is done inside the theme using mostly html and css, and it will be moved to Drupal core, so core is going to output html and css? So parts of theme.info and most tpl.php are going away and themers will need to write php code to be able to define layouts and regions? I would love feedback from themers on this.
from #1775302-27: Do a UX review of Breakpoint module about SCOTCH:
"The express goal of the blocks and layouts initiative is to make everything a little building block on the page (vs. custom things that there were before), with those building blocks much more flexibly configurable in themselves (eg. Kris is working on blocks instances so you can place the same block multiple times on the page with different configuration)."
Blocks need some love and I'm all in favor of doing this, but my main concern is the move from theme to core. As I understood is this was going to make blocks smarter (context, easier to create/duplicate, easier to extend, reuse) but apparently this also means that the whole rendering is changed. For the moment I don't see the need to change the theme part of the story.
"Building in a GUI to be able to put these pieces into a layout is a logical next step vs. just keep shipping core with hard-coded PHP developed layouts that are only modifiable to people who know PHP and CSS. That does not mean people who do want to have super-precise control should not be able to ignore any layout builder and do their own stuff hardcoding the layouts using the building blocks but stitching them together in code instead of a GUI. For those people, it should be easy to ignore whatever GUI we have for breakpoints, grids or layouts, they are just not part of the audience for this tool."
So themer need to learn how to build a new plugin in PHP to be able to add a region to their theme, and need to find a way to distribute it as well? Now (D7) the theme defines the regions and the layout so it's easy to distribute, but by changing this it means the theme isn't no longer responsible about the layout, but only about styling?
from #1775302-27: Do a UX review of Breakpoint module about the UI:
"Whether Drupal needs a GUI for this was proven by Panels (on 126000+ sites) and Context (on 69000+ sites) in contrib very well. Of course not everybody uses those, and whatever layout tool comes out , if it is included with core, it will not be mandatory either."
So 17% of the installs use panels, 83% doesn't.
- If I offended somebody in any way I apologize right away, I just want to clarify things.
- I'll try to add some more information later today to clarify