[Layout Initiative meeting] 2019/4/23 [#3050021]

Moderated By: timplunkett (he/him)

Hello everyone ! Welcome to our weekly Layout Initiative meeting.

This meeting:
➤ happens right here every Tuesday, 1pm ET / 10am PT / 17:00 UTC
➤ is chat only (no audio or video)
➤ happens in threads so keep an eye on those notifications
➤ the agenda is public and anyone can add to it: #3050021: [Layout Initiative meeting] 2019/4/23

0️⃣ Introduce yourself if you are attending!

timplunkett (he/him)	Hi, Tim from Philadelphia!
akalata	Anna in Chicago, hoping to get more involved!
alphex	Hi, Duran from Atlanta, and is lurking
Jeff	Hello, Jeff from Knoxville.
starshaped (she/her)	Aubrey from Boston, lurking essentially
tedbow	Hi, Ted from Ithaca, NY, USA, Earth
bnjmnm	Ben in Ann Arbor
shaal	Ofer, Boca Raton, Florida
eaton	Hi, Jeff from Chicago. Lurking because php are hard
ashrafabed	:wave::skin-tone-3: Ashraf from VA
timbozeman	Hi, Tim from San Diego
akalata	@eaton did you move to Chicago? Or are you just saying that because nobody knows where Aurora is? :smile:
douggreen	Also lurking, hi @akalata. If you’re looking at layout builder, we should talk afterwards. I’ve done some work.
azslay	Ashley from Tucson. Mostly lurking since I attended my first Drupalcon in Seattle and heard about this channel there. Curious to see what it's all about
phenaproxima (he/him)	Adam from Boston
eclipsegc	Kris from OK, still plugging away!
tedbow	plugging I get it
jidrone	Ivan from BA, Argentina
dsquaredb	Danita from Virginia
eaton	@akalata In the Drupal community, “I live in Geneva” actually causes more confusion, it turns out :smile:
damienmckenna	Damien from Bangor, ME.
pekens	Pekens from philadelphia
Aaron McHale	Oh damn, did I miss it
timplunkett (he/him)	@Aaron McHale no worries, we're back to weekly now
Aaron McHale	Ah good :slightly_smiling_face:

1️⃣ Layout Builder is stable for 8.7!

timplunkett (he/him)	We're in the Release Candidate phase right now. There are still some types of issues that can go in, but it is very limited.
timplunkett (he/him)	Focus now is on 8.8 and backporting bug fixes for 8.7.1+
phenaproxima (he/him)	Did #2955065 make it into RC?
timplunkett (he/him)	I'm not sure that it made it in pre-RC, but it's going to be in 8.7.0 for sure
phenaproxima (he/him)	Well, I know it’s not pre-RC, but is it actually in RC1? I ask because this determines if I need to roll a new release of some Lightning crap. :slightly_smiling_face:
phenaproxima (he/him)	/ me does a bit of git digging
timplunkett (he/him)	it is not in RC1
phenaproxima (he/him)	Oh, okay. Thanks for the clarification!

2️⃣ We're working on a roadmap for 8.8

tedbow	Plan issue for Translations #3044386: [META] Make Layout Builder layouts translatable
damienmckenna	The trick there will be to make it clear from the UI what option(s) are available, and avoiding confusion.
tedbow	yep.
timplunkett (he/him)	8.8 is our last real chance to land big things until 9.1
alphex	maybe this is already fixed… but is there a way (a plan to have a way?) for limiting what is able to be chosen to place, in the layout builder? to avoid an endless glut of options that overwhelm a content manager?
timplunkett (he/him)	http://www.drupal.org/project/layout_builder_restrictions
alphex	thanks!
timplunkett (he/him)	But that's on the agenda to discuss :slightly_smiling_face:
tedbow	@alphex but this issue would help #2977587: Improve block listing in Layout Builder by hiding uncommon block plugins
damienmckenna	Is there a meta issue for 8.8 improvements for layouts?
tedbow	I think that would just be everything in the queue
tedbow	with “Feature Request” or “Task”
tedbow	whoops or “Plan”
damienmckenna	So basically one would be useful? :slightly_smiling_face:
timplunkett (he/him)	we can have one, but the only issue on the roadmap is synced translations :slightly_smiling_face:
timplunkett (he/him)	and i usually prefer to use tags than parent issues. so if it came to it, an `8.8 target` tag or something... but I won't be mad if you want to create a plan issue :slightly_smiling_face:

3️⃣ Work has begun on a migration path from Panelizer to Layout Builder!

phenaproxima (he/him)	I’m writing a basic version of it, in order to support Lightning’s needs.
timplunkett (he/him)	There are several features in Panelizer that are not supported by Layout Builder itself, but in conjunction with contrib it should be possible for a 1:1 migration
phenaproxima (he/him)	The first blocker is support for arbitrary contexts, which is something that Panels can do but LB can’t. Yet. I’m working on https://www.drupal.org/project/core_context, which will provide at least an API for this.
damienmckenna	Tim: are you talking about Layout Library?
timplunkett (he/him)	Layout Library is one, Core Context is another
damienmckenna	Gotcha.
phenaproxima (he/him)	Layout Library is already used by Lightning and it works pretty well
phenaproxima (he/him)	Just need to get Core Context to the point where it can actually do things. I’m going to not bother doing a UI for now, since all we need for a 1:1 migration, technically, is a storage/data layer and API.
timplunkett (he/him)	There's also the whole concept of Relationships
phenaproxima (he/him)	I’m unfamiliar with that — can you tell me a bit more?
timplunkett (he/him)	essentially it's just traversing Entity References
phenaproxima (he/him)	This is something Panels already does?
timplunkett (he/him)	well maybe it doesn't, actually. that might not have made it in the port from D7...
timplunkett (he/him)	which would be nice :slightly_smiling_face:
phenaproxima (he/him)	Yeah, it sounds very unfamiliar to me. Not that I know Panelizer’s plumbing as well as @damienmckenna
damienmckenna	I don't know Panelizer's plumbing that well, because a lot of it comes from CTools and Panels, which I don't understand a lot of.
alphex	you’re the magic glue that makes it all work.
phenaproxima (he/him)	Well, ctools is. :slightly_smiling_face:
phenaproxima (he/him)	And yeah…it’s a jungle in there
damienmckenna	And it's not a happy jungle with happy butterflies, it's an angry jungle with a Terrasque.
phenaproxima (he/him)	It’s the one Indiana Jones almost gets killed by at the beginning of Raiders
phenaproxima (he/him)	Complete with a Giant Rolling Stone Ball of Death
phenaproxima (he/him)	So basically…if relationships are a thing I need to worry about, someone please enlighten me about them :slightly_smiling_face:
damienmckenna	And the giant boulder is an update that adds fourteen new interconnected APIs..
damienmckenna	Am very excited about this work! Just to be clear, this will be to migrate from Panelizer 8.x, right?
phenaproxima (he/him)	Yes.

4️⃣ There are many contrib modules popping up to enhance/alter/extend Layout Builder

timplunkett (he/him)	Some of them are listed here: https://www.drupal.org/docs/8/core/modules/layout-builder/additional-mod...
timplunkett (he/him)	"Layout Builder Restrictions" is the answer to the most common question I'm asked :slightly_smiling_face:
timplunkett (he/him)	We might want to find a way to promote these modules more
douggreen	https://www.drupal.org/project/paragraph_blocks
damienmckenna	Doug: that's just awesome! I love entity type reuse.
timplunkett (he/him)	@douggreen I was just pulling up that link! Please feel free to add it to that handbook page
Jeff	this is a potential contrib. #3029830: Provide single field values from multivalue fields as layout builder-friendly blocks ?
timplunkett (he/him)	@Jeff that's sort of what Paragraph Blocks does, but as a specialized implementation. A generic solution has some tricky UX implications
Jeff	gotcha.
ashrafabed	@timplunkett (he/him) I was just thinking that (skimming the paragraphs blocks video)
ashrafabed	I think/hope that the current proposed solution in that issue Jeff linked addresses the UX implications
ashrafabed	I want to try putting a patch together for that issue but haven't been able to find the time

5️⃣ There are many opportunities to contribute to the Layout Initiative

timplunkett (he/him)	Manual testing of patches, improvements or additions to documentation, fixing bugs in CSS/JS/PHP, accessibility fixes and improvements, triaging/grooming of the issue queue
starshaped (she/her)	I’m definitely here for any CSS/JS or accessibility fixes.
timplunkett (he/him)	This link is slightly out of date (I curated it for the contribution day at DrupalCon Seattle), but it is a dynamic list of issues that are actionable: https://contribkanban.com/board/LayoutBuilder
timplunkett (he/him)	The #1 thing anyone can do is to _use the module_!
timplunkett (he/him)	There are many known issues with it, but there could be many important bugs that we have not yet found.
timplunkett (he/him)	Also, case studies and blog posts about using Layout Builder are really important