[meta] Blocks/Layouts everywhere

updating some of the text as appropriate

Sun,

It may be not the right place to ask this, but the 3. point:

"Introduce data sources to core in general, and block plugins specifically.
E.g., to render a particular field within a particular context as a block."

is on my interest list, can you give more information about this ? I would like to help on the "introduce data sources" concept.

@Sylvain

I think fago has largely covered this already with his property work. I am currently evaluating that for inclusion in this space, so the work required here may already largely be done. If I find that things are otherwise, I'll trying to come back to this issue and update it with regard to that, but for the time being, I think we can consider that issue largely covered barring a bad review by myself (which I've already done a 1 on 1 with fago on the topic already and am pretty sure it will meet our needs).

Thanks for the thought though.

Eclipse

@Sylvain: #1696640: Implement API to unify entity properties and fields can benefit greatly from more reviews, so if you can look that over and leave your thoughts, that would be awesome. Doing so will both help accelerate that patch getting in, and also put you in a great position to help with follow-up work integrating it with Blocks.

Updated issue summary.

Linking back to #1775302-20: Do a UX review of Breakpoint module since it's related to part 5 of the roadmap and confusing a lot of people.

I created #1784456: [Meta] Implication of Layout & blocks everywhere to discuss to implications of 5, because there are a lot of people having problems to understand the implications (me included)

Sandbox removed

Issues for converting things to blocks:

• Site elements: #1053648: Convert site elements (site name, slogan, site logo) into blocks
• Page elements: #507488: Convert page elements (local tasks, actions) into blocks
• Global menus: #1869476: Convert global menus (primary links, secondary links) into blocks

All have patches from @EclipseGC.

By the same reasoning as #1818142-2: [meta] Unified Blocks and Layouts (SCOTCH+WSCCI+Spark+Field UI), demoting to major. The conversions in #7 are still very important as part of #1830854: [meta] The ESI pipeline battle plan.

Added block conversion issues.

8.1 at least I think.

Just a note that step four is now complete. All page variables have now been converted to blocks.

#10: WOOOOOT!

Should we create a new issue for step five for 8.1.x?

I really don't think we're ready for that yet. Contrib is moving forward on this and I think we should let a solid solution evolve there before we embark upon pulling it into core. There's already an issue for 5.1 #2296423: Implement layout plugin type in core

The rest we should probably let evolve for the next few months.

Eclipse

Should this be closed as a duplicate of #2811175: [plan] Add layouts to Drupal?
For now, untagging it.

I bet that's better status