WEBVTT 53 00:12:27.540 --> 00:12:36.680 Aaron McHale: welcome. This is the drupal usability meeting for the fifteenth of March 2024. I am Aaron Mikkel, moderating today. 54 00:12:36.750 --> 00:12:50.719 Aaron McHale: Joining us. We have Quinn Pam, Ralph Koler, Simon Hailsten and Scott. And yeah, Ralph's gonna kick off the discussion with the issue. He's sharing on the screen now. So over to Ralph. 55 00:12:55.650 --> 00:13:21.060 Ralf Koller: unmuted. Okay, issue number is 30433330, reduce the number of field blocks created for entities, entities, possibly to 0. That issue got already committed. But in one of the last comments before it got committed. Quite one already 56 00:13:21.410 --> 00:13:27.350 Ralf Koller: commented. And noted that she has 57 00:13:27.520 --> 00:13:45.830 Ralf Koller: certain problems, understanding basically, the interface changes and input and the label and the description based on the label in the description here issues understanding what actually is meant. And she already recommended asking the Ux folks. 58 00:13:46.410 --> 00:13:50.490 Ralf Koller: And I've agreed, and I've 59 00:13:50.650 --> 00:13:59.280 Ralf Koller: spent a bit of time trying to understand the actual functionality underneath. For comprehension. The 60 00:13:59.960 --> 00:14:06.500 Ralf Koller: change lock. I also paste the link in the chat helps. But 61 00:14:06.780 --> 00:14:11.630 Ralf Koller: I ask for clarification over in the book Content Channel yesterday. 62 00:14:12.430 --> 00:14:16.939 Ralf Koller: basically to outline the functionality that 63 00:14:18.350 --> 00:14:21.559 Ralf Koller: I'll open a new window 64 00:14:24.470 --> 00:14:27.060 Ralf Koller: that doesn't help much. 65 00:14:29.380 --> 00:14:33.959 Ralf Koller: to illustrate the functionality is basically the following. 66 00:14:34.980 --> 00:14:46.970 Ralf Koller: I've extended basically added a few more fields to the article content type as well as the basic page. And in addition to that, 67 00:14:47.230 --> 00:15:00.759 Ralf Koller: I've activated layout builder for article content type as well as the basic page. as you can see. 68 00:15:02.230 --> 00:15:14.870 Ralf Koller: if you go now to and on the account settings at the moment layout builder is deactivated. and if you go to close this again. 69 00:15:16.670 --> 00:15:21.450 Ralf Koller: a layout for the article content type and add a block. 70 00:15:23.160 --> 00:15:31.889 Ralf Koller: Then, you see, basically, the content fields are based oops. I have to take a look. 71 00:15:33.270 --> 00:15:35.779 Ralf Koller: cause I wanted to start 72 00:15:36.360 --> 00:15:39.109 Ralf Koller: a Barbara said. 73 00:15:40.430 --> 00:15:42.180 Ralf Koller: Basically, the the 74 00:15:42.310 --> 00:15:48.799 Ralf Koller: setting is added to content authoring layout builder. That one I forgot to 75 00:15:49.550 --> 00:16:00.059 Ralf Koller: at at the moment. It's disabled. That means, when disabled, only any deep type bundles that have layout builder enabled will have their fields exposed. 76 00:16:00.640 --> 00:16:02.560 Ralf Koller: and that means 77 00:16:04.140 --> 00:16:09.299 Ralf Koller: in content fields. All the fields available on the article content type 78 00:16:10.950 --> 00:16:12.040 Ralf Koller: are shown 79 00:16:12.380 --> 00:16:16.850 Ralf Koller: and exposed, and if you go scroll down, you see. 80 00:16:16.960 --> 00:16:23.480 Ralf Koller: users is not available. If we go now here and activate 81 00:16:25.740 --> 00:16:26.410 Ralf Koller: well 82 00:16:35.650 --> 00:16:37.900 Ralf Koller: again. Reload. 83 00:16:46.280 --> 00:16:48.010 Ralf Koller: as you can see now. 84 00:16:49.320 --> 00:16:51.059 Ralf Koller: more fields are exposed. 85 00:16:52.340 --> 00:16:57.429 Ralf Koller: I deactivate. Now. 86 00:16:57.480 --> 00:16:59.060 Ralf Koller: layout builder again 87 00:17:01.270 --> 00:17:02.440 Ralf Koller: for accounts. 88 00:17:02.870 --> 00:17:05.089 Ralf Koller: move over and 89 00:17:05.460 --> 00:17:10.329 Ralf Koller: activate the functionality meaning 90 00:17:10.700 --> 00:17:15.790 Ralf Koller: when enabled. The setting exposes all fields for all entity view displays. 91 00:17:16.109 --> 00:17:19.240 Ralf Koller: save that's basically 92 00:17:19.730 --> 00:17:22.670 Ralf Koller: The state 93 00:17:23.560 --> 00:17:29.820 Ralf Koller: before that commit got in. That was the behavior before. And if we go null 94 00:17:31.370 --> 00:17:34.599 Ralf Koller: it's deactivated. Reload. 95 00:17:37.610 --> 00:17:40.419 Ralf Koller: scroll down, and, as you can see, still 96 00:17:40.490 --> 00:17:42.420 Ralf Koller: all user fields. 97 00:17:43.470 --> 00:17:48.500 Ralf Koller: all fields of on the account entity 98 00:17:49.110 --> 00:17:49.960 Ralf Koller: are 99 00:17:50.350 --> 00:18:00.870 Ralf Koller: exposed and shown, but as you can, as if node and what has to be noted if you added a layout, for example, for the article Content type. 100 00:18:01.100 --> 00:18:10.680 Ralf Koller: No matter if that feature is activated or not. the basic page fields are never shown. 101 00:18:10.750 --> 00:18:12.910 Ralf Koller: but it has to be noted. 102 00:18:13.040 --> 00:18:22.430 Ralf Koller: case. The feature is activated. They are not shown, but still they're still basically 103 00:18:24.130 --> 00:18:31.600 Ralf Koller: how Adam remotely phrased it. I have to switch 104 00:18:33.390 --> 00:18:48.379 Ralf Koller: with the settings enable those field block block plugins for those other bundles will still exist. So they are still created, but just not shown. And that is basically the underlying behavior. And 105 00:18:49.410 --> 00:18:53.510 Ralf Koller: the problem is comprehension-wise. 106 00:18:54.580 --> 00:19:01.079 Ralf Koller: To wrap your head around just based on that description available on here is 107 00:19:01.320 --> 00:19:03.920 Ralf Koller: a bit challenging. Let's put it that way. 108 00:19:05.040 --> 00:19:06.070 Aaron McHale: So 109 00:19:07.310 --> 00:19:14.880 Aaron McHale: we go any further just to ask in fact, I'll just say that Thomas joined us. So welcome, Thomas, 110 00:19:15.220 --> 00:19:16.910 Aaron McHale: and Thomas Howell. 111 00:19:17.080 --> 00:19:31.289 Aaron McHale: And yeah, is there is everybody clear on what is going on here? certainly. It was a little. Took me a minute to wrap my head around it. Does anybody have any questions about this behavior, or what what's happening here? 112 00:19:33.350 --> 00:19:45.709 Simo Hellsten: One question so does expose means they are not accessible for the for the layout, meaning that if that somebody unchecks those boxes 113 00:19:46.180 --> 00:19:48.250 Simo Hellsten: previously added 114 00:19:48.500 --> 00:19:54.150 Simo Hellsten: blocks would disappear, or is it that they are not shown in the user interface. 115 00:19:55.790 --> 00:20:01.010 Ralf Koller: they are 116 00:20:04.000 --> 00:20:06.510 Ralf Koller: depending on what 117 00:20:10.390 --> 00:20:14.970 Ralf Koller: do you mean the fields for? For a layout. 118 00:20:17.150 --> 00:20:21.990 Ralf Koller: So let's let's take the example of the article content type. 119 00:20:22.230 --> 00:20:35.009 Ralf Koller: we have basically body, a Boolean field, a comment field image field, a phone field and a text field. 120 00:20:36.050 --> 00:20:43.310 Ralf Koller: And currently, everything is exposed. That's on always disable it. 121 00:20:44.240 --> 00:20:50.180 Ralf Koller: Your question was, basically, if something is removed there or 122 00:20:51.110 --> 00:20:53.130 Simo Hellsten: if 123 00:20:54.200 --> 00:21:00.480 Simo Hellsten: if fields are exposed to the layered bitter, bitter, and they are used there. 124 00:21:00.880 --> 00:21:11.040 Simo Hellsten: and if one. So if then afterwards, if you revoke that and like, revoke that, exposure them 125 00:21:11.370 --> 00:21:16.159 Simo Hellsten: so uncheck the box, and save with that they disappear from layout. 126 00:21:16.390 --> 00:21:19.650 Simo Hellsten: or will they be kind of there, but not shown? 127 00:21:20.300 --> 00:21:24.859 Ralf Koller: In that in that particular case they're still shown. 128 00:21:25.050 --> 00:21:25.770 Simo Hellsten: Hmm! 129 00:21:27.690 --> 00:21:36.430 Aaron McHale: I think it does. It only impact the list of blocks. I think it only pass the list of blocks that you see. When you go to add a new block. Is that right, Ralph? 130 00:21:37.520 --> 00:21:40.530 Ralf Koller: Yes, and no. 131 00:21:40.690 --> 00:21:45.449 Ralf Koller: it. Basically. 132 00:21:46.700 --> 00:21:53.330 Ralf Koller: it's it's basically about the performance and the the scope of 133 00:21:53.810 --> 00:21:59.100 Ralf Koller: what's called field blocks create field block plugins created 134 00:22:01.260 --> 00:22:02.120 Ralf Koller: for 135 00:22:02.230 --> 00:22:08.579 Ralf Koller: directly visible. It is not much of a difference. The only difference was basically, if you 136 00:22:08.820 --> 00:22:19.349 Ralf Koller: check everything there, then, for example, no matter the example I've taken here with the account settings, no matter if the use layout build is activated or not. 137 00:22:19.760 --> 00:22:24.349 Ralf Koller: If that is checked. 138 00:22:25.750 --> 00:22:28.069 Ralf Koller: you will see basically 139 00:22:29.000 --> 00:22:35.560 Ralf Koller: the available fields. Otherwise, if it's this, one is unchecked. 140 00:22:36.120 --> 00:22:37.140 Ralf Koller: And 141 00:22:37.810 --> 00:22:40.809 here, in account settings is unchecked, then 142 00:22:41.050 --> 00:22:46.589 Ralf Koller: the list is shorter. It's just the amount of fields shown. But 143 00:22:48.350 --> 00:22:56.000 Ralf Koller: the the real impact that is that issue is about is just the performance. Because if in the current state 144 00:22:56.090 --> 00:23:02.730 Ralf Koller: which is basically to expose everything and create for every entity type those 145 00:23:03.430 --> 00:23:08.360 Ralf Koller: field block plugins. it's a performance trick. 146 00:23:09.110 --> 00:23:15.450 Aaron McHale: and in in the chat, Scott says, expose all fields. 147 00:23:15.670 --> 00:23:19.549 Aaron McHale: equals, provide fields to be placed in a layout. 148 00:23:22.280 --> 00:23:24.830 skaught: Yeah, the phrasing's awkward. 149 00:23:25.080 --> 00:23:26.790 skaught: That's the first piece of that. 150 00:23:27.410 --> 00:23:34.920 Aaron McHale: I also may I actually say I think it's strange to also 151 00:23:35.250 --> 00:23:37.999 skaught: have a line. I'm talking about 152 00:23:38.180 --> 00:23:40.950 skaught: performance of this because it's an in min form. 153 00:23:46.290 --> 00:23:54.840 skaught: like, yes, it takes more. It takes more to create the list of fields and place them. But it is an inmate form, it is for editing and layout content. 154 00:23:55.150 --> 00:24:00.480 skaught: It's it's it's a piece of information that makes somebody worry about something that I don't think they should need to worry about 155 00:24:01.870 --> 00:24:02.859 skaught: as ecosystem. 156 00:24:04.250 --> 00:24:04.960 Aaron McHale: Hmm! 157 00:24:13.470 --> 00:24:14.270 Ralf Koller: And 158 00:24:16.920 --> 00:24:28.570 skaught: the other thing if I'll go on. The one other thing that's really kind of weird is that this form? I'm actually sure. Yeah, I'm not actually sure I know about layers. Of course, I'm not actually sure about this specific form when it was added 159 00:24:28.740 --> 00:24:35.809 skaught: to like actually released, I guess. But in general it's weird to have this separate form in a different place 160 00:24:35.890 --> 00:24:41.729 skaught: rather than on the content type, when you're enabling the layout for specific entity. 161 00:24:42.070 --> 00:24:52.479 skaught: and then, you know, it would make more sense if it was on each entity that you were actually specifying rather than a global option. Because there might be another entity where you want to user fields. 162 00:24:55.750 --> 00:25:02.380 skaught: Right? So you're cutting, you're cutting out everything across the board. But situationally, there might be another content type where you want 163 00:25:07.480 --> 00:25:10.690 Ralf Koller: just one word about 164 00:25:11.910 --> 00:25:16.769 Ralf Koller: that issue got committed 165 00:25:18.070 --> 00:25:26.390 Ralf Koller: maybe a week ago. and is destined for 10.3. So it is not in a public release yet. 166 00:25:26.870 --> 00:25:31.640 Ralf Koller: In regards of your second point, to provide that 167 00:25:32.820 --> 00:25:36.099 Ralf Koller: configuration on every content type. 168 00:25:36.650 --> 00:25:41.080 Ralf Koller: I'm not sure if 169 00:25:43.360 --> 00:25:49.410 Ralf Koller: it's it would be too granular. And 170 00:25:51.520 --> 00:25:52.839 Ralf Koller: against the 171 00:25:54.920 --> 00:25:58.289 Ralf Koller: basic paradigm that this issue is about 172 00:25:58.860 --> 00:26:01.489 Ralf Koller: not sure. 173 00:26:03.360 --> 00:26:08.770 Ralf Koller: And it would maybe also overcomplicate things even more 174 00:26:09.040 --> 00:26:11.789 Ralf Koller: cause with, for example, the 175 00:26:12.470 --> 00:26:16.080 Ralf Koller: unchecked state. You already have that 176 00:26:17.270 --> 00:26:26.349 Ralf Koller: behavior. You outline that you can decide on a per content type basis if something is exposed or not. 177 00:26:27.670 --> 00:26:36.760 Ralf Koller: And therefore I think it is okay. My bigger gripe is basically the 178 00:26:37.560 --> 00:26:45.200 Ralf Koller: the form in the the form. The control is exposed to the user or present it with a check box. It's 179 00:26:45.390 --> 00:26:54.899 Ralf Koller: sort of suboptimal to wrap your head around. Basically, you first expose all fields and then you explain each state 180 00:26:55.320 --> 00:26:56.750 Ralf Koller: of the checkbox. 181 00:26:57.010 --> 00:27:12.889 Ralf Koller: that's rather challenging. And from my perspective, I think it might be reasonable to apply a pattern we've recommended previously before, with going with radio buttons and the right buttons. In that case, add 182 00:27:13.010 --> 00:27:25.170 Ralf Koller: might shorten. Then you don't. You can skip basically the when enabled when disabled part and make it being more specific on every radio button and make the actual description. 183 00:27:25.520 --> 00:27:28.260 Ralf Koller: Just about the performance and the implications there. 184 00:27:30.100 --> 00:27:31.649 skaught: Yeah, I agree. 185 00:27:34.180 --> 00:27:36.950 Aaron McHale: Sorry. Yeah, Thomas, use your hand up. 186 00:27:37.170 --> 00:27:40.140 Thomas Howell: Thank you. So 187 00:27:40.300 --> 00:27:49.679 Thomas Howell: for my days in support drupal sites. Things like this are enormous ly problematic 188 00:27:50.440 --> 00:27:53.100 Thomas Howell: in that, just because it says 189 00:27:53.380 --> 00:28:11.129 Thomas Howell: could significantly decrease performance. People have a tendency to just make this kind of change, and then not know how to find where it is, and the only symptom you can find is a slew of very slow database calls 190 00:28:12.790 --> 00:28:14.579 and it can be 191 00:28:15.630 --> 00:28:37.500 Thomas Howell: frustratingly difficult to troubleshoot. Why, a site is slow. So my primary concern is that this is off in the middle of nowhere. And if I were to build a site and Aaron, you were to come and say, this site is super slow, and and Thomas is gone, and he's not here to work on the site. I have no idea what Thomas did. 192 00:28:37.680 --> 00:28:39.130 Thomas Howell: That's killing my 193 00:28:39.560 --> 00:28:40.420 I 194 00:28:40.970 --> 00:28:42.320 Thomas Howell: database calls. 195 00:28:42.970 --> 00:28:59.530 Thomas Howell: And this is highly effective for a certain class of website. It's very useful for websites that have a low number of users, or where you can basically cache everything, or you don't have an insane number of fields. 196 00:29:00.470 --> 00:29:22.190 Thomas Howell: But that's a pretty specific use case in which you can safely do this without blowing your site up. And so again, I'm not saying, get rid of it. It's not an evaluation of if this is needed, but it's I'm not a fan of where this is, or how difficult it would be to find something that could be potentially 197 00:29:22.280 --> 00:29:36.359 Thomas Howell: catastrophic for a site like if someone came in and flipped that on a production site because they, because Aaron came in and I built the site, knowing this couldn't be enabled, and it got flipped on, and then nobody knew what was happening. 198 00:29:36.630 --> 00:29:40.430 Thomas Howell: That worries me, that it's that something so impactful is 199 00:29:40.540 --> 00:29:46.700 Thomas Howell: essentially hidden in a configuration space that people aren't going to see, you're more likely to see it 200 00:29:46.730 --> 00:29:52.020 Thomas Howell: if it's at least visible from individual content pages. 201 00:29:52.830 --> 00:30:16.070 Thomas Howell: So even if we don't want to enable it from there, because it changes the paradigm. We need to have some form of messaging that is visible elsewhere, either on your report page or on content pages. But there has to be something when a significant, a potentially significantly performance impacting decision has been made so that people can find it again. 202 00:30:19.590 --> 00:30:21.680 Thomas Howell: And I'll get off my soapbox. 203 00:30:25.620 --> 00:30:27.480 Aaron McHale: So, Scott, did you want to come back in? 204 00:30:29.020 --> 00:30:34.960 skaught: Yeah, no, I was just agreeing with the radios might make it more obvious, because then you have labels and descriptions. 205 00:30:37.310 --> 00:30:38.730 Aaron McHale: Yeah, I read, we 206 00:30:39.150 --> 00:30:40.189 Aaron McHale: sorry. Go ahead. 207 00:30:41.040 --> 00:30:45.440 skaught: I agree with the soap box like it's it is the complexity of we wanna 208 00:30:45.750 --> 00:30:56.110 skaught: add the function in. I know that also, just to know that using the navigation menu. But the content authoring menu navigation is that part of core. Now where we have content authoring and text formats 209 00:30:56.130 --> 00:30:59.650 skaught: in this new little menu outside of navigation. 210 00:31:01.330 --> 00:31:06.249 Aaron McHale: Yeah, it's Ralph, could you go up to the configuration screen. 211 00:31:08.600 --> 00:31:21.919 Aaron McHale: Oh, maybe, is the background to do it. Yeah. So this is what you what you see right now here. So content offering, you see there. So that has always been there. It's just the new navigation provides a different way of like 212 00:31:21.950 --> 00:31:29.410 Aaron McHale: navigating so people less people will see this page in the future with the new navigation scheme. 213 00:31:30.630 --> 00:31:35.250 skaught: Yeah, I expect text formats to be someplace else in my head. That's what it's growing up. 214 00:31:35.510 --> 00:31:37.919 Aaron McHale: And there is some, some work 215 00:31:37.950 --> 00:31:43.740 Aaron McHale: that has happened on rethinking the navigational structure, but 216 00:31:43.940 --> 00:31:55.819 Aaron McHale: no changes have yet come of that. Simo says chat expose all fields, is blocked in layout builder Ui. 217 00:31:56.180 --> 00:32:03.770 Aaron McHale: as I guess you're proposing it as the title, and then 2 radio buttons, first one to be on, or 218 00:32:03.930 --> 00:32:10.850 Aaron McHale: that with a label for all intepes, the second one per entity type specific setting. 219 00:32:11.360 --> 00:32:15.309 Aaron McHale: So this would be back on the thanks, Ralph, for copying that. 220 00:32:15.470 --> 00:32:22.039 Aaron McHale: Yeah, maybe if you go right, if you go back to the Layer builder settings Ralph. 221 00:32:22.330 --> 00:32:42.139 Aaron McHale: there! There is 2 things here that you know people have mentioned. There's one is the we use, you know, restructures use radio buttons, which I fully support. And the other thing is a good thing about like making this easier to find. So you know something in the stages report or you know. Maybe I was thinking as well, like even a link 222 00:32:42.170 --> 00:32:57.409 Aaron McHale: like a a a text and a link next to when the button where you turn on the use of layout builder. and that could be a good place to indicate. Hey, there is an additional. So I think, perhaps cause I think, yeah, it's like, people aren't used to this page existing this form. 223 00:32:57.580 --> 00:33:03.559 Aaron McHale: Awareness. It's important to raise awareness. But it's here. 224 00:33:04.650 --> 00:33:05.330 Ralf Koller: hmm! 225 00:33:06.210 --> 00:33:15.810 Ralf Koller: Maybe even in both places, for one on the content type or the entity type, very activated and at the same time. Also in the status report. 226 00:33:16.210 --> 00:33:28.770 Ralf Koller: Yeah, in case the checkbox is checked here. set a warning, maybe. And if a certain number of basically fields is available that is created, or 227 00:33:28.820 --> 00:33:33.090 Ralf Koller: a certain threshold of a number of 228 00:33:33.160 --> 00:33:35.280 Ralf Koller: field block plugins is reached. 229 00:33:35.880 --> 00:33:36.630 Aaron McHale: Yep. 230 00:33:37.610 --> 00:33:44.470 Simo Hellsten: it might be an overkill, but its one possibility would be to use the same kind of status message 231 00:33:44.480 --> 00:33:47.890 Simo Hellsten: that we have been discussing about. When 232 00:33:48.260 --> 00:33:55.480 Simo Hellsten: some some settings are overridden in settings dot Php. 233 00:33:55.580 --> 00:33:56.610 Ralf Koller: so 234 00:33:57.060 --> 00:34:00.029 Simo Hellsten: so that kind of it would be something that 235 00:34:00.330 --> 00:34:07.019 Simo Hellsten: it would be using existing fashion, and but it might be to kind of to 236 00:34:08.350 --> 00:34:11.950 Simo Hellsten: too much emphasis on that. But that's one option. 237 00:34:12.800 --> 00:34:20.300 Ralf Koller: mean 1 Si have to link 238 00:34:22.199 --> 00:34:28.430 Ralf Koller: that issue. The there is no indication on configuration forms. If there are overwritten values. 239 00:34:32.389 --> 00:34:41.630 Aaron McHale: Yeah, that was when we looked at last week. I think, Seymour, are you saying like they all like, so having this is something you can 240 00:34:41.920 --> 00:34:48.429 Aaron McHale: turn on and configure it in in the settings file or somewhere. That that isn't maybe isn't in the user interface. 241 00:34:48.870 --> 00:34:52.790 Simo Hellsten: I was thinking that if we want to show this, if 242 00:34:52.820 --> 00:34:58.059 Simo Hellsten: show information that this check box for all, all 243 00:34:59.030 --> 00:35:05.789 Simo Hellsten: all entity types has been already has been selected for all entity types for that. The other check box on that 244 00:35:06.260 --> 00:35:08.120 Simo Hellsten: entered a specific form. 245 00:35:08.900 --> 00:35:13.970 Simo Hellsten: Doesn't have effect. Then it would kind of explain to the user that 246 00:35:14.520 --> 00:35:21.739 Simo Hellsten: if you check, check this check box or uncheck it, it doesn't have effect, because it's a kind of a global setting that's overriding it. 247 00:35:22.790 --> 00:35:26.990 Simo Hellsten: So it's kind of a so a user wouldn't wonder why 248 00:35:27.050 --> 00:35:28.429 Simo Hellsten: he or she can't 249 00:35:28.510 --> 00:35:30.139 Simo Hellsten: turn it off 250 00:35:30.800 --> 00:35:31.640 Simo Hellsten: from them 251 00:35:31.760 --> 00:35:34.300 Simo Hellsten: content by specific setting 252 00:35:38.610 --> 00:35:42.149 Aaron McHale: right? Cause. This is. This is only a global 253 00:35:42.470 --> 00:35:44.500 Aaron McHale: level option, which is 254 00:35:44.980 --> 00:35:49.049 Aaron McHale: Scott noted earlier, is 255 00:35:49.400 --> 00:36:02.129 Aaron McHale: something that maybe could be configured per layo. And I know. And obviously it's worth noticing that I think, Ralph, you mentioned earlier that this issue is already committed, so anything here that we recommend will be done follow up issues. Therefore, I think 256 00:36:02.200 --> 00:36:07.900 Aaron McHale: if we feel if we feel strongly about making the case to have this 257 00:36:07.950 --> 00:36:22.719 Aaron McHale: configurancy type, and that's something. Where could be a follow up issue. I'm not sure technically how how that would work. But as we have sometimes the lock share this meetings, we we don't necessarily worry about the technical details. 258 00:36:22.900 --> 00:36:28.800 Ralf Koller: Ralph, go ahead. Just one thought about them or suggestion. 259 00:36:29.970 --> 00:36:34.150 Ralf Koller: I'm not sure if it is a 260 00:36:34.480 --> 00:36:38.889 Ralf Koller: if it would be appropriate to have some sort of info message or 261 00:36:39.140 --> 00:36:41.749 Ralf Koller: warning message. 262 00:36:41.760 --> 00:36:48.560 Ralf Koller: because it is not really the case, like overriding, or that is overwritten but overwritten by 263 00:36:48.710 --> 00:36:51.410 Ralf Koller: that's set that's setting. 264 00:36:52.770 --> 00:36:54.360 Ralf Koller: It's more of 265 00:36:55.740 --> 00:37:12.399 Ralf Koller: because in the end, the effect to the user, what basically fields are available and shown is more in most cases the same. It's more of under the hood in regards of performance. So 266 00:37:12.570 --> 00:37:18.989 Ralf Koller: I'm not sure if having a more. That's that's kind of admin message 267 00:37:20.600 --> 00:37:25.220 Ralf Koller: would be the right thing. I I'm more drawn to 268 00:37:25.440 --> 00:37:29.450 Ralf Koller: the suggestion of Thomas says, like some sort of 269 00:37:31.490 --> 00:37:34.020 Ralf Koller: line or status, and 270 00:37:34.440 --> 00:37:41.550 Ralf Koller: next to the activate, the layout builder, setting and all the 271 00:37:41.850 --> 00:37:45.470 Ralf Koller: setting on the state of support, including maybe a threshold. 272 00:37:46.070 --> 00:37:48.039 Ralf Koller: Something like that is 273 00:37:48.290 --> 00:37:50.200 Ralf Koller: probably the 274 00:37:51.560 --> 00:37:54.250 Ralf Koller: less invasive and less 275 00:37:54.670 --> 00:37:59.190 Ralf Koller: visually striking one. 276 00:38:00.050 --> 00:38:00.830 Aaron McHale: Yup. 277 00:38:04.240 --> 00:38:19.140 Aaron McHale: okay. So we we are getting posted halfway through the meeting. So it might be good to start. Well, I guess we'd be bike shedding here. But start to come up with some recommendations if there aren't any other fine questions. 278 00:38:19.350 --> 00:38:39.299 Aaron McHale: And we've already got a couple of good suggestions there in the in the form of that might be quite easy to get out in the form of adding a safe support message. If this is enabled and also potentially a link below the the use lay of other option on content types. 279 00:38:39.590 --> 00:38:41.499 Aaron McHale: so I'll just do a quick 280 00:38:42.060 --> 00:38:53.349 Aaron McHale: thumbs up. Actually. So if who would be in favor all the status support message when this is enabled, just give it like a thumbs up in in zoom a Seymour, Ralph. 281 00:38:53.640 --> 00:38:54.600 Aaron McHale: Thomas. 282 00:38:57.870 --> 00:39:05.319 Aaron McHale: Okay, cool. And similarly, if we had like on 283 00:39:05.870 --> 00:39:12.889 Aaron McHale: next, I guess below the the use layout builder checkbox on 284 00:39:13.130 --> 00:39:15.029 Aaron McHale: the monitiously. 285 00:39:15.200 --> 00:39:19.079 Aaron McHale: In fact, maybe, Ralph, if you could quickly jump over to like 286 00:39:19.250 --> 00:39:22.159 Aaron McHale: I manage this way, we can. We can. Just so we can see that. 287 00:39:22.960 --> 00:39:31.219 Aaron McHale: yeah. So like, I'm guessing we were talking about on this page where we've got use layer, builder, 288 00:39:31.250 --> 00:39:38.989 Aaron McHale: do people feel that some kind of something here like a link below the use layout builder, or or some information there might be useful. 289 00:39:46.470 --> 00:39:49.710 Aaron McHale: feel free to also comment on the idea. 290 00:39:53.250 --> 00:39:55.809 skaught: Yes, because I'm people know where they can go to. 291 00:39:57.020 --> 00:39:57.820 Aaron McHale: Yeah. 292 00:40:03.300 --> 00:40:10.080 Ralf Koller: so basically on on the manage display 293 00:40:10.360 --> 00:40:16.089 Ralf Koller: more or less as an direction or way finder to the actual setting 294 00:40:16.160 --> 00:40:19.859 Ralf Koller: and the state of support for the actual warnings. 295 00:40:21.330 --> 00:40:24.460 Aaron McHale: Yeah, cause II think this kind of builds on. 296 00:40:24.710 --> 00:40:30.790 Aaron McHale: Certainly what Thomas was saying, where like, if you have this on, and you don't know why the site is slow, like 297 00:40:31.430 --> 00:40:33.690 Aaron McHale: how did 298 00:40:34.300 --> 00:40:45.499 Aaron McHale: it was like you, you know, raising awareness of the fact that this is. you can go here. I guess I'm thinking, as well like, if we have a stage of support message, do we then, do we need something here that. 299 00:40:45.570 --> 00:40:50.030 Aaron McHale: you know takes you to that also takes you to those sightings? 300 00:40:52.410 --> 00:40:53.430 Aaron McHale: Yeah, Thomas. 301 00:40:54.300 --> 00:41:01.469 Thomas Howell: it might be extraneous. However, contextually it would make sense. 302 00:41:02.620 --> 00:41:15.970 Thomas Howell: it. It doesn't. A. I think they would serve different purposes here, making it visible helps people who are enabling layout builder know that they're that the option is available. 303 00:41:16.690 --> 00:41:40.750 Thomas Howell: and so I think, adding it here is about making the option visible, which is helpful, but slightly different than the concerns I had, which putting it onto the status page would help alleviate, though I would also add that it should drop some message into or some warning into the log 304 00:41:41.420 --> 00:41:42.979 Thomas Howell: when you enable it. 305 00:41:43.750 --> 00:41:48.670 Because that way, if someone's searching their logs, they could see a warning in the log as well. 306 00:41:52.390 --> 00:41:55.769 Aaron McHale: Yeah, that's a good idea. Scott. 307 00:41:56.590 --> 00:41:58.700 skaught: Logs aren't persistent, though. So 308 00:41:59.170 --> 00:42:00.549 skaught: that's not gonna really be 309 00:42:01.070 --> 00:42:08.029 Thomas Howell: it. It's not persistent. But it's still a record of the action being taken, whereas 310 00:42:08.750 --> 00:42:20.999 Thomas Howell: the status page is doesn't show you when something was enabled, and both pieces can be important when troubleshooting, so that I know that oh. 311 00:42:21.190 --> 00:42:31.969 Thomas Howell: Thomas is the one who enabled this because I was the one making changes at such and such a time. That's different than what the status page does. The status page is about addressing in real time 312 00:42:32.020 --> 00:42:40.450 Thomas Howell: that there is a problem, whereas the warning that gets dropped into the logs about recording when a system impactful action has been taken. 313 00:42:43.760 --> 00:42:44.600 skaught: Understand? 314 00:42:45.980 --> 00:42:52.359 Aaron McHale: Yeah? And we do. I believe we do add log messages for things like when entities are deleted. 315 00:42:52.640 --> 00:43:03.869 skaught: yeah, but that's always the problem is again like watch dog. If if most sites are trimmed at 10,000 lines, then if you have a slight lot of errors that's going to get trimmed out before you even know it, anyway. 316 00:43:04.050 --> 00:43:22.649 Thomas Howell: But a a lot of places roll their logs and so really, that just becomes an administrative question. But then those same flick companies would have like configuration setup in their website. They know that somebody changed a configuration. They may not know who to blame, but they know what configurations been changed. It would get reset with a config reset. 317 00:43:23.820 --> 00:43:30.669 Thomas Howell: Yeah, all I know, is more information is typically better and storing it in the logs is better than not having it anywhere. 318 00:43:32.150 --> 00:43:33.730 Aaron McHale: Ralph. 319 00:43:34.450 --> 00:43:44.879 Ralf Koller: But you mean adding log messages, for when the layout builder is a use layout builder option a 320 00:43:45.150 --> 00:43:48.419 Ralf Koller: checkbox is activated. But wouldn't it be 321 00:43:49.230 --> 00:44:00.439 Ralf Koller: not for use? Layout I was talking about when you have all the expose, all feature. That's that's okay. That's that's functionally, okay, then I agree. Okay, so 322 00:44:00.470 --> 00:44:15.130 Aaron McHale: but that's something. I mean, that's not like obviously to be clear. That's not. I wouldn't say that's, you know, necessarily strictly usability thing. But I think if we're opening a follow up issue, that's certainly something that we could put in as a recommendation that it was the group felt that was a useful thing. 323 00:44:15.890 --> 00:44:18.280 Aaron McHale: so yeah, just to go back. 324 00:44:18.540 --> 00:44:28.019 Ralf Koller: Sorry, Ralph, your hand sold. Did you have another thing hard to lower the hand sharing at the same time? 325 00:44:28.210 --> 00:44:42.970 Aaron McHale: Okay, so we does sound like we have good consensus on adding a state to support message. And potentially, also, you know, some kind of log message when this is enabled. That could be a an option. 326 00:44:43.180 --> 00:45:05.259 Aaron McHale: and rough. Do. Sorry. Could you slip back to the the manage display screen in a second? just if yeah. So W. With that use layable or option. I would in my head. I was thinking you could have like something that points people to there being like additional settings. 327 00:45:06.090 --> 00:45:16.650 Aaron McHale: But again, I don't know if that is something where it it would be, you know, excessive or necessary, if the log message the status report is enough to indicate that that option is turned on 328 00:45:16.830 --> 00:45:21.690 Aaron McHale: or if it's worth raising awareness of 329 00:45:21.780 --> 00:45:26.430 Aaron McHale: the fact that there there is now these additional settings that didn't previously exist. 330 00:45:27.790 --> 00:45:30.980 Aaron McHale: throwing that open for anyone who's got any any thoughts on it. 331 00:45:42.420 --> 00:45:51.649 Aaron McHale: Okay, I guess I guess no one has any any particular thoughts on that. So let's how about we go back to the the the configuration form. And 332 00:45:54.050 --> 00:46:06.980 Aaron McHale: yeah, Ralph saying in the chat, it might make sense for a wait to find. But stage 4 is more important. Yeah, okay, so I think the other thing. Obviously, we want to figure out here, and we could probably use a better time to do that is, is 333 00:46:07.110 --> 00:46:08.120 Aaron McHale: probably 334 00:46:08.420 --> 00:46:24.589 Aaron McHale: I'm still thinking we get the easy bit slightly first. This is probably the most challenging bit is figuring out, what, how should these radio buttons or how should you know this? Be restructured into radio buttons? Because, it. The thing, I think is challenging here is understanding 335 00:46:24.930 --> 00:46:42.750 Aaron McHale: and and communicating what the differences between when this is turned on and turned off, because even for me. The text here is, is I. I'm so I'm still a little bit. If I was reading at the first time, and I got I understand it now after I've demoed it, but I think for me reading it the first time. Would. 336 00:46:42.810 --> 00:46:48.519 Aaron McHale: I might not still not be clear on what the different options actually do. 337 00:46:52.520 --> 00:46:55.010 Aaron McHale: But I like to 338 00:46:55.560 --> 00:47:02.469 Aaron McHale: think it was. Was it seamless suggestion? As a starting point? I think we could probably try to work with that and see 339 00:47:02.620 --> 00:47:10.020 Aaron McHale: Would it be expose? 340 00:47:11.800 --> 00:47:17.920 Aaron McHale: Oh, Thomas, do you want to come in? 341 00:47:18.730 --> 00:47:21.450 Thomas Howell: Yeah, I was just gonna say that. 342 00:47:21.580 --> 00:47:28.520 Thomas Howell: I find the entire form page really odd, because it feels like a massive waste of space. 343 00:47:29.810 --> 00:47:38.279 Thomas Howell: Just kind of you. You're looking at this single check box in the middle of a page, and it just feels 344 00:47:40.080 --> 00:47:54.540 Thomas Howell: just feels like it's it's and I don't know if we do this in a lot of other places like, I don't recall a bunch of places where you have a single check box in the middle of a form, and that's all that exists. 345 00:47:55.400 --> 00:48:13.619 Aaron McHale: Well, there, there is an example of the role setting screen that has a single option. That was something we did advocate for, and I think it was on the basis that the account settings screen was not the right place for role settings. And 346 00:48:14.120 --> 00:48:30.799 Aaron McHale: I also I don't know. III understand your point. I would. Just, I'm trying to think, where, where else could we put this? Because there aren't really another place for global land or settings. No, II and just like the media library settings, and it makes sense. 347 00:48:30.940 --> 00:48:35.239 Thomas Howell: It just I'm thinking of it again from a 348 00:48:36.010 --> 00:48:41.889 Thomas Howell: why I brought up the the logging message earlier is part of usability to me is find ability 349 00:48:42.500 --> 00:48:43.670 Thomas Howell: and 350 00:48:43.740 --> 00:48:52.600 Thomas Howell: if you think of each page as an additional node in an information network, or 351 00:48:52.670 --> 00:49:04.680 Thomas Howell: sort of like a a web page. And it's the more the more you spread the information out the more challenging you make it for an administrator to find these things which know they even exist. 352 00:49:07.640 --> 00:49:32.580 Thomas Howell: And so that's a it's a usability per issue, because you wanna make certain that people know that an option exists and simply having. If it was a top level menu item, then they would know it exists, but the moment you've put it a couple of levels down you have to know. Go to configuration, go to content authoring, then go to layout builder, and there's gonna be something specific and nothing else useful 353 00:49:32.580 --> 00:49:41.000 Thomas Howell: is on this page but the ability to expose all fields. And that's that's the concern. I don't have a solution for it. But I 354 00:49:41.180 --> 00:49:58.180 Thomas Howell: that's why that's how the perspective I'm taking. As we have this discussion about what information should be here. What should be elsewhere, and when I hear things like well, should it be in this place or that place that's about trying to address the findability? 355 00:49:58.380 --> 00:50:06.069 Thomas Howell: And I don't know if we are solving a symptom rather than trying to come up with a cure. 356 00:50:06.680 --> 00:50:07.660 Aaron McHale: Hmm. 357 00:50:07.890 --> 00:50:20.989 Aaron McHale: yeah, I'm I'm trying to find it. But there was an issue that I think I proposed a while ago in the ideas queue to make it easier to deep link between parts of the admin ui, so that. 358 00:50:21.040 --> 00:50:24.900 Aaron McHale: and if that was ever done, the the self case there was like. 359 00:50:25.200 --> 00:50:32.090 Aaron McHale: if you're deep in the field, ui! And there's some settings somewhere else like this is a good example of that. It would be a standard way to 360 00:50:32.360 --> 00:50:38.929 Aaron McHale: go to that. So if that ever gets done that would certainly help with with what you're describing there, because I know that is a 361 00:50:39.170 --> 00:50:51.599 Thomas Howell: a tricky a tricky problem. And looking at this, my question becomes, why is layout builder its own page rather than something that's on a content, authoring configuration page 362 00:50:52.010 --> 00:51:01.840 Thomas Howell: like, I don't understand why we wouldn't bubble these things up to a more consolidated page for configurations. 363 00:51:04.340 --> 00:51:05.350 Aaron McHale: Raf, go ahead. 364 00:51:06.210 --> 00:51:09.569 Ralf Koller: I think 365 00:51:09.870 --> 00:51:24.219 Ralf Koller: at this point it's just a single setting. But this discussions to extend the functionality of layout builder like with something like layout builder plus at the moment the contract module 366 00:51:24.310 --> 00:51:31.640 Ralf Koller: and then more settings in the context of layup builder would go in. But at this point 367 00:51:31.940 --> 00:51:40.190 Ralf Koller: I'm not even sure if I would file it under content. Author's okay, it's about exposing 368 00:51:40.200 --> 00:51:44.149 Ralf Koller: feels. But, on the other hand, it's more about 369 00:51:44.440 --> 00:51:47.739 Ralf Koller: performance and the underlying 370 00:51:49.440 --> 00:51:56.310 Ralf Koller: behavior, how things are handled. And so maybe I would even put it under something like 371 00:51:56.520 --> 00:51:58.559 Ralf Koller: development or system 372 00:51:58.630 --> 00:52:02.330 Ralf Koller: cause it's performance related. But yeah, it's yeah. 373 00:52:02.620 --> 00:52:03.599 Ralf Koller: not sure. 374 00:52:05.010 --> 00:52:12.180 Aaron McHale: But then, as you said, if there's more things coming in here, then yeah, does that make sense? Scott, you have your hand up, please come in. 375 00:52:12.830 --> 00:52:22.420 skaught: I think it's this, I agree. Development then, makes it a developer setting. And then people know that they shouldn't mess with the setting right? Other users. If I'm not a developer they wouldn't 376 00:52:22.540 --> 00:52:25.990 skaught: hopefully have access to the developer menu. I know that permissions don't actually do that. 377 00:52:26.300 --> 00:52:30.229 But that would clarify that the setting is a performance setting 378 00:52:30.700 --> 00:52:37.359 skaught: right? That's the direction. Whereas then, putting it back on the entity type clarifies that one, you're doing it on the entity. 379 00:52:37.580 --> 00:52:44.570 skaught: you're doing it per entity that way. If different entities need to be handled differently like this is literally like literally on our website right now, we have. 380 00:52:44.840 --> 00:52:53.959 skaught: we're doing, you know, Bios. And we need the author bio on it. So once one content type, we need the user field. so that you know that basically breaks our project 381 00:52:56.250 --> 00:53:02.190 Aaron McHale: right? So layout on one note, like, if every node is allowed a different layout. 382 00:53:02.310 --> 00:53:06.920 skaught: some nodes you may want to use field some you may not like, you know, your use cases are huge, right? But 383 00:53:08.920 --> 00:53:22.869 Aaron McHale: yeah, so there's a couple of things there like, there's there's that idea of. Could this be an entity level setting? In which case that it it doesn't need to live in configuration all so it looks near or next to the use layout builder 384 00:53:23.370 --> 00:53:24.350 Aaron McHale: setting 385 00:53:24.810 --> 00:53:31.760 Aaron McHale: that's turned on for an individual bundle, or potentially, as you said, it could live on. 386 00:53:31.840 --> 00:53:48.510 Aaron McHale: If we if we think this is more of a performance thing, there is the performance settings page under development, and that might be a more appropriate home for this? So there's potentially, yeah. So there's potentially 2 2 options there. 387 00:53:49.690 --> 00:54:01.329 Aaron McHale: and we, we could say that th, those are also you know, things that need to be considered. Because there is, you know, there's obviously implications there in terms of the the development effort. 388 00:54:03.770 --> 00:54:05.360 Aaron McHale: But yeah, 389 00:54:07.750 --> 00:54:15.529 Aaron McHale: I'd like, II, okay, so that that could be some additional things that we recommend. I do want to come back to the the specific 390 00:54:16.090 --> 00:54:23.340 Aaron McHale: form elements that form element, because I think it is important that we we provide some direction on 391 00:54:23.830 --> 00:54:26.419 Aaron McHale: the radio button 392 00:54:26.680 --> 00:54:27.940 Aaron McHale: option. 393 00:54:28.630 --> 00:54:34.090 Aaron McHale: I see. Actually, Scott has put in the chat that you still think 394 00:54:34.230 --> 00:54:44.850 Aaron McHale: the info about it, for performance is not needed. For this reason too much info for any user to understand. And is that in the oh, that's the third line. 395 00:54:45.970 --> 00:54:55.259 Aaron McHale: Yeah, I guess if it was moved to the performance page, then you kind of already are in the headspace of thinking. These are performance settings so 396 00:54:56.600 --> 00:55:03.750 Aaron McHale: certainly that could be a a a indicator that should live under performance. Ralph, go ahead. 397 00:55:04.110 --> 00:55:06.740 Ralf Koller: I'm 398 00:55:06.890 --> 00:55:09.959 Ralf Koller: not 100% sure that I agree, but 399 00:55:10.690 --> 00:55:12.860 Ralf Koller: sort of I do. And 400 00:55:13.170 --> 00:55:22.589 Ralf Koller: as a corresponding thought by adding to the status reports page and some sort of 401 00:55:22.730 --> 00:55:40.109 Ralf Koller: threshold there. If you get, then over a certain threshold and get the exclamation mark, hey? You may have a performance impact here. Queue to your setting on that at the moment. Layout layout builder, page. 402 00:55:41.100 --> 00:55:47.209 Ralf Koller: that might make the note about the performance unnecessary. But 403 00:55:48.470 --> 00:55:49.430 Ralf Koller: yeah, yeah. 404 00:55:50.550 --> 00:56:17.540 Aaron McHale: I think we? The good thing, though, is because what we can do is because we'll be creating call up issues. We can bring each issue back for more specific consideration. So we don't have to answer everything here. And we we obviously we might not get to the bottom of everything. But at least we have some guidelines about. You know, these are the kinds of things that we're we're recommending. And we can create issues around around those recommendations. And then and then, yeah, bring each one up meetings. 405 00:56:19.310 --> 00:56:31.329 Aaron McHale: but yeah, we are. We are actually about 46 min and so we don't have much time left, but it would be as I said, it'd be good to to see if we can make some progress on 406 00:56:31.470 --> 00:56:43.229 Aaron McHale: the the radio button option here, even if, like, I said, we, we put this in a specific issue, and then we bring this it, that issue up a a feature meeting for consideration. 407 00:56:43.380 --> 00:56:56.199 Aaron McHale: I guess one thing it it comes to mind based on similar suggestion. Which office got this one here is is it? Would we need to say, expose all fields. We could say, like. 408 00:56:56.440 --> 00:57:07.870 Aaron McHale: just expose fields as blocks exposed fields is blocked. They probably don't need to see if this is on the layer builder settings. Page probably don't need to stay layout builder. Ui, 409 00:57:35.500 --> 00:57:40.699 Aaron McHale: yeah. So yeah, it could just be like exposed fields as blocks. 410 00:57:43.230 --> 00:57:52.189 Aaron McHale: I guess. Keep in layered other like, I guess it. Yeah. Suppose it depends. Is the setting staying here, or is it getting moved? Would be the question. 411 00:57:53.540 --> 00:57:55.799 Aaron McHale: Because and you would. Wanna 412 00:57:58.080 --> 00:58:04.269 Aaron McHale: you know, if this lives on the performance page, you probably want to emphasize that this is for layover. But if it's on the layer builder settings page. Then 413 00:58:04.530 --> 00:58:05.190 Ralf Koller: yep. 414 00:58:38.720 --> 00:58:44.010 Aaron McHale: for the second one. There. Yeah, that you're editing. I'm wondering. 415 00:58:48.200 --> 00:58:50.440 Aaron McHale: So for entity 416 00:58:50.460 --> 00:58:51.510 Aaron McHale: type 417 00:58:52.730 --> 00:58:54.000 Aaron McHale: friends type. 418 00:58:56.350 --> 00:58:57.169 Aaron McHale: Thanks. Have a way 419 00:58:57.440 --> 00:58:58.380 active. 420 00:58:59.260 --> 00:59:02.519 Aaron McHale: Yeah, I guess it'd be for bundles, because it is per bundle. 421 00:59:03.050 --> 00:59:06.240 Aaron McHale: So I guess, instead of entity types there, we should say bundles. 422 00:59:06.610 --> 00:59:08.959 Ralf Koller: But that's one thing. 423 00:59:10.130 --> 00:59:15.650 Ralf Koller: I struggled with the most, and that for me it 424 00:59:15.940 --> 00:59:23.809 Ralf Koller: It was really the point about linguistic insecurity that is a field. All that entities 425 00:59:23.940 --> 00:59:33.970 Ralf Koller: bundles. I was uncertain if I'm picking the right term for the right context, and all right, just asking 426 00:59:34.050 --> 00:59:40.709 Ralf Koller: that functionality. If I understood everything correctly, I was always insecure. If I used the right thing and 427 00:59:40.760 --> 00:59:48.239 Ralf Koller: the term bundle, I'm not sure if it is use that often in the ui. 428 00:59:48.450 --> 00:59:52.000 Aaron McHale: Yeah, we don't tend to. If you, for example. 429 00:59:53.260 --> 00:59:56.220 Ralf Koller: look under help. it's for your model. 430 00:59:59.810 --> 01:00:00.740 Ralf Koller: A view mode. 431 01:00:01.020 --> 01:00:01.740 skaught: Yeah. 432 01:00:05.150 --> 01:00:08.370 Ralf Koller: no. I meant if you, if you search for bundle. 433 01:00:08.610 --> 01:00:12.589 Ralf Koller: and if you have any entry there, and there is no result. 434 01:00:12.840 --> 01:00:14.930 Ralf Koller: Even that is, that is the point. 435 01:00:15.270 --> 01:00:17.300 Aaron McHale: Cause we usually say 436 01:00:17.500 --> 01:00:27.509 Aaron McHale: we we usually talk about in terms of like content types, media types. You know, those are all bundles in themselves. 437 01:00:28.670 --> 01:00:33.459 Aaron McHale: so yeah, I. And obviously, some of you are involved in the drupalisms 438 01:00:33.690 --> 01:00:40.020 Aaron McHale: work, and we are keen not to introduce even more confusion. 439 01:00:41.240 --> 01:00:51.090 Aaron McHale: so. But I mean, answer, tax is probably fine, because, like technically like the Via, a lot of these fields per user. You know, it's the whole edge type. Or, yeah. 440 01:00:53.420 --> 01:00:54.509 Ralf Koller: yeah. But even 441 01:00:54.560 --> 01:00:59.660 Ralf Koller: an entity type is there, the is the overall thing. But an content type 442 01:01:01.550 --> 01:01:05.710 Ralf Koller: is basically a bundle, an old bundle. But 443 01:01:07.580 --> 01:01:10.889 Ralf Koller: it's tricky. And and it's it's not just about content types here. 444 01:01:11.960 --> 01:01:14.969 Ralf Koller: And I think, and using entity type 445 01:01:19.500 --> 01:01:28.180 Ralf Koller: and also communicating the the point. I've demonstrated with the article and the basic page example, that 446 01:01:28.410 --> 01:01:41.079 Ralf Koller: if you're editing a layout for article. then. even if you have exposed all fields as blocks today, outbuilder, active. then you still don't see the fields for 447 01:01:41.090 --> 01:01:43.049 Ralf Koller: basic page, and that 448 01:01:46.100 --> 01:01:48.280 Ralf Koller: has to be reflected somehow 449 01:01:49.440 --> 01:01:52.070 Ralf Koller: in the description as well. It's 450 01:01:52.780 --> 01:01:54.090 Ralf Koller: not trivial. 451 01:02:16.030 --> 01:02:23.379 skaught: Yes. So user fields are a related field. Right? So we're exposing other related field information to the content. 452 01:02:23.710 --> 01:02:25.380 skaught: We're currently headline. 453 01:02:27.240 --> 01:02:27.950 Ralf Koller: Yep. 454 01:02:59.690 --> 01:03:02.380 Aaron McHale: above access. 455 01:03:04.520 --> 01:03:05.870 Aaron McHale: Yes, 456 01:03:06.100 --> 01:03:08.629 Ralf Koller: your voice is currently distorted, Aaron. 457 01:03:16.010 --> 01:03:23.690 Aaron McHale: Sometimes that happens, I will switch to my laptop microphone. my headset is a wireless headset and 458 01:03:23.870 --> 01:03:25.359 Aaron McHale: the joys of bluetooth. 459 01:03:25.470 --> 01:03:29.019 Aaron McHale: So yeah, I think like. 460 01:03:29.170 --> 01:03:30.790 Aaron McHale: maybe 461 01:03:31.060 --> 01:03:36.649 Aaron McHale: the second option for entity types with maybe with layout builder enabled 462 01:03:46.430 --> 01:03:48.080 Ralf Koller: oops build a 463 01:03:54.990 --> 01:04:02.130 Aaron McHale: I think Quinn just suggested the same thing in the chat. I'll get Quinn and I can share credit for that one there. 464 01:04:03.680 --> 01:04:08.229 Aaron McHale: So we are getting close to the end of the meeting. 465 01:04:10.070 --> 01:04:27.370 Aaron McHale: how do people feel about the this? This latest version? And obviously like, I said we, we don't have to get to a final conclusion here. We can continue to iterate on this in slack and on the issue, and bring up the future meetings. But does this? 466 01:04:27.430 --> 01:04:31.510 Aaron McHale: this is feel like an improvement to people in terms of where where we started. 467 01:04:37.780 --> 01:04:39.309 Aaron McHale: I'm not from Semo. 468 01:04:41.290 --> 01:04:45.009 Aaron McHale: Thomas as well. And Scott, you have your hand up. 469 01:04:47.230 --> 01:04:49.810 Aaron McHale: Oh, I'm Scott. 470 01:04:50.170 --> 01:04:53.250 Aaron McHale: Oh, is that just us? Is that? Just wait to be a thumbs up. 471 01:04:55.840 --> 01:05:10.770 Aaron McHale: yeah. So I think I think we we have made some good progress here because we've been able to provide some direction in terms of the follow up issues that can be created and also got some good progress in terms of the 472 01:05:10.950 --> 01:05:14.609 Aaron McHale: that's the how this could change. 473 01:05:15.470 --> 01:05:37.360 Aaron McHale: Ralph, I'm assuming you're you've been taking some notes there, or are you? Gonna review? Okay? Yeah. So we'll get. We'll get the follow up issues created. And please, please do join us in slack to continue the conversation. As I'm sure we will, we will continue in the Us. Channel and slack, and also on on the issues. 474 01:05:37.970 --> 01:05:46.439 Aaron McHale: is there anything? Just before we close out? We do have a few minutes left. So is there any anything anybody wants to mention before we close out. 475 01:05:47.180 --> 01:05:47.890 Aaron McHale: alright. 476 01:05:55.940 --> 01:06:01.520 Ralf Koller: Just one question in regards of the approach Lee already mentioned 477 01:06:01.530 --> 01:06:05.559 Ralf Koller: on the issue that a follow-up issue should be created? 478 01:06:05.600 --> 01:06:11.100 Ralf Koller: I think it might. since those 479 01:06:12.040 --> 01:06:17.790 Ralf Koller: several different interventions, basically 480 01:06:17.910 --> 01:06:24.959 Ralf Koller: to write everything up in a single issue and find it isn't basically an air quotes Meta issue. And then 481 01:06:25.150 --> 01:06:28.759 Ralf Koller: follow different follow-up child issues could be created from that. 482 01:06:30.350 --> 01:06:34.059 Aaron McHale: Yeah, that sounds that sounds like a good idea. Because, 483 01:06:35.580 --> 01:06:45.490 Aaron McHale: you know, we we have. For instance, we've recommended a couple of things around. This could be on the Nc. Type, or it could look under performance. And of course, that if 484 01:06:45.820 --> 01:07:04.789 Aaron McHale: that could impact how the setting ends up being, you know what what wording is used. Right? So I think it makes sense to just bring everything together into a single comment. That will, of course, help us just referencing it for the visibility issue. The meeting issue. So yeah, let's that sounds like a good idea. 485 01:07:06.600 --> 01:07:08.659 Aaron McHale: okay. And I think 486 01:07:10.670 --> 01:07:20.630 Aaron McHale: is that we're hitting up against the hour we do, I believe on Monday is the next drupalism speaking. That's correct. 487 01:07:20.640 --> 01:07:23.360 Ralf Koller: Yeah. And for those of us who are participating in that 488 01:07:23.430 --> 01:07:25.430 Aaron McHale: and 489 01:07:25.590 --> 01:07:35.350 Aaron McHale: yeah, I will see people on seasonal. So Monday thought look forward to seeing everybody, and next week's meeting, and you might help me again, because II think Benji is. 490 01:07:35.470 --> 01:07:50.739 Aaron McHale: unless anybody keen to volunteer to moderate because I have to. I'm probably gonna have to head away like sharp, or, in fact, I might not even might not even be able to do it next week. So we'll see. We'll figure out slack. 491 01:07:52.140 --> 01:07:54.209 Aaron McHale: then use it. Nitcamp 492 01:07:54.220 --> 01:08:06.649 Aaron McHale: perfect. Okay, we'll figure out slack. Then. Okay, thank you. Everybody for coming today and for your input and that, yeah, please do come back next week, assuming next week's meeting. Go ahead. So 493 01:08:07.030 --> 01:08:09.089 Thomas Howell: thanks so much. Aaron. Thanks everyone. 494 01:08:09.100 --> 01:08:13.569 Ralf Koller: Thanks everyone. Nice weekend. 495 01:08:13.840 --> 01:08:14.729 Aaron McHale: You, too.