Wagtail release candidates testing, step by step

Speaker 1: Go.

Speaker 2: Hello.

Speaker 1: Hey Sage.

Speaker 2: Hello, T-Bug.

Speaker 1: What's up?

Speaker 2: Good. Thanks. How are you?

Speaker 1: Great. I have some good news for you today.

Speaker 2: Oh, what is it?

Speaker 1: We have a Wartail, release, candidate to text!

Speaker 2: Wow.

Speaker 1: I know, right?

Speaker 2: When did that happen?

Speaker 1: Well, honey, you should ask. I have the dates right in front of me. Just a sec. Hello.

Speaker 2: Wow.

Speaker 1: Have you worked on this release, Sage?

Speaker 2: Oh I

Speaker 1: Let's be real. How much of your heart and soul have you poured into this over the

Speaker 2: last

Speaker 1: many months?

Speaker 2: A lot. It's hard to quantify, I think.

Speaker 1: Let's give ourselves some love. Let's give ourselves one favorite. Okay. Let's take a look, shall we?

Speaker 2: Yeah.

Speaker 1: Sage, I don't know if you've uh done this before. Have you ever tried um PS Candidate on the Real World project?

Speaker 2: Bakery demo is all I got.

Speaker 1: Bakery demo, our official demo site.

Speaker 2: Yeah.

Speaker 1: It's pretty rare for me as well. And um That's why we thought it would be really cool for us to actually try it out proper. Give people an example of what it looks like to try a release candidate of Wagtail on a project. We have the release candidate announcement posts from our colleague Matthew, aka Gasman, that says has quite a bit more details on um uh what it means to try out a release candidate and what to look out for in a specific release. Um and uh it's also very timely because it's not just White that has a release candidate or I guess I guess has a pre-release to try it, you know, another project. Sage that might have a pre-release at the moment. Starts with a D.

Speaker 2: Does it end with an O?

Speaker 1: Yes, it does. Django 5. 2 Alpha 1. Should we try the Django Alpha and Aries candidate at the same time?

Speaker 2: Oh, that would be fun.

Speaker 1: That would be fun, yeah. I don't even know if that's Possible, but um have you looked at the Django Rase candidates yet?

Speaker 2: Well, I'm running the dev version on my machine.

Speaker 1: There are quite a few things on here I have been aware of and lots more that I have not seen yet. So it'll be very interesting to spend time on there. We'll see if that's possible. It'll be fun to try I thought before we get going with um with this, I'll thought I'd also share um I guess some context on how important this is for us, the release candidates, and I assume the same for Django. Um yeah, Sedge and I have spent lots of time testing those features we've added to Wagtail. But there is, you know, testing with our demo sites and then there is the contacts with the real world. The real world of how people set up cocktail sites in all sorts of different ways. So what we're looking at here is um our statistics

Speaker 1: on how many people out there test the biggest candidates. So by version keep tabs of how many times three candidates are downloaded and basically the more the merrier um Sometimes we make lots of a push and lots of people try it out and sometimes we make less of a push and fewer do. Yeah this is super helpful for us to get that kind of feedback before the final release Have I shared this with you, Sage, before?

Speaker 2: I don't think so.

Speaker 1: Okay.

Speaker 2: The numbers, T-Bo, what do they mean?

Speaker 1: Uh So yeah, I guess when I say when I say buy version, so this is the numbers of download between the time at which we've released our you know pre-release version. and the time of the actual release so basically this state for work test six dot four that would be um when we put the release candidate number one and that date will be early February when Wagtail 6. 4 actually goes live for people. And then like everything after is just trying to quantify how that's how you know release candidates downloads compare with um normal white downloads. Like for example, if we had 1000

Speaker 1: RC downloads and only 10,000 people use Wagtail. That's a big number, 1000 RC downloads. Whereas if we have 100,000 people testing Wachtel and we still get 1000 downloads that's a bit less. Um anyway, there's no right or wrong number It's just fun to track to see how successful we are at encouraging people to try it out basically. And um yeah, let's take the plunge. Um I thought I would demo this on wactil. org. I've just opened it in my IDE. Um How do we get going? I guess I can uh get my dev set up and running and hope for the best.

Speaker 2: Maybe you want you want to make sure that it's on the latest main branch?

Speaker 1: Probably. No module named Django, that's a good start. Okay, I have not set it up in a while. Let's do this Docker setup so I don't have to check exactly how I might or might not have set up this project in the past. People who might not have used Docker yet, I'm looking around to check what's the best command to get the project up and running. I'm sure it's well documented in the README, but I like to have a peek at the configuration to see for myself.

Speaker 1: Alright. And port 8000 Okay, so I probably will also need To log into the container and to run server? Do you like Docker Sage?

Speaker 2: Um sometimes. It gets it can get complicated sometimes.

Speaker 1: It can get complicated.

Speaker 2: It does help sometimes.

Speaker 1: Oh might have to reset this account. Okay, there's quite a bit more needed to do, but we should be able to get there. Um the

Speaker 2: eight cache table.

Speaker 1: Yeah, I'm surprised that um Oh I can never remember which of the commands are

Speaker 2: no underscore

Speaker 1: underscore separated or not. Is

Speaker 2: is there any command that is I think the official ones from Django don't have an underscore.

Speaker 1: None of them

Speaker 2: I can't recall any of them. Yeah.

Speaker 1: Oh true, yeah. That's the rule

Speaker 2: then.

Speaker 1: Look, this is my our user workflow. K refresh.

Speaker 2: You can't see you refreshing hard enough.

Speaker 1: Um why do we have static files not loading? That's interesting Um

Speaker 2: cache, is it? You mean

Speaker 1: browser cache?

Speaker 2: Yeah.

Speaker 1: Ooh, nice one sage.

Speaker 2: Oh, waste the cache.

Speaker 1: I'm surprised not to have my media files working either, but it could be that I deleted the files. um at some point in the past to save space on my computer. And I think that should be okay anyway as far as testing. Wactel 6. 3. 1. So we are One patch release behind the latest. I assume we don't need to play to the latest patch. I can just do pip install wactest 6. 4 and see what happens.

Speaker 2: Yeah Here shall we try the um def zero thing? Um

Speaker 1: So Wagtail greater than six dot four dev zero is what you want to try?

Speaker 2: I think so, yeah.

Speaker 1: Can you say more about it?

Speaker 2: Well, why why is there no output?

Speaker 1: It's not a good sign, is it?

Speaker 2: Oh no, now you have a file called six four times zero equals actually.

Speaker 1: I assume there is sorry.

Speaker 2: Yeah, sorry. That was like redirecting the standard output. But yeah, the dot uh version dev zero is uh one of the valid spear specifiers. So this allows you to just use whatever the I guess the version newer than 6. 4, including three releases. So if in the future we put out a new RC release, like RC2. That 'll install RC2 instead of RC1.

Speaker 1: Yeah, we do quite often. Actually, I have some stats on that.

Speaker 2: Yeah.

Speaker 1: Number of RCs. Wow, it's been a while that we've not had RC2. Last time well we had one in May Well, actually a year ago technically. Um

Speaker 2: RC one was a mistake and it was immediately followed up by RC2, so it it doesn't really count, I'd say.

Speaker 1: Oh no That's why. So actually it's been since um wow two and a half years ago now that we've not had multiple RCs. Yeah, we used to do that way more way more.

Speaker 2: Yeah, because I think 3. 0 and 4. 0 was like the big jump to the UI.

Speaker 1: Yes. Is this Wagtail's Python free thing or

Speaker 2: you can say that.

Speaker 1: Oh, we definitely didn't go all the way there. Uh okay, we are on the latest and greatest stage.

Speaker 2: Well, no, unless you install from main

Speaker 1: That'll be for another day. Okay. And I assume that I um will still need to Who can I remember the uh manage the PY commands to change passwords? Is it that? What?

Speaker 2: I think you need to Yeah, provide the user.

Speaker 1: I was not expecting that. Maybe I just didn't read um error message or maybe our error message is just uh the kind that doesn't tell you if um the account doesn't exist What's your go-to password sage for your local dev setup?

Speaker 2: Change me.

Speaker 1: Change me. Do you know where change me comes from?

Speaker 2: Um, I feel like I saw it somewhere. But I'm not sure. Where does it come from?

Speaker 1: I don't know either. I'd just be very interested interested to know why uh at least for Wagtail, all of our demo sites, like local development demo sites, the admin password is always changed me. It is just so ironic and tasty to know that. Okay, we are in.

Speaker 2: Wow.

Speaker 1: And it is Wagtail 6. 4 RC1. And Woohoo! We have our page that tells us what has changed. So at least that works. That's great. And in the sidebar I have my notification that we have a new release. Thank you Sage for creating that capability

Speaker 2: Well, it's been years.

Speaker 1: I still love it. You know it's so easy when you're walking on a site with lots of people. for the person to that does the upgrades not to necessarily know who to tell that the upgrade has happened and now even if um they didn't know or someone wasn't around like they were on holidays and s or something. At least when they log in the CMS, they know that things have changed and they have a sense of why. Okay, um well I guess when I do when I try a new version of what they like this as part of a site upgrade, I'd probably spend time trying out some of the site's features. to see that they still work with the new version. Like exploratory testing

Speaker 1: with you know some sense of what the site's custom features are. But for today we could probably look at the release notes and See top to bottom how to test them since it's a risk candidate we probably want to try the specific features that are in there, no? Um and the first one is background tasks. That's quite a cool one. Have you um spent time looking into this before, Sage?

Speaker 2: Um I read Jake's RFC but um and also his enhancement proposal, but I haven't actually tried the package. But now we're forced to because it's uh

Speaker 1: it's not

Speaker 2: it's not a requirement of white tail

Speaker 1: now. Yes, that's so so cool Does he link to the RFC in there? Yeah, RFC 72. RFC 72 from 2021 from Jake, which turned into Dep 14 for Django which turned into the Django tasks package as a reference implementation and I'm not sure if he links to his pull request to Django in here, but yeah definitely at some point this would be directly in Django itself. But for now we get to try the package. And I have not ever used it myself, so I think we'll just have to trust the documentation of the package to know what to test.

Speaker 1: My understanding is that by default it's using this thing called immediate backend, which means that nothing 's actually running in the background. It just works the same as before in the current thread And uh yeah, we have a few other backend options. Uh I assume eventually there'll be like you know, task Q backends, but for now we have a database one. Let's try database backend and see what happens.

Speaker 2: Yep.

Speaker 1: Okay. So in the release notes for Wagtail we have a note of which features will work differently. Search index, creating entries for the reference index. Image focal points. Wow, that's quite cool. I didn't realize. Um Maybe we can look at the reference index and the search index. Um have you worked on the reference index yourself, Sage?

Speaker 2: Um not directly, so Yeah, I've used it in different places, but I was not very involved in the implementation of the index itself.

Speaker 1: I haven't either and I'm very glad that there are clever uh people out there that do this. Um I didn't know there were two like Wacted update index and update index. I wonder if it's just some backwards compatibility thing.

Speaker 2: No, it's to avoid clash with different package that uses the same command. I think there's another package that has update index command.

Speaker 1: I'm glad I've never had to think about uh namespace clashing for management commands before. Um so it looks like the um index updating works the same as before. with uh Django Tasks installed and um the references indexed you want to talk to us about what it's for Sage

Speaker 2: Um yeah, it's for tracking the use of model instances inside fields that may not necessarily be foreign keys but it also includes um tracking references through foreign keys but in white tail we also have things like stream field which is um Semi -structured data that uses JSON. Semi

Speaker 1: -structured Oh that's so funny. I wonder like if there is someone that that's made the chart of the the spectrum of data structuredness from like literally a blob of Nothing to I don't know what's the most structured you could get. What happens in the

Speaker 2: pretty structured?

Speaker 1: What's pretty structured?

Speaker 2: SQL.

Speaker 1: SQL Yeah, but you know, even these days, cool cool kids SQL like there is Jason Fields.

Speaker 2: Oh no

Speaker 1: Um I'm just setting up multiple terminals so I can um run those commands without quitting the server. We do we go there again. Um Yeah, I think feel like in my mind it's pretty structured to be honest. Like obviously, you know, we don't um necessarily intend people to query this data super easily, but there is a schema that makes the reference index feasible to start with.

Speaker 2: Yep.

Speaker 1: Um Okay, so let's switch over to the different task backend and hope for the best. requires Django tasks that backends. database adding to installed apps. That's interesting.

Speaker 2: Yeah, you might have to run migrations after that.

Speaker 1: Take a peach Migrations is another thing and I'm so happy clever people have figured out and they made it a part of the framework. Because um yeah I don't wanna reinvent that. Ooh typing. Jake, oh my gosh. Are we adding types to Django now?

Speaker 2: Very brave.

Speaker 1: I am um Giving a talk at FOSDEM. Not this weekend but the one after. And the topic is uh existential threats to Django. One of the threats will be making a decision on typing. Cause I feel like these days lots of people um rightly or not expect it from there. Um frameworks

Speaker 2: yeah because in some cases it also helps with well not in some cases in a lot of cases it helps with IDE as well as you write your

Speaker 1: code

Speaker 2: It's very helpful.

Speaker 1: Yeah, just that 's string non, even for the most basic of stuff. Like it's just not having to keep in your head like whether the dot gets method here what it defaults to Well obviously you know you still have to trust but ver but verify but

Speaker 2: yeah

Speaker 1: saves time okay um we are officially running the database backend according to this I Thought there might be some migrations showing up here. Oh, I forgot to add the installed apps line. Did you see Sage um Simon Willison 's uh Django plugins.

Speaker 2: I did, yeah.

Speaker 1: What do you think of it?

Speaker 2: Very magical. But also um well I can't imagine it being big at this point um because Django is very mature But

Speaker 1: if

Speaker 2: it were something that Django came up with in the very beginning, I can see it being like the way to install Django plugins.

Speaker 1: Yeah, that's a good point. That's another of my threats on the for my talk is uh like just uh You know, Django, I think lots of people would say one of its strengths is the package ecosystem. But it is non-trivial when you start to combine lots of different packages to make sure they all work together. Um and you know, make sure they all work together like that's both on the package maintainers, but also helping users. um configure and customize the packages is is quite quite tricky. Um Okay, um I feel like we should be up and running.

Speaker 1: Um nothing has just disappeared, so Update references index, hope for the best. YOLO I could use completion, but Is there a way to empty it altogether?

Speaker 2: I think it started out by emptying it out.

Speaker 1: Ah, okay.

Speaker 2: But you can technically delete all instances of the reference index model.

Speaker 1: Yeah. Well it all seems to be working. I think if I wanted to double check I might also I've never used this command, so there's a fair chance it's just me not using it right. Um if we had more time I might also look at um um database management tool to see what's happening in there. But for now I think we can just trust Jake to have done it right. And um See if there's anything else to test. Yeah, okay, so this would also be all be if we wanted to um

Speaker 1: Hmm. To spend more time in there. Ah, that's what I was missing. So why does it still walk then?

Speaker 1: I was a bit surprised it was so magical So maybe the output here is the same, but the actual indexing hasn't happened.

Speaker 2: We're not exactly sure which part of the rebuild command makes use of the tasks.

Speaker 1: Maybe. Maybe I'm thinking of this wrong. And what's actually happening is the command is already, you know, quite friendly towards background workers. So maybe we've not actually updated the command. We've just updated the rebuilding of the index when you actually make changes in the CMS.

Speaker 2: I think that's what happens. Yeah. I I I'm currently looking at the code. Yeah, it looks like if you rebuild the whole index, that's still not using because it doesn't really make sense to

Speaker 1: defer it to another command.

Speaker 2: Yeah It's for um taking something out of the uh what's normally in the request response cycle.

Speaker 1: Yeah. So I think the way we could test this is um to add a reference or do a page publication that would update the search search index, see it's not happened, and then um Then see the changes later.

Speaker 2: Yeah.

Speaker 1: Let's give it a quick go. I feel like I might be um a bit out of my depth with this. It might be better for switch to other features, but We can try. So for example, if I change the page title here, I would assume it would have to be reflected in the search index. Um published in twenty twenty five, let's keep it simple. And um I think from what I recall when you hit publish here, you get the a setting in Wagtail to decide, like a

Speaker 1: Django setting to decide if you want the such index to be resided automatically or for that to be deferred. So I assume that with the Django Task syllabus backend that would not be picked up by this db worker. But there might be more configuration needed.

Speaker 2: I'm not sure if it's supposed to have any output there.

Speaker 1: Yeah. All right. We'll just trust Jake on this one and switch over to the next one over. and get back to testing this more once we've um had more time to get up to speed with um Django Tasks API Ooh, preview for Streamfield Blocks, Sage. How exciting.

Speaker 2: What is that?

Speaker 1: Well, I mean I could show you a screenshot, but we have Sage himself who implemented the feature. Tell us more, Sage.

Speaker 2: What is a stream field block?

Speaker 1: You know you say that, but I realized until today that we actually didn't use the word stream field ever in our user guide for a while. CMS users?

Speaker 2: Is that intentional?

Speaker 1: I do not know. We do use it in marketing material for the CMS, but I think it's one of those terms that um You know, if you've never used heard of it before, you don't just don't know. So in the interface, at least within the CMS, it is very intentional that it never says stream field. It just talks about blocks. Because that's a you know more agnostic term. Yeah in the docs I think I'd prefer to keep it two two blocks as well but now and then it can be helpful to um use more idiosyncratic terminology. Yeah, that's what I drafted it here with.

Speaker 2: Okay.

Speaker 1: Um Yeah, let's uh let's try it out. So Sage you've not written documentation yet for this?

Speaker 2: Um I have. But very briefly I intend to update it during the RC release.

Speaker 1: That's great.

Speaker 2: Yeah. So this is the brief documentation on how to configure it. But I guess before we do that, um maybe we should look into the current state of the lock picker.

Speaker 1: Sure. So we're going to go. Let's go back to the same blog page. It's using Streamfield quite a bit. Headless survey. So we have our standalone CTA block. Within the stream fields with quite a few other options. Um And I guess I can pick any of the options. I can type something. And I'll see the results on the preview off to the side here.

Speaker 1: Why do we need a block preview, Sage?

Speaker 2: Well, if you look at the options we have for the blocks, maybe like um what does a teaser CTA plug look like

Speaker 1: well like a diamond obviously because it has a diamond right there Sage Yeah, I've I've been I'm a dev so I've been you know subjecting myself to this UI for quite a while and like already looking at this It looks like none of the none of the fields are required, but I can see off to the side here that there are validation errors So you know that some of these it's filling in and then it's uh it's a test of okay which fields might I need to

Speaker 2: Why does it not have the asterisk?

Speaker 1: Well yeah um I think there is a bug in Streamfield specifically for that. Or it could just be that you know it's conditional validation where it expects one of the three and

Speaker 2: you don't really have a good um

Speaker 1: yeah the language in a UI isn't so good for dependent

Speaker 2: edition

Speaker 1: like this.

Speaker 2: Yeah if you clear it and then you save it then it tells you but before that um There's because it's also not very friendly to just shoot a r an error message right away.

Speaker 1: True. Yeah, they need some kind of help text that says feel one or the other.

Speaker 2: Yeah, and that's already possible if the developer added an a help text for the block, right? True.

Speaker 1: Yeah. It's one of those features that I think has been there for quite a while, but people don't necessarily realize and maybe also they copy paste their block definition from project to project and don't Forget to forget to check if the new capabilities might be there. Okay, so that's um that's a page teaser. Um I wonder if I should add at least one test image to the site so it's a bit more meaningful.

Speaker 2: That's sad.

Speaker 1: I know, it's just me that has a broken dev setup. Um then we do

Speaker 2: Yeah, because it's quite a lot of files. The whiteel. org website has been around since for as long as WhiteDel existed, right? So it's got a lot of media files if we were to pull it all to your local machine.

Speaker 1: Yep. Now we're in business. Okay, so I was able to tell what the block looks like. And now we can try the block preview?

Speaker 2: Yeah. So yeah, uh yes uh uh the the reason why there is This new thing called block previews is as you just noticed we had to actually try to insert the block and then fill out the data to see what it's going to look like. Which if you are an editor and your developer has set up different types of blocks and you're currently writing your content, it can get in the way in so in in it in terms of like you may not know which block to e to choose like um if you don't remember the exact block because there's different types of blocks and it's going to be It would have been very useful if you could know what the block looks like before you choose it.

Speaker 2: And that's the thing that we're going to add to Wiketail.

Speaker 1: Indeed. And in real-world websites, this is a real-world website, but I I certainly think there are sites out there that have even more blocks than this because you don't necessarily want to have too many page types so it's quite natural to instead ramp up the numbers of blocks so you have more flexibility and then there might be Yeah, twice that amount is is no problem

Speaker 2: really.

Speaker 1: And then you know within those block types maybe there is some nesting even and it gets even trickier to know what's what Okay, let's see if your docs are good, Sage. Shown inside the block picker. To enable this feature, you must configure the preview value and templates. Yes. Description greats I like that. Let's do description first So here you have it on the struct block directly as a query parameter and then you have it in the meta class of the block.

Speaker 2: Yeah, so you can do it in different ways. Just adapt to what your currently code uh your current code is like.

Speaker 1: I can already, you know, again, like with the maintainer's perspective, hear someone in my mind asking Oh, can I change this based on the current user?

Speaker 2: Okay.

Speaker 1: Which of those methods take the request object, Sage? Just tell us.

Speaker 2: Context. You can find the request in the context.

Speaker 1: It's funny how often that comes up. I don't know if it's funny or if I should see a bigger pattern here. Let's see if we can find the blogs. So we are in the blog area of the site. And um yeah okay so we have block. py but in this case it all inherits from um story block that is shared across other areas of the site So we'll head there. Okay, quite a few block types coming straight from Wacktail And um a few coming from a separate blocks file specific to the project. We were looking at teaser block, right?

Speaker 2: Yep.

Speaker 1: So we have all of the fields, we can see the custom validation. Definitely something that we want to streamline someday, being able to select from different types of Um types of links. Is this where you would set up the block help text as well?

Speaker 2: I don't think I'm not sure if struct block has helped that. It's usually in the field blocks. Like a charter block or um Yeah, U of L block or something.

Speaker 1: Um yeah, so help text I think it's interesting nuanced there. I don't know if it's supposed to either or not, or just for that check. The point I guess is to help people feel the form description. The point is to help people understand. What even the head is the teaser block to start with? So I guess we could describe either the visuals or the intended use, um, or both. So maybe I could say something about uh featuring an existing page um with um full width Um

Speaker 2: is it a card or

Speaker 1: is a content and image And maybe we could describe also here which page types it's been built for specifically. You know, it could be that it's reused across lots of the sites now and then, but has been built primarily for this or that type of content. Is that the right length? Do you think it would be better if it had more?

Speaker 2: It wouldn't hurt to have more, but that's also already a good description.

Speaker 1: Mm-hmm. Oh, so I do need to have the preview set up for description to appear.

Speaker 2: Yeah.

Speaker 1: So I'll do that next. So preview underscore value. Oh, that's a chunky one for us to get started with

Speaker 2: I guess we can use a custom URL instead uh just to ease things up

Speaker 1: Yeah.

Speaker 2: Because otherwise if you need a page, you're going to need to make a database query.

Speaker 1: So then I would do that inside the get context rather than oh no inside get preview value.

Speaker 2: Yes.

Speaker 1: Let's see if um

Speaker 2: no, I haven't tested this. What's gonna happen What is this?

Speaker 1: I was not expecting that either. Oh, okay, that might just have been me.

Speaker 2: Um you also need to set up a review template.

Speaker 1: Ooh. So Sage, you've added a few options to do that. And I think your personal go-to would be the The global template?

Speaker 2: Yeah, because you likely already have a custom template for your blocks.

Speaker 1: Yep. Uh teaser. Yeah, it's a block. We even have some test data for it for it already. Tea's a book, tea the block. Hmm, oh CTA.

Speaker 2: No. It's right above that.

Speaker 1: Oh, thank you. Too many options. I got blind. Oh, teaser block preview is failing. See, that's why it's better for it to be directly in Wachtel. Then there is no need to use YAML for the configuration. Uh but at least here I can I could reuse the exact same thing as there for consistency. Or you know we could iframe that preview if we preferred. But I think for us.

Speaker 2: Just to clarify that template, uh sorry, the pattern library is not related to what we were talking about in Whitel.

Speaker 1: No Should it be?

Speaker 2: Mm, that's a good question

Speaker 1: Is that enough, Sage?

Speaker 2: Um well ideally you should extend from the built-in template because that's going to be like the actual page used for the iframe.

Speaker 1: So I have it in do I have it in the right folder

Speaker 2: I mean yeah if you don't want to set up the right path you can uh for now you can set a specific template just for that block. But not the others.

Speaker 1: It's not the right path.

Speaker 2: It is. Um, I think it is.

Speaker 1: I'm surprised it doesn't just show up here, even with my CD templates.

Speaker 2: Oh, wait. Um what's the order of the uh

Speaker 1: yes

Speaker 2: installed apps?

Speaker 1: I do not know.

Speaker 2: And or have you reloaded the server? Because you might need to for for the template loader to pick the new directory.

Speaker 1: Ah good point. Always forget about this. I wonder if there's a technical reason why um It's not autodetecting templates outside um the loader being reloaded. Ooh. Look at that sage. We even have a few other blocks that just have it walking just like that.

Speaker 2: Wow. What do they look like? I wonder.

Speaker 1: Oh

Speaker 2: hello

Speaker 1: hello

Speaker 2: everything is just hello

Speaker 1: See, that's why I really like that um Matthew started work for the next phase of work there on on default validation. To me, like I really like to go incremental and do the least amount of work to get some feedback from the technology that things are set up and then I can invest time actually making sure that it's used correctly

Speaker 2: Yeah.

Speaker 1: Um okay. And thankfully Sage has just provided the template to copy. My styles. css. Um, let's see, how do we do it elsewhere? I guess we want to look at our base site template and make sure that we're going similar enough, right?

Speaker 2: Yep. Oh, manifest.

Speaker 1: I don't know. Apparently. This this irks me. The quotes are

Speaker 2: Yeah, it doesn't Yeah, that's good.

Speaker 1: And uh JavaScript, do we need JavaScript for our block?

Speaker 2: Maybe not

Speaker 1: Oh, see the quotes are right here.

Speaker 2: Yeah, if you don't need it, you can omit the job script. But I guess just to be safe, we can add it for now.

Speaker 1: Yeah. That's the kind of thing I'd like to omit, but uh it might also cause pain further on the line. Um okay it's easier.

Speaker 2: Hello.

Speaker 1: Ooh.

Speaker 2: Oh I guess it's the review values.

Speaker 1: Test, test, test.

Speaker 2: Yeah.

Speaker 1: Expected and block are manifest of course. Do you know where manifest comes from, Sage?

Speaker 2: I don't. I don't think I've heard of it. I thought

Speaker 1: I will be honest. I don't recall why this is set up like that on this project. Oh, it's using the manifest webpack loader, that's

Speaker 2: that's why.

Speaker 1: NC stuff.

Speaker 2: Okay, yeah. By the way, you might not need to reload the page because it's in an iFrame.

Speaker 1: Oh yes, that's true. Looks age.

Speaker 2: Wow, what is that? Why is it like that? Why is it just test?

Speaker 1: What were you expecting?

Speaker 2: Well, where's the I don't know the blue thing?

Speaker 1: I'm guessing this is um That's a lot of tests And the blue thing is indeed missing. I'm gonna guess that's simply enough this block's styles depend on more than what we have in the template at the moment. So we might need um

Speaker 2: oh um it might need the the bug fix that I added in my PR

Speaker 1: Which one?

Speaker 2: I think the div wrapper that has the block dash um block name CSS class.

Speaker 1: I don't know. Um

Speaker 2: or you know, you can always um open it in a U tab.

Speaker 1: Maybe it's something with the screen width that got in the way. So certainly here.

Speaker 2: What if you open the iframe in a U tab?

Speaker 1: Oh, the iframe.

Speaker 2: Yeah.

Speaker 1: So block, block, block, block.

Speaker 2: Their block preview, yep.

Speaker 1: Okay, we need a different block ID then. So that's definitely a feature that is promising but takes quite a bit of um of work to adopt, right?

Speaker 2: Yep Is it one two seven?

Speaker 1: One, two, three, probably is the first one that I do.

Speaker 2: I was thinking of looking at the iframe directly and just look at the SRC type, the attribute.

Speaker 1: What do you mean?

Speaker 2: Um when you open the block picker. Ah, there it is. Uh that

Speaker 1: 's just a screen with thing. Um why does it show twice, Sage? What have I done wrong?

Speaker 2: What does your block premium template look like?

Speaker 1: What does your block producer take look like?

Speaker 2: Oh maybe because you provided both um was it both the page and the URL?

Speaker 1: That is um an option. Let's make it a bit more real. Um teaser content that's so cool. This is such

Speaker 2: Yeah, that's very good copywriting TV.

Speaker 1: Thank you. Hey. Yeah. Um I like that Do you think it's possible for me to use get preview value then and just like you said about images fetching them from the database, would would I be able to um Scour through my whacktail content and find an instance of it like a real one and use that.

Speaker 2: Yeah, we can do that right now

Speaker 1: I feel like it's a bit beyond me, but I'd just like to know if it's possible.

Speaker 2: It is definitely possible. Um yeah, I just so it's sort of providing preview value in your meta class, you can override the get preview value method in the block class. And then you can do your, you know, Django query against the image model, for example, and get, for example, get a random image or like the last image uploaded, maybe

Speaker 1: Oh yeah, yeah. And that's the docs you were hoping to add, right? Like those methods

Speaker 2: that you use. Yeah, and I I'm still not sure where that docs should leave because I don't think we have um like the reference API for stream fields um road link. So yeah. Yes, some of the like documentation for other methods like get template for example they currently live in this very page just a few lines above I think if you look for get template Yeah. So it tells you how to use it and how to override it, but there's no like the reference

Speaker 2: section for that method itself. And I'm not sure what to do.

Speaker 1: So why would there be a reason why you can't add it to the block reference?

Speaker 2: No reason. I was thinking of adding it there. Um, but yeah, currently the get template itself doesn't have Like ideally I'd like it to be like side by side or like next to each other.

Speaker 1: Yeah.

Speaker 2: So maybe I should add that as well.

Speaker 1: I would guess that in the reference it's good to cover as many things as possible and ideally have it be automated when it's an option so you don't have to um think too hard of what to cover or not to cover and then in a how to you can be more intentional about the order in which you cover things so that people are more likely to pick up the patterns that you think work well

Speaker 2: Yeah, I guess um the problem is if you do it automatically uh people might assume that everything is included in the deprecation policy.

Speaker 1: Hmm. Yeah, okay.

Speaker 2: So yeah. Usually we do a combination of both. So we automatically generate the documentation based on the signatures and any doc strings, but we still select what methods we want to document manually. So that we don't accidentally document private methods.

Speaker 1: Got it. Okay. Let's try one more feature. It definitely takes time to try with these candidates. I think I'm really appreciative of people who take the time to do that because it's uh super helpful to us. But I guess, yeah. I guess there's the benefit that then you know you have a better sense of what it will take you to upgrade as well, maybe. Um so yes, streamfield blocks we've covered headless documentation is documentation changes that are super helpful, but Hopefully won't break anything. It's just more docs. Thank you, Saiva and Alex.

Speaker 1: Um text improvements. That'll take quite a bit of time to check out. So let's try the shorthand.

Speaker 2: Yeah, that that'll be quick and simple.

Speaker 1: This is really cool. I have no idea how long Matthew has been working on this and like whether it came from specific discussions or no, but feels like such a win to reduce the syntax a bit.

Speaker 2: Yeah.

Speaker 1: So I think what we want to do here is compare our page editing form before and after switching to this shorthand syntax.

Speaker 2: Well nothing will change, but uh the code will.

Speaker 1: Yep. So that would be um oh yeah, here for example. That'd be neater. Um and we were looking at the blog page. And yeah, so the Oh wow, so many of those fields we could simplify. Interesting to know how he's handled if you don't use this class defaults headings and labels. Let's convert it all, shall we, and see side by side what's happened. No. Yes. Chuck.

Speaker 1: So we said side by side. So I think I can um put another browser window on the same page

Speaker 2: I don't know if Chrome has it, but Microsoft Edge has a split view.

Speaker 1: Split view? Yeah.

Speaker 2: It's very cool.

Speaker 1: Moving over right now. Do you use Microsoft Sage?

Speaker 2: Uh yeah, sometimes. Um not at work for some reason. I think uh just because for my personal stuff I have it synchronized.

Speaker 1: Makes sense? Uh how do you use the split view sage teachers?

Speaker 2: I think if you click on the I'm not sure what that is that the one? Yeah.

Speaker 1: What Wow. Let me take a moment to adjust my screen sharing so we can make the most of this. Okay. So Let's say left will be before and then right will be after. So I assume I can refresh that one without the other refreshing. Yeah, and then we can make the changes and see what happens. Um boom boom boom boom boom boom.

Speaker 2: Look at this ten times engineer.

Speaker 1: Yeah, that's what they do with their Vim mic macros, right?

Speaker 2: You have Vim bindings?

Speaker 1: Honestly, like I've considered picking them up a few times, but um I don't know, I just couldn't um say

Speaker 2: it

Speaker 1: 's to me like ye yeah there are more important things to see my score than typing. I don't know Sage on a daily basis. Do you spend more time writing or typing?

Speaker 2: I spent more time thinking, I think.

Speaker 1: That's a good point. Did it just work? Is it what just happened?

Speaker 2: Did anything change?

Speaker 1: Oh yeah, looks look look at that.

Speaker 2: Oh

Speaker 1: block page related page one. Block page related page two That's a lot of related

Speaker 2: and you can now actually click on it. It's not disabled the add button.

Speaker 1: Yes, because we removed the

Speaker 2: Yeah, yeah. So that changed.

Speaker 1: Well that's really cool. Um yeah, I I think for inline panel uh Uh I feel like quite often you might want to customize the label still.

Speaker 2: Yep.

Speaker 1: But uh the defaults are pretty decent. And so it's called block page related page, I assume because It derives from from that?

Speaker 2: Um there might be uh

Speaker 1: Oh no, hang on, I'm looking at the wrong. Yes. That's why. That makes more sense. So I guess yeah, you could just pick a better class name here if you wanted to trust those defaults. Um yeah, or optimize the UI by using the longhand syntax. Cool. Um Drag and drop, Sage?

Speaker 2: Oh, who worked on that?

Speaker 1: Who worked on that

Speaker 2: Oh, what is that?

Speaker 1: Boom.

Speaker 2: Oh

Speaker 1: Um drag and drop, yeah, that's that warrants its own videos, the coolest. I'll just give leave that that teaser. Search terms report. Do we use the search terms on this website?

Speaker 2: Let's find out.

Speaker 1: Ah, we do

Speaker 2: headless. It's a favorite.

Speaker 1: That's a good one. We do have a page about the headless, but I would assume that it is relatively hard to spots it might not be like in our main menus or anything. That's a really useful feature. I'm really happy we landed this one. And that's um we have it in the release notes. Performance optimizations or stage. You've done lots of this And then there's a plethora. Thanks to your

Speaker 2: audit.

Speaker 1: Yeah. Well there's more to do. There's a plethora of other features which will be worth testing, but not today. I think we've done good today, Sage. Some things work. Some things need improvements.

Speaker 2: Definitely.

Speaker 1: We'll get there.

Speaker 2: Yeah

Speaker 1: That was fun. I hope it encourages a few more people to test our candidates and have fun with us. Maybe we'll do a live version of this at some point. Just go through this with people together.

Speaker 2: Well, that would be fun, yeah.

Speaker 1: I'll think of a date and make it happen. And um yeah, Wachtel 6. 4 due to be released. Let's look at Sage's master calendar.

Speaker 2: Master calendar.

Speaker 1: It is so cool, Sage. I wanna I wanna I want to look at it every day if I can.

Speaker 2: This bunch of bunch of bunch of numbers. It's in the White Tele organization now. Not sure if I linked it here. I think the yeah this uh the one I linked here is still on my account, but if you just um scroll up to the projects tab at the top on GitHub What were you doing? Just scrolling down the discussion. Yeah.

Speaker 1: So we are here in red. And six dot four is due Monday. Not not Not next week, Monday, but the one after. So there's like what ten days left to test it? Do you think we're on schedule to ship on time?

Speaker 2: I think so. Well, unless. Unless. That's why we need your help.

Speaker 1: Yeah, most definitely.

Speaker 2: Yeah.

Speaker 1: Let's do some testing with Django 5. 2 as well. So we see quite important. I don't know if you've seen my message about this, but I assume that since Wagtail 6. 4 is released before Django, we won't formally commit to supporting it, but we probably still will be supporting it anyway.

Speaker 2: Yeah, we'll probably say that it's it has provisional support for it because currently our tests are passing with the uh Django 5. 2 branch So we expect any breaking changes in Django would be treated as regressions and therefore also release blockers. for the 5. 2 release. So by the time the final release of Django 5. 2 is out, it shouldn't have any of those regressions anymore. Ideally. Which is usually what happens. So yeah.

Speaker 1: Maybe we'll add support in the patch release like we done before, considering um There probably won't be any code changes.

Speaker 2: Yeah, and yeah, there there's currently nothing stopping you from installing Django 5. 2 by the time white till 6. 4 comes up because the requirements um yeah we we have the upper boundary for Django set to 6. 0 currently, which we're hoping to remove at some point in the future.

Speaker 1: Are we?

Speaker 2: I think so.

Speaker 1: Aw. I liked the upper boundary.

Speaker 2: Yeah, but

Speaker 1: It's okay, I'll let it go. Let it go. Ooh, look at that I know what I'm doing next after this meeting, say

Speaker 2: you should drop the Django's upper boundary on Django Pattern Library. Why does it mean to have it?

Speaker 1: Because otherwise it just breaks without people noticing.

Speaker 2: Well.

Speaker 1: But yes, it would be neat if it just worked with every future version Django ever

Speaker 2: Which is historically what happens, right? I mean , uh Has there been many changes in Django that broke, yeah?

Speaker 1: Um I think like Three or four to be honest. If I if I screen shared again um this Right here is exactly the type of thing that I wish we didn't ship um the package with. So this is Django introducing a warning when uh a template tag is registered multiple times. Which is um fundamental aspect of how the binary works at the moment. Um

Speaker 2: I was wondering what that what that was about. Yeah.

Speaker 1: Now you know. So I don't know which version of Django introduced that or which configuration changed, but yeah, that's exactly the type of compatibility issue that You know, even if for the sake of the argument, even if there was no code change to do in a library, I think I'd at least want a document in the Really said introduced his support for that version of Django.

Speaker 2: Yeah.

Speaker 1: Oh, now you'll be a warning. Anyway, we'll get there. Thank you, Sage. It was fun.

Speaker 2: Yeah, thank you, Tibor, for actually doing all the testing. I'm just telling you what to do.

Speaker 1: Programming is good.

Speaker 2: Yeah, it is good

Speaker 1: Talk to you soon.

Speaker 2: Alright. See you.