Just Chatting and Clicking Random Links! - CourtneyR.dev's 2nd Brain

Just Chatting and Clicking Random Links! ![rw-book-cover](https://img.youtube.com/vi/xPskuyyIrps/maxresdefault.jpg) 🔗 **Source:** [Just Chatting and Clicking Random Links!](https://www.youtube.com/watch?v=xPskuyyIrps) > [!note]+ Document Notes > tags: [wordpress, gutenberg, php-blocks, live-stream] > author: Ryan (Stream Host) > source: Twitch Stream > reference: https://www.youtube.com/watch?v=xPskuyyIrps > date created: 2024-12-28 16:21 > > # 🏷️ Title: Just chatting and clicking random links! >  ## 🧰 Action Inbox - [H1] Test Gutenberg 22.4 PHP-only blocks functionality — live demo #gutenberg - [H2] Review VS Code Interactivity API extension feedback — extension launched #interactivity-api - [H3] Consider Talk Devi to Me podcast format — community engagement #devrel ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [Gutenberg 22.4 Release](https://make.wordpress.org/core/handbook/) - [VS Code Marketplace Extension](https://marketplace.visualstudio.com/) ## 📝 Summary - Live stream covering Gutenberg 22.4 PHP-only blocks, VS Code extension demo, and community discussion - Why it matters: Shows practical WordPress block development without JavaScript build processes - Key stakeholders: WordPress developers, block creators, community members - Risks and tradeoffs: Documentation gaps between Gutenberg plugin and core WordPress - Bottom line takeaway: PHP-only blocks now functional in Gutenberg 22.4, new developer tools available ## 📖 Main Content Ryan demonstrates the newly functional PHP-only block registration in Gutenberg 22.4, showing how developers can create blocks using only PHP without JavaScript build processes. He showcases his new VS Code extension for Interactivity API development, discusses documentation challenges in the WordPress ecosystem, and engages with community members about various development topics. The session covers technical implementation details, community feedback on block proliferation, and practical developer tools. Notable is the discussion about Block Editor Handbook documentation being auto-generated from trunk rather than stable releases, causing confusion for developers. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/xPskuyyIrps?t=0) — [H1] Stream introduction and snow day delays - Key idea: Stream nearly cancelled due to heavy snowfall requiring extensive driveway clearing - Evidence: "I woke up to 800 feet of snow in my driveway... took an hour and a half" #### ⏱️ [02:15](https://youtu.be/xPskuyyIrps?t=135) — [H2] Flappy Gate incident recap - Key idea: Previous stream's malicious link incident opened 96 popup windows with inappropriate content - Evidence: "I clicked the link and then... it had opened 96 popup windows and they were all bouncing" #### ⏱️ [08:30](https://youtu.be/xPskuyyIrps?t=510) — [H1] Gutenberg 22.4 PHP-only blocks demonstration - Key idea: New Gutenberg version enables PHP-only block registration without JavaScript - Evidence: "22.4 came out... now we can get these things happening which is really cool" #### ⏱️ [12:45](https://youtu.be/xPskuyyIrps?t=765) — [H2] PHP block attributes and meta fields - Key idea: Block attributes automatically create meta fields based on type definitions - Evidence: "attributes based on the type string, integer, boolean, string and this enum. It was creating meta fields for us" #### ⏱️ [18:20](https://youtu.be/xPskuyyIrps?t=1100) — [H2] Script and style registration in PHP blocks - Key idea: Can register CSS and JavaScript directly in block registration without separate enqueue actions - Evidence: "I don't think we necessarily need to put it on the actions that you would normally encue" #### ⏱️ [25:15](https://youtu.be/xPskuyyIrps?t=1515) — [H1] Icon block development progress with data views - Key idea: Icon block now uses WordPress data views component for improved modal interface - Evidence: "I'm using data views for it. So now when you load this now we have this going on" #### ⏱️ [32:40](https://youtu.be/xPskuyyIrps?t=1960) — [H2] Documentation challenges discussion - Key idea: Block Editor Handbook auto-generates from trunk, creating confusion about feature availability - Evidence: "documentation that represents things that are not in core and that are not in the released version" #### ⏱️ [41:10](https://youtu.be/xPskuyyIrps?t=2470) — [H3] Block proliferation and enterprise concerns - Key idea: Better to disable unneeded blocks than build missing ones for client projects - Evidence: "it's better to have to disable a block than it is to have to build one" #### ⏱️ [46:30](https://youtu.be/xPskuyyIrps?t=2790) — [H1] VS Code Interactivity API extension demo - Key idea: New extension provides autocomplete for WordPress Interactivity API directives and state - Evidence: "when I hit state, I get prompted with the items from the state" #### ⏱️ [52:15](https://youtu.be/xPskuyyIrps?t=3135) — [H2] Extension features walkthrough - Key idea: Extension validates store names, detects duplicates, and parses view.js files - Evidence: "it'll actually tell you, hey, there's no store name dev inspector" #### ⏱️ [58:45](https://youtu.be/xPskuyyIrps?t=3525) — [H3] Talk Devi to Me podcast concept - Key idea: Proposed stream format for developers to showcase their projects - Evidence: "people are going to come on and we're going to talk about the thing they're building" #### ⏱️ [63:20](https://youtu.be/xPskuyyIrps?t=3800) — [H2] AI development tools discussion - Key idea: Used Claude and Nano Banana to build VS Code extension in two days - Evidence: "I built this with Claude Code in like two days and I'm super excited with it" #### ⏱️ [68:40](https://youtu.be/xPskuyyIrps?t=4120) — [H2] Community member Paul joins discussion - Key idea: Real-time collaboration on PHP Storm extension conversion and WordPress core contributions - Evidence: "Paul wants in... you're going to take that thing that I did and you're going to get AI to convert it" ## 📚 References - [Gutenberg Plugin](https://wordpress.org/plugins/gutenberg/) - [WordPress Developer Handbook](https://developer.wordpress.org/) - [VS Code Marketplace](https://marketplace.visualstudio.com/) - [WordPress Interactivity API](https://make.wordpress.org/core/2024/03/04/interactivity-api-dev-note/) ## 🗣️ Paraphrase - Gutenberg 22.4 enables complete PHP-only block development without JavaScript build processes, making WordPress block creation more accessible - Documentation challenges arise from auto-generation based on development trunk rather than stable releases, causing confusion about feature availability - New developer tools like VS Code extensions can significantly improve WordPress Interactivity API adoption through better autocomplete and validation ## 📰 Newsletter 🎉 **PHP-Only Blocks Now Live in Gutenberg 22.4!** Great news for WordPress developers who prefer server-side block development! The latest Gutenberg plugin update makes PHP-only blocks fully functional. You can now register blocks with attributes, styles, and scripts entirely in PHP without touching JavaScript build processes. This is a game-changer for developers who want to create custom blocks but don't want the complexity of modern JS tooling. Simply define your block attributes, and WordPress automatically creates the corresponding meta fields. **New Developer Tool Alert:** Check out the new VS Code extension for WordPress Interactivity API development, featuring intelligent autocomplete for directives and state management. **Resources:** - [Learn WordPress](https://learn.wordpress.org/) - Official training platform - [Developer Docs](https://developer.wordpress.org/) - Technical documentation - [WP-CLI](https://wp-cli.org/) - Command line interface Join the conversation in WordPress community Discords and forums to share your PHP-only block experiments! ## ✅ Action Items #### DevRel - Community engagement: Host "Talk Devi to Me" developer showcase streams - Education: Create tutorials for PHP-only block development workflow - Developer experience: Address documentation gaps between Gutenberg plugin and core - Developer marketing: Promote new VS Code extension for Interactivity API - Community management: Moderate stream chat with improved link filtering #### WordPress - Core: Validate PHP-only blocks functionality across WordPress versions - Documentation: Consider versioned docs to separate trunk from stable releases - Community: Support developers transitioning from JavaScript to PHP-only workflows - Plugins: Review extension approval process for developer productivity tools - Design: Improve data views component integration in block interfaces #### Community - Maintainers: Gather feedback on PHP-only blocks implementation - Contributors: Test new development workflows and report issues - Sponsors: Support developer tool creation and maintenance - Ecosystem: Document best practices for PHP-only block patterns ## 🧪 Hypotheses - PHP-only blocks will increase WordPress block development adoption among backend-focused developers - VS Code extensions can significantly reduce Interactivity API learning curve through better developer experience - Documentation generated from trunk rather than stable releases creates unnecessary developer friction - Community-driven developer tools fill important gaps in official WordPress tooling ### 📊 Methodology - Survey developers about PHP-only blocks adoption rates before and after 22.4 - Track VS Code extension downloads and user feedback metrics - Analyze documentation-related support requests and their resolution patterns - Monitor community Discord discussions for common development pain points ### ❓ Questions - Will PHP-only blocks reduce JavaScript build tooling complexity concerns for new developers? - How can WordPress core better communicate feature availability across plugin and core versions? - What additional developer experience improvements would accelerate Interactivity API adoption? ### 🔮 Future Research - PHP-only blocks performance compared to JavaScript-built blocks - Developer productivity gains from specialized WordPress extensions - Community-driven vs official tooling effectiveness in WordPress ecosystem ### 💡 Implications - Practice: Simplified block development workflows may increase community contributions - Policy: Documentation versioning strategies need reconsideration for developer clarity - Education: Developer onboarding paths can focus more on PHP skills initially - Funding: Community tool development deserves support alongside core WordPress funding ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade (technical developer content) #### 👀 Visual learners - Present: Live screen sharing, code demonstrations, extension interface tours - Improve: Architectural diagrams for PHP-only blocks, data flow visualizations #### 🔊 Aural learners - Present: Live stream format with verbal explanations and community discussion - Improve: Recorded tutorials, podcast format for complex topics #### 🗣️ Verbal learners - Present: Interactive chat, technical terminology explanation, analogies - Improve: Glossary of WordPress-specific terms, comparison tables #### 🧩 Kinesthetic learners - Present: Live coding demonstrations, step-by-step implementation - Improve: Downloadable code samples, hands-on workshops #### 🧠 Logical learners - Present: Sequential development process, cause-and-effect relationships - Improve: Decision trees for block development approaches, performance comparisons #### 🧑‍🤝‍🧑 Social learners - Present: Live chat interaction, community Discord integration - Improve: Collaborative coding sessions, peer code reviews #### 🧘‍♀️ Solitary learners - Present: Individual coding time, personal project development - Improve: Self-paced tutorials, documentation deep-dives #### 🌿 Naturalistic learners - Present: Real-world problem solving, organic community conversations - Improve: Case studies from actual WordPress sites, ecosystem impact analysis ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Live stream with verbal descriptions of visual elements - Improve: Alt text for shared code screenshots, structured heading hierarchy #### Keyboard navigation - Present: Demonstrated VS Code keyboard shortcuts and workflows - Improve: Document keyboard-only development workflows #### Contrast and readability - Present: High contrast code editor themes during demonstrations - Improve: Verify code example visibility across different displays #### Media and captions - Present: Live stream with audio commentary - Improve: Auto-generated captions, post-stream transcriptions available #### Standards reference - Follows WCAG 2.2 AA guidelines for live streaming accessibility ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global community participation through chat and Discord - Improve: Acknowledge different time zones for stream scheduling #### Inclusive language - Present: Gender-neutral technical terminology, welcoming tone - Improve: Define technical jargon consistently, avoid cultural idioms #### Neurodiversity support - Present: Multiple communication channels (audio, chat, visual) - Improve: Provide agenda/outline for streams, consistent structure #### Representation - Present: Diverse community member participation and recognition - Improve: Highlight contributors from different backgrounds and experience levels #### Psychological safety - Present: Respectful handling of technical mistakes, learning-focused environment - Improve: Clear community guidelines, escalation paths for issues ### ✅ Logical Validity #### Strong reasoning - Deductive strength: PHP-only blocks reduce complexity → increased adoption (valid premise, sound conclusion) - Inductive strength: Documentation confusion examples → systemic issue (multiple data points support generalization) - Causal reasoning: Gutenberg 22.4 release → PHP-only blocks functionality (direct causation established) - Analogical strength: VS Code extension success → PHP Storm extension potential (reasonable parallel) #### Fallacies - Appeal to authority: "It's better to have it and not need it" - presented as universal truth without context - Hasty generalization: Documentation issues from single experience - needs broader data #### Tone of voice - Overall tone: Enthusiastic and community-focused with technical expertise, occasional casual humor ### 🛡️ DARVO Analysis - Deny: No denial patterns present in technical discussion - Attack: No attacks on accusers - collaborative problem-solving approach - Reverse victim/offender: Not applicable to technical content - Emotional cues and rhetoric: Positive enthusiasm about community contributions and technical progress ## 🎯 Conclusion - Gutenberg 22.4's PHP-only blocks represent a significant accessibility improvement for WordPress block development - Community-driven developer tools like the Interactivity API extension demonstrate the value of grassroots innovation - Documentation challenges between plugin and core versions need systematic solutions for better developer experience ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] PHP-only blocks enable server-side WordPress development > [!quote] [Just chatting and clicking random links!](https://www.youtube.com/watch?v=xPskuyyIrps) by [[Ryan]] via [[Twitch Stream]]. Published 2024-12-28. Accessed 2024-12-28. > "22.4 came out... now we can get these things happening which is really cool" Gutenberg 22.4 enables complete block development without JavaScript build processes. [view highlight](https://youtu.be/xPskuyyIrps?t=510#H1) #gutenberg #php-blocks ID:rw_001 ### [H2] Documentation auto-generation creates developer confusion > [!quote] [Just chatting and clicking random links!](https://www.youtube.com/watch?v=xPskuyyIrps) > "documentation that represents things that are not --- ## Full Transcript [03:48] Hello everybody. Microphone. Microphone. [03:51] Ryan. Need the microphone. Hello [03:52] everybody. [03:54] How's it going today? Hey Paul. Hello. [03:57] Hello Paul. Paul. Hello. [04:01] Um [04:05] yeah. Cool. Hi. How's it going today? [04:07] I'm all over the place. I woke up to 800 [04:10] feet of snow in my driveway. Um, so I've [04:13] been shoveling and snowb blowing the [04:15] snow all morning. Took an hour and a [04:16] half to get our our driveway done. It [04:18] was ridiculous. And it's snowing heavily [04:19] right there now. Uh, yes, you did miss [04:22] the fun last week, Paul. Um, I have [04:24] scrubbed it from the internet, [04:27] but um there's there's a couple of [04:29] shorts up there that that sort of uh um [04:33] had to turn off all your content [04:35] filters. [04:38] Ah, it's going to be one of those. I'm [04:40] never going to live this down. If I [04:42] could ever find my mouse, [04:46] >> that [04:50] that might be the best comment so far. [04:53] Hello from YouTube. I'm sorry I cannot [04:57] pronounce say your username. Um, but hi [05:00] and welcome to the stream. We're over [05:02] here in Twitch hanging out. [05:05] Um, I barely made it into stream today. [05:07] Like I was saying, I had a ton of snow [05:09] out there. My my neighbor uh whose snowb [05:10] blower broke yesterday, I had to go help [05:12] her and her daughter dig out. Uh, too [05:15] too bad. What was the link? Kevin. [05:19] >> Kevin. [05:20] >> Kevin. [05:22] Oh, it was [05:27] >> Kev XB. Um, it was it was it was quite [05:31] the link. I'm sure someone will show up [05:33] in chat and drop it. Uh, but that was it [05:36] was like the most I'll never trust the [05:39] link. In fact, after that I I I changed [05:42] my settings so I don't think anybody can [05:43] drop links in chat [05:46] because I I don't trust myself. [05:49] It was Kevin. [05:52] It was the most intense experience ever. [05:56] I clicked the link and then there was [05:58] like this thing as oh it's a Flappy [05:59] Warrior clone. clicked it and then n [06:01] Okay, so I was scrubbing my computer [06:03] with bleach and uh I I found it had [06:06] opened 96 popup windows and they were [06:09] all bouncing and moving and I and I [06:11] realized that that you guys probably [06:13] didn't hear this because I I don't think [06:14] I had the uh my browser routed in the [06:18] audio, but all the stuff that was being [06:21] shown there was screaming audio so loud [06:24] and so like my reaction was was instant [06:27] fear. I peed a little. It was horrible. [06:29] Uh, and it also downloaded a bunch of [06:31] images to my downloads folder that I'm [06:33] like, you know, [06:36] would never ever want on my computer [06:38] ever. So, yeah, it was uh I they got me. [06:41] They got me. They got me. Anyhow, but [06:45] that's not why that's not why I'm here [06:48] today. [06:52] Oh, [06:53] I think I I've been streaming now for [06:55] about four years. I'm going on five [06:57] years. And uh that's the first time it's [06:59] ever happened. So knock wood. That'll be [07:01] the last time it's it's ever happened. [07:02] It ever happens. Oh, but uh so I don't [07:05] have a lot going on today. Um I am [07:06] looking for there was a new version of [07:08] Gutenberg released which is very cool. [07:10] 22 22.4 came out. So I wanted to see um [07:15] if our PHP only block stuff. Um if you [07:19] remember last week before [07:22] Oh, we got to come up with a flappy bird [07:24] gate. Flappy gate. Let's call it flappy [07:26] gate. We we we we need a name for the [07:28] thing that happened. Um so throw some [07:32] names. You know what? Let's do a poll. [07:34] Actually, throw some names in chat and [07:36] and we'll come up with it. And I'm I'm [07:38] going to do like some emotes and stuff [07:40] and I'm going to really milk this for [07:42] all it's worth. [07:44] And if you haven't seen the short that I [07:47] put together on it, please go look at it [07:49] because I'm very proud of it. I think [07:51] it's very funny. Um, [07:55] let me see if I can find it here. Um, [07:58] it's like a little movie. It's like a [08:00] little movie. Can you guys hear that? [08:02] You guys can't hear that, can I? [08:06] Hold on. Hold on. Hold on. I might have [08:09] to turn on standby. Hold on. We're going [08:12] to show this. Where's my loop back? [08:14] There it is. So, we're going to put [08:15] Chrome on. I'm going to just pause my [08:17] music real quick. And then we're gonna [08:20] >> TypeScript type. [08:21] >> Do I want to click this link? [08:24] >> Oh my god. [08:27] >> Now, somebody way back way back in in [08:30] chat asked me to look at a a a game. I [08:34] got flapped. Who was it? Oh, new bird [08:36] game net. Okay. Stove 423. Are you still [08:38] in chat? Store 423. I don't see you. [08:43] Do I want to click this link? [08:46] Oh, it's Flappy Bird. [08:49] Oh my god. Oh my god. [08:54] >> Do I want to click this link? There we [08:56] go. That's my art. Oh my god. [08:58] >> My art movie. Ah, lost the mouse. Get [09:00] out of here. [09:01] >> That was it. So, yes, I think that's [09:05] that was that was funny. Anyhow, doesn't [09:07] matter. Okay, so what are we doing here [09:10] now? All right, right. Okay, so let's go [09:12] back into my old posts and let's see [09:14] what Okay, so this is my PHP only block. [09:16] So I kind of forget what we were doing [09:17] there. So let's take a look. So the [09:19] block is loading. Okay. So So if we [09:24] remember, let's look. Uh I got to jump [09:26] back over to [09:28] Is it in here? [09:31] I do this every time. I have to go to uh [09:35] to here. I got to go Twitch stream. I [09:37] got to go to VS Code and Okay, here we [09:39] go. So here's our our content only [09:41] block, right? So all we're doing is [09:43] registering of our our blocks directly [09:45] with register block type uh with a [09:48] namespace and then we're adding all of [09:49] these things and so the thing that why [09:51] is this being stupid? How it expected [09:55] six one two three four five six [10:01] one two three four five six now it's [10:04] okay. [10:11] Oh my lordy lordy. Right. Okay. So, [10:15] let's [10:20] anyways. Uh, [10:24] if only somebody could come up with a [10:26] way to format this for me automatically [10:28] so I didn't do this. I'm sure it's [10:30] possible. [10:34] Why is there a period in there? It needs [10:36] to go away. All right. Anyways, uh, I [10:38] have to screw down. So what we were [10:40] doing is we were defining our attributes [10:41] in here and the attributes based on the [10:43] type string, integer, boolean, string [10:46] and this enum. It was creating uh meta [10:49] fields for us. So if if you remember [10:52] last week uh uh 22.3 was still the [10:56] active version of Gutenberg and so now [10:58] we've we we got 22.4 active. It just [11:01] just came out. And so now this PHP only [11:03] blocks thing [11:05] uh now we can we can get these things [11:08] happening which is really cool. So this [11:09] is this is kind of fairly complete like [11:14] fairly complete. I think I think we're [11:16] in a position now where you just install [11:19] the Gutenberg plugin and you're able to [11:21] do PHP only blocks. So um that's super [11:25] powerful. Super powerful. And we also [11:27] discovered that you can still in in quue [11:29] JavaScript [11:31] and add handles and stuff. So what I was [11:33] actually thinking about this was [11:37] I was in queuing I was using I was [11:39] putting this on on the actions that you [11:42] would normally put them on. But I don't [11:44] know if you if you need to do that. I [11:46] think we can just register [11:48] styles like what if we just did this. I [11:50] want to try something here. Going to [11:52] register my styles in the same place [11:54] where I'm registering the block, right? [12:02] Hey. [12:07] Oh, man. It's such a good song. Uh, [12:10] great to see you. Also, [12:13] let's see if this works. So, I I've [12:15] taken out the Oh, I need to get that. [12:18] No, I need to get that CSS file. So, [12:20] we're going to see. So this should be [12:23] registering some CSS [12:26] for us and a script and the script [12:30] is what's okay. So what test CSS what [12:33] does it do? It makes the title big and [12:37] this just alerts something I think. [12:40] What is all this crap? [12:47] Weird. Okay, we're gonna Oh, I know what [12:50] I what I did there. I'm going to do [12:51] that. So what I just want to I want to I [12:53] want it to alert. Hi with two I's and [12:57] two J. Sure. Why not? Why not? You know [12:59] why not? And now we shouldn't have to [13:01] build anything. [13:03] Oh, okay. So that worked. [13:06] That worked multiple times and it's [13:09] doing that. So let's see. So where did I [13:13] So script handles styles handles. [13:19] Oh, I get it. So the script script [13:20] handles. So, [13:22] these are getting loaded on both. That's [13:26] cool. All right. And this one, what is [13:28] this one? What's the editor? So, editor. [13:31] Um, I should be able to do the same [13:33] thing, [13:35] right, with the editor. I should be able [13:36] just to drop it in here. Um, the reason [13:39] I'm doing this is because I don't think [13:41] we necessarily need to, um, you know, [13:44] put it on on on the actions that you [13:46] would normally encue the actions on [13:48] because we're just registering the [13:49] script. And so because the point of it [13:53] is you register these scripts and then [13:55] you can you could define script handles [13:57] and styles and whatnot for for editor [14:00] and for the uh front end with these [14:03] arrays. So you could still get your CSS, [14:07] you can still get your JavaScript into a [14:09] a PHP only block. I think that's pretty [14:11] powerful. Let's just make let's make [14:13] sure it works though. [14:17] We know that works. We know that works. [14:20] It's loading twice though, which I don't [14:21] like. Am I doing it twice? [14:28] That's a good question. Um, that's a [14:30] really good good question. I mean, the [14:32] way that these work is that [14:35] this should only be per block, I would [14:38] imagine. Let's check. Let's take this [14:40] out. Save. [14:43] We'll refresh. [14:46] Uhoh. [14:49] Huh? [14:51] Wonder why? [14:53] Why? Oh. Oh, that makes sense because [14:56] the block is actually being loaded. It's [14:58] just not in there. Okay. Okay. So, let's [15:02] let's put the block back. Can I undo [15:04] what? Custom. [15:07] Uh, what is the name of the block? Crap. [15:11] Yeah, that's that's annoying. Okay, [15:14] that's annoying. [15:16] Okay, screw off. [15:18] That needs to go away. Okay, so we know [15:20] that that works. So, what was the name [15:22] of this block? That's the thing. Twitch [15:23] something or other. Let's find out. We [15:26] called it my custom title. Okay, so [15:27] we're going to do my custom title. So, [15:31] we're going to put that in. So, that's [15:32] getting the CSS there. [15:37] >> It is Troy Shaplin. Okay. So, that's [15:40] getting the CSS. And so now let's put [15:42] this [15:44] let's put this back. [15:47] And that's that and that's loading that [15:49] there. So that does only load on the [15:51] front end. So if I get rid of this and I [15:53] save this and I refresh this. Okay. So [15:57] the JavaScript does is not being loaded [15:59] on on the front end. Um [16:02] which is good. So uh let's see let's [16:05] check the sources too because we can see [16:07] where the sources are. Uh just ignore [16:10] that. I don't know what that is. [16:13] Let's look for sources. Let's look for [16:14] page. Let's look for blocks. Page only [16:17] blocks. [16:19] Um, [16:20] so I I don't see any scripts being [16:25] loaded because the block's not there. So [16:27] I So yes, I know I what? No, no, no, I [16:31] didn't. It's right there. It should be [16:33] alerting. Um, [16:38] what error am I getting? [16:42] weird. Okay. But if we put it back, if I [16:45] put that block back in and I save it and [16:47] I refresh this, I should get that that [16:50] popup. Yeah, I do. Okay. So, now if we [16:51] look at the sources, you can Where are [16:53] the s be content plugins? I was looking [16:56] in the wrong place. Assets. So, we're [16:58] getting JavaScript. Yep. We're getting [17:00] CSS. Yep. Let's take it out again. Save [17:05] it. [17:07] Refresh. [17:10] page content. Okay. No, so it does not [17:14] get loaded on the front end. Um, [17:17] regardless of where you're registering [17:19] it. That's pretty nice. So, yeah, [17:21] because we're not actually in quueing it [17:23] in our in like this code is not incuing [17:25] anything. All this is doing is this is [17:27] registering those. So then once we have [17:29] those those uh those those slugs or [17:32] whatever we're calling them, um you just [17:34] pass them in here and then and then bing [17:37] bong bang, you've got uh porn in your [17:40] chat. That that's that that's a new [17:44] saying that I'm going to start coming [17:45] out with. Um that's like, you know, [17:48] Bob's your uncle, Robert's your father's [17:50] brother. Bang, you got porn in your [17:51] chat. Same thing. See, you like it. I [17:53] love it. Let's do it. [17:56] Um, blast nastier. [17:59] Hello from Portland. Uh, hello from [18:02] Canada, Ontario, Canada. Um, glad you [18:06] could join. Thanks so much for hanging [18:08] out with us today. Are you first time [18:10] chatter? You are first- time chatter. [18:11] Nice. Well, thank you for the chat and [18:14] uh, welcome. Welcome aboard. Welcome [18:17] aboard. Okay, so that's pretty cool. So, [18:19] go and download Gutenberg 22.4 before [18:21] came out I think on Tuesday and now you [18:23] can do blocks is cross keys here. He's [18:25] going to love all this. Um he's going to [18:29] love all this. Uh you know I you know [18:31] what I didn't do? I didn't announce my [18:32] my stream anywhere. I'm going to do [18:35] that. Just going to open up Discord [18:39] and drop some some links in there [18:46] because you know why not? Why not? [18:48] Really? Why not? [19:09] Uh, [19:10] do I have do I have I have this open? [19:12] Yeah. Outreach. So, um, yeah. So, the [19:15] other there's there are something else I [19:17] I I wanted to there's a couple more [19:19] things I I Yeah, I just don't click any [19:20] links. Exactly. Couple more things I [19:23] wanted to uh just chat about today. And [19:27] what were they? Um [19:30] Oh, uh [19:32] oh crap. I had I had all these great [19:34] ideas. New version of Gutenberg came [19:36] out. I think I don't know where the post [19:38] is. I can't find it. Um because that [19:42] that would be good to have. Let me just [19:44] see. Boom. [19:46] Oh, it's it's still in review. Okay. [19:49] It's not quite [19:51] uh [19:53] it's in review. [19:56] Okay. So, it's not quite ready to go. [19:58] So, like every every time that there's a [20:00] version of Gutenberg that comes out, [20:01] there is also a corresponding uh what's [20:03] new in Gutenberg link. Um and uh yes, I [20:07] wanted to uh [20:11] Oh. [20:29] Oh my god. I can't type. Sorry. It's no. [20:31] Okay, cool. Um, right. So, that's that. [20:34] I think I I just messaged Cross Keys [20:36] because he's literally talking about [20:37] this in one of the Discord chats about [20:39] like, "Has anyone done this?" Uh, cool. [20:42] But the other thing is, what is the [20:45] other thing? [20:47] Uh, okay. It's not in there. It's not [20:49] there. It's not there. It's not in [20:49] there. Ply box plug in Gutenber. Oh, [20:52] great. Okay. So, I've been working on [20:54] the icon block again. And I'm super [20:57] excited about the uh about the work that [20:59] we've sort of um uh been able to to to [21:03] get done. So, I I I want to kind of show [21:05] you y'all the some of the um uh some of [21:10] the work. So, uh, the icon block now has [21:14] width and height settings, which is [21:15] super nice because those were merged [21:17] into core. So, I'm I'm using those. Um, [21:20] the other thing now is is I've made some [21:23] changes to the modal. So, the modal that [21:26] that that was in Nyx plugin, which is [21:28] great, was custom. Um, [21:32] oh my god, it's been a week already. [21:33] Yes, it has. Um, so it's been it's been [21:36] custom. It was a custom once, but I'm [21:38] using data views for it. So now when [21:40] when you when you load this now we have [21:42] this going on and I'm super excited [21:45] about this. This is so cool. So um you [21:48] you can sort you can do all kinds of [21:50] things. We can show number you know all [21:52] these things. We can hide certain stuff. [21:54] Um so it's very much a work in progress [21:56] but we're getting so much closer. And [21:59] there's an API for icons that is being [22:02] worked on uh sim simultaneously which is [22:06] a word that I didn't say properly. But [22:09] if we look at my uh my my poll requests [22:13] my poll requests for here the icon block [22:16] I can link to the other one [22:22] right here. You can see where this is [22:24] going. So th this is the work that's [22:27] being done on the uh [22:31] oh I don't know who who [22:36] yeah seems like only yesterday I was [22:38] checking out that link. So this so go [22:40] check out this. So this is going to be [22:42] this is the work that's been done on the [22:44] um on the what you call it the the the [22:46] icon API the ability to register icons. [22:50] So, what that meant for me with the icon [22:52] block is that meant that things got a [22:54] lot simpler because Nyx block does a lot [22:57] of really or did a lot of really cool [22:59] things. Uh, it allowed you to upload [23:01] SVGs. It allowed you to copy and paste [23:04] SVGs, but because we have this API [23:06] coming um and they're very much these [23:08] are very much connected at the hip. So, [23:10] if the API [23:12] doesn't make it to 7.0, this doesn't [23:15] need to be there. Um, then this block [23:18] won't make it to 7.0 0 either, but um [23:21] we're working hard on it. So, it means [23:24] So, anyway, so what it means is that we [23:25] I can remove all that stuff. So, we're [23:27] not going to have the ability to copy [23:28] and paste SVGs. We're not going to have [23:29] the ability to upload SVGs because that [23:32] was always going to be a sticking point [23:34] always because SVGs and core have always [23:36] been a problem because they're very hard [23:38] to validate and they're very easily [23:41] manipulated and they could be attack [23:43] vectors for um hackers and all sorts of [23:46] fun stuff. So, so having core enabled [23:49] that is probably going to be a problem. [23:50] But anyway, so it mean meant that I can [23:53] strip out a ton of code. Uh, yeah. And [23:55] so I I I've been focusing on on this [23:57] thing, which I think is great. It's [23:59] going to be so much fun. It's my first [24:00] real foray foray into data views. Here's [24:03] my tangent interrupting for the stream. [24:04] Okay, bring it. Bring it on. Cross keys. [24:08] Um I I I I wanted to mention but just [24:12] before you you came on we actually had [24:15] um [24:16] 22.4 uh Gutenberg uh came out. [24:22] Uh and so now now all of these all these [24:25] attributes that we were doing before now [24:28] work now now they register the blocks. [24:30] So okay so here here is the question. [24:33] Hey Mr. Gutenberg. Oh my god. Are you [24:35] calling me Mr. Gutenberg? That's [24:38] hilarious. Um, [24:41] you can Well, you can bother anybody. Do [24:45] you have an issue? [24:50] Yes. Yes. There is a really great post [24:52] about about the data view on on on the [24:54] developer blog. I believe it's the the [24:56] developer blog. You can check this out [24:57] right here. Yeah, it just came out. It's [24:59] really great. Go check that out. One [25:01] thing that I found very confusing about [25:04] it was there's a lot of moving parts. [25:06] Um, [25:08] there's a lot of move moving parts with [25:09] this, but once you kind of wrap your [25:10] head around how the pieces fit together, [25:12] it's it's super powerful. [25:15] Yeah, the Goodword Docs already merged [25:17] to the core block editor handbook. Yes, [25:19] there are. That is a correct statement. [25:23] So, if you want to make changes to the [25:26] docs for the block editor handbook, you [25:28] you would do Hey, Mr. Hey, [25:31] Mr. Gutenberg, I need a I need a shirt [25:34] or something that says that. Um, [25:40] hey Philipe, how you doing? [25:43] Um, [25:46] okay. There's a number of things going [25:47] on right here, but I'll answer questions [25:49] as I can. The other thing, all right, [25:52] somewhere there's a person trying to out [25:54] block it or losing his mind because he's [25:55] trying to use the autoregister key and [25:56] it's both doing nothing and throwing no [25:58] errors. Oh, that's what you're saying. [26:00] Okay. First of all, I feel your pain. [26:04] 100% feel your pain. The the the the the [26:09] one one issue that has always been an [26:11] issue with the block editor handbook is [26:13] because it's merged because when things [26:16] are merged, it autogenerates every time [26:19] something's merged in into trunk, you [26:21] get into a position where you have [26:23] documentation that represents things [26:25] that are not in core and that are not in [26:27] the released version of the plug-in, [26:30] right? And it is very frustrating [26:34] 100%. I I get it. Um [26:39] we have discussed a number of things [26:41] about how to how to make that happen. [26:44] The the problem that we run into is it's [26:48] a maintainability issue and this is an [26:50] excuse not a reason 100%. So we had [26:54] talked about having things so [26:56] yes so they get built on merge to trunk [27:03] which is a thing we've talked at length [27:06] my my team internally um when I first [27:09] joined and we really yeah well I mean [27:13] yes it's just the way it is just the way [27:14] it's set up right now doesn't mean it's [27:16] right doesn't mean it can't change but [27:18] it but I wanted to explain it so when I [27:20] merge anything when when But when [27:22] something gets merged to to to trunk in [27:25] Gutenberg within 15 minutes there's a [27:27] cron that runs and it it it builds out [27:30] all the documentation. A lot of that [27:31] documentation is also autogenerated [27:33] based on the source code. So um it's not [27:36] something that's just managed where you [27:38] just go in and you make a change to uh [27:40] to a page. So like if we look at [27:42] Gutenberg [27:44] um uh do I have that open? I don't where [27:47] is it? Gutenberg development. So if we [27:50] look at Gutenberg development here and [27:53] we take a look at let's take a look at [27:55] the docs. So for example docs, right? So [27:59] we're going to have let's use reference [28:01] guides. No, let's go. [28:06] I can never find it. The thing that I'm [28:08] looking for getting started. Oh, I I [28:11] know how it works. Okay, let me go to [28:13] packages. Let me go to Let's go to um [28:17] whatever the block editor. Going to read [28:18] me. So in the read me somewhere down [28:22] here. Why does it look like that? [28:25] Okay. Why does it look like this? [28:28] Something screwed up. Oh, there we go. [28:30] Okay. So, when you see this, what this [28:33] is doing is this is autogenerated by [28:35] this tool that that's called [28:42] Okay, I'll get to your question in a [28:43] second, cross keys, because it's [28:44] nuanced, but yes. So when you see this, [28:47] anything below this line is [28:49] automatically generated by this docgen [28:51] tool. So it takes all the the [28:53] documentation [28:54] and pulls out um so let's see what's [28:58] this function that we're looking at [28:59] block canvas. You know what this let me [29:02] do a better one maybe the core core data [29:05] that might be a better one. So if we [29:07] look in core data you can see that there [29:09] is all these uh some point you'll see [29:12] there so you'll see these add entities. [29:14] So this is an action right and then it [29:16] pulls out all so delete entity record it [29:19] pulls out all the parameters from the [29:20] actual doc block itself. So this is all [29:23] dynamically generated which makes it [29:25] difficult to be able to differentiate [29:27] between core Gutenberg and and in [29:30] development from a from a documentation [29:34] uh point of view. [29:36] Um so to answer Kusky's question [29:41] uh to answer this question why is good [29:43] work and good Gutenberg affecting the [29:44] block edit ed editor docs they should be [29:46] sovereign code braces that you merge [29:48] periodically um [29:51] the block editor handbook is basically [29:53] Gutenberg it's basically all the stuff [29:56] that gets introduced via Gutenberg 2 [29:58] core let's put it that way so I do agree [30:00] with you what what would be really great [30:02] is if we had the ability to toggle [30:05] between um variations of the of the [30:09] documentation. So when Gutenberg or [30:13] sorry when a new version of core is [30:14] released um then we have the docs are [30:18] built from that tag right so so 6.9 [30:23] would would build out the docs that [30:25] would be everything that's inside of of [30:27] core then when there's a new version of [30:29] Gutenberg released every two weeks we [30:31] would build off of that that release or [30:34] that tag or however that's done and then [30:36] we could have one from trunk so you'd [30:38] have essentially three versions of the [30:40] documentation, what's in core, what's in [30:41] Gutenberg, the plug-in, and what's being [30:44] worked on. Um, because I have also run [30:47] into the problem that you've run into. [30:49] I've I it's bit me when I was at Tenup. [30:51] There was this thing called render [30:52] appender for the um innerblocks [30:56] uh component that was in the docs and it [30:58] just didn't work and I couldn't figure [30:59] out why it didn't work and it was [31:00] because it was in it wasn't even in the [31:03] plug-in at the time. It had just been [31:05] merged. So, it's very frustrating. I [31:06] feel your pain. It is something that the [31:08] project has to figure out. And it's it's [31:11] there's there's technical solutions to [31:13] this. It's just a matter of like [31:16] figuring out how it's displayed and how [31:18] it works and getting someone to be like, [31:20] "Yeah, let's change this entirely and [31:22] see how much we can we we can break it." [31:24] So anyways, that's my reason. It's not [31:27] an excuse, but that is that's the the [31:29] history. [31:34] Yeah, you can totally do it. So also [31:37] explains why some of the doc contra each [31:38] other or don't acknowledge parallel [31:39] methods. Yeah. Yeah. [31:46] Yeah. So like like there's there's a lot [31:49] of under the hood stuff as well. Like [31:51] for example, it is a WordPress site. [31:52] What you're looking at the the block [31:54] developer handbook. It is absolutely a [31:56] WordPress site. Those pages are [31:58] generated. They are generated and they [31:59] are inserted. The content is inserted. [32:00] So you need to duplicate every single [32:02] page in that site like twice. you need [32:05] to have a version for core, a version [32:07] for Gutenberg, and a version for cutting [32:09] edge or even just Gutenberg and and [32:12] core. Um, so there's a lot that needs to [32:15] be figured out. It's a massive it'd be a [32:17] massive migration, massive scale, [32:21] you know, but that's a great question. [32:25] Yeah. [32:28] Yeah. [32:31] Oh, the playground devril is asking me a [32:34] playground question. I feel like I'm [32:35] getting sent up or set up. [32:42] I've working on the playground website. [32:44] What what is this? Let's uh this is the [32:47] one. While working on a playground [32:48] website, I noticed a Gutenberg modal [32:51] component using divs. Is there a plan to [32:52] migrate it to a dialogue component [32:55] because it's supported by 90% of the [32:56] browsers and a lot of stuff is [32:57] implemented on the browser side? I don't [32:59] know. That's a good question. H have you [33:00] have you taken a look in at the like I I [33:02] think it's worth opening up an issue. Um [33:08] I think it's definitely worth opening up [33:10] an issue. Let's see. Um let's do search [33:13] and issues because there may not be one [33:16] but and if there isn't I think it's [33:17] worth it's worth looking at. What is it? [33:20] uh [33:22] dialogue [33:25] component. [33:28] I spell it wrong. [33:32] Yep. I don't see any anything. I would [33:35] I' I'd go open an issue and and just [33:38] start the conversation, right? [33:42] The dialogue HTML tag is not in it. [33:53] dialog wrapper. [33:58] Did Did I put dialogue in? Oops. Oops. [34:02] Oh, new block dialog popup. Is this it? [34:22] So there is this issue [34:24] um if you want to take a look that even [34:27] more core core blocks that invited [34:31] themselves in. Um okay is that that [34:36] that's a statement. Yeah. um cross keys [34:40] the the thing about Gutenberg and the [34:42] thing about the the blocks is that [34:46] like [34:49] there's there's a there's I don't know [34:51] this is my opinion but I know that there [34:53] are a ton of blocks right it's just it's [34:56] a okay [34:58] yeah no and and I get it so like back in [35:01] my agency days we were like oh my god we [35:03] didn't do designs for every iteration of [35:05] whatever block right of all the embeds [35:07] of all the whatever all the icons, all [35:09] that stuff. So, it's hard, right? [35:11] Because you because when you're working [35:13] for a client, they have a very specific [35:15] like branding, [35:18] well, branding is the word I'm trying to [35:19] say. Then, like you have to you you have [35:22] to make sure that they can't make their [35:23] buttons rounded if that's if that goes [35:24] against the branding guidelines. So, in [35:27] that in that way, Gutenberg can be very [35:29] very frustrating. But on the on the flip [35:32] side of that is people that just want to [35:33] build a site don't want to be like the [35:36] like they need to have the tools to [35:38] build what they want, right? Like if if [35:41] they don't have if they can't embed [35:43] something on it, like I keep bringing up [35:44] embeds because I know that you're [35:46] talking about embeds in the Discord, but [35:47] I mean like if if they can't do what [35:49] they want to do, they're going to go [35:50] somewhere else, right? Um, so it's it's [35:52] a balancing act between like [35:56] giving authors what they want and and [35:59] then also like, you know, not inundating [36:01] people with with things. So, I mean, I [36:04] don't think it's a bad thing to disable [36:06] the blocks. I mean, it's easier it's [36:08] better, let's think of it this way. In [36:10] my opinion, it's better to have to [36:12] disable a block than it is to have to [36:13] build one that that they don't have [36:15] because disabling blocks is a lot a lot [36:18] less work. [36:20] Full stop. Mic drop. Whatever. I don't [36:22] know. [36:24] Cool. Um, [36:31] yeah, exactly. You just like turn them [36:33] all off and just, you know, bring them [36:36] back as as needed. I mean, like when [36:38] when you're when you're working at the [36:39] enterprise level, when you're working at [36:41] a big level, you're turning off a lot of [36:42] WordPress stuff anyways. Like so many [36:45] themes starters and scaffolds and stuff [36:47] like that, they turn off stuff, you [36:49] know, like maybe they don't want the [36:50] rest API. They just turn it off. Like [36:52] whatever. I mean the public, right? Oh, [36:56] I kind of dated myself because I don't [36:57] think you can turn it off now, but [37:00] unless you do that, the rich content [37:01] equivalent of the Homer Simpson card is [37:03] like, yeah, well, but that's just it, [37:04] right? You have to just get yourself to [37:07] a place where where where you need it. [37:09] So, I love the idea of it's better to [37:12] have it and not need it than to need it [37:14] and not have it, [37:16] you know? So, I don't ever think I'm [37:19] going to use a third like twothirds of [37:21] the blocks that that we're shipped with. [37:23] But that one time when I want it, it's [37:25] there, right? That's what I think. And [37:29] it's not hard to turn stuff off. It's [37:31] way harder [37:33] uh to to build out something and [37:36] maintain it too, right? Because the more [37:38] blocks that core builds, the less blocks [37:39] you have to build and the less blocks [37:41] you have to maintain. And with block [37:43] variations and block bindings and stuff, [37:45] that gets super powerful. [37:49] Yeah, you should absolutely do that, [37:50] Troy. Even if it's a snippet. So, uh, [37:53] the developer blog has like full [37:54] articles like this, but it also has [37:57] snippets which are super helpful. Um, [38:00] like how do I hide how to register a [38:02] blog variation, but hide it from the [38:03] inserter? See, that's what I did, right? [38:07] just little block uh variations. There's [38:09] lots of stuff in there. Uh snippets and [38:10] it's just like small little chunks of [38:12] code that can be helpful. There you go. [38:14] Go check those out. Pretty hardcoded, [38:16] but I've only had to do three CSS hacks [38:18] so far. Yeah. I mean, and if you find [38:20] something that's hardcoded and and and [38:22] you and you've got a valid reason for it [38:24] not to be hardcoded, then I mean, open [38:26] up an issue that it's not it's not like [38:29] you have to live with the way it is. I [38:32] mean, it's an open source project. I [38:33] mean, I realize it's hard to, you know, [38:35] not everybody has the time and and the [38:38] and the inclination to go and do it, and [38:40] I get that and that's cool. But I'm just [38:41] saying if you if you're having the [38:42] issue, someone else probably is. And if [38:44] you open up an issue with a potential [38:46] like, why don't we do it this way? You [38:48] know, like come to to the table with an [38:50] idea, and that's usually the way that [38:52] things get moved forward, right? [38:56] I built something similar in my [38:57] validation plugin when you can run a [38:58] validation in the editor and turn them [39:00] off in the side editor. Shouldn't be [39:01] hard to set that up for blocks. Yeah, [39:02] cool, cool, cool, cool. Um, okay. So, we [39:06] talked about Oh, yeah. So, we talked [39:07] about this. So, yeah, if you're [39:10] interested in following along or you [39:11] have or you have any ideas about this, [39:15] um, then I would love [39:18] I would love your [39:21] feedback on here. That's the issue. [39:24] Yeah, Troy, talk about your validation [39:26] plugin. Oh, I have an idea for a new [39:30] thing. um for the stream and I'm going [39:34] to start it with my with Rob who is um [39:38] with WP Rig and we haven't figured out [39:40] when we're going to do it yet, but I [39:42] he's he's going to come on the stream [39:43] and he's gonna we're gonna he he's going [39:44] to talk we're going to talk about it. [39:46] We're gonna hang out. So, I have this [39:47] idea. I It's a great name for a podcast. [39:49] I think it's called Talk Devi to Me [39:53] and the idea is people are going to come [39:56] on and we're going to talk about the [39:57] thing they're building and they can talk [39:59] Devi to me. So that's the idea. So Troy [40:02] Troy's got a couple of things in the [40:04] works which I I don't know if I'm [40:05] allowed to talk about them or not, but [40:06] his validation plugin, I think you [40:08] should definitely come on and talk about [40:09] it. And that thing you sent me, the [40:11] interactivity API thing that you're [40:13] working on, that would be cool when [40:15] you're ready for that. [40:17] Oh, [40:21] Troy can't send. Okay, so the links are [40:24] getting stripped out. That's that's [40:26] fine. [40:28] Um, [40:30] how can I allow that link? [40:34] Think I might need to change that. [40:36] I removed links for obvious reasons. So, [40:40] if you want to DM, um, [40:45] if you're in the Discord [40:48] Oh, why did AOL do Oh, Kevin, I think [40:50] it's because you're a moderator. [40:53] Yeah, [40:56] I I I I'll have to look look at that. [40:59] But if you're in my Discord, [41:01] um [41:03] drop drop the link in the Discord. Um it [41:07] might even be in there. [41:10] Yeah, if you drop the link in the [41:11] Discord, um [41:14] what you call it, your name is Troy, [41:16] then I can drop it in chat and and [41:18] that'll be fine. or if you want to just [41:20] go to my discord and we and we can share [41:22] stuff there, there's a uh show us the [41:24] goods page where you guys can can uh [41:28] drop your stuff in there. So, if you're [41:29] not on my discord, you can get there [41:33] right here. [41:36] You can you can go there and you're [41:39] welcome to join. It's not super active, [41:41] but I think I might try to channel some [41:43] of my my my link sharing there um just [41:47] to just to keep the porn to a minimum. [41:50] Uh but in anyways, yeah, cool. So, [41:52] that's that's what I was thinking. So, [41:54] if you guys are if anybody's got [41:55] anything that they want to share that [41:56] they want to talk about, um be cool to [41:59] have you on the stream and we and and [42:00] and we can chat about it. Um all right. [42:03] So, the next thing that I want to show [42:05] you guys is something that I've been [42:06] working on. Uh, I built it yesterday and [42:09] it is a extension. Where's my extension? [42:13] Right here. It's called [42:16] and uh [42:18] I I I built this with with Claude Code [42:21] in like two days and I'm super excited [42:22] with it. It's my first real like um [42:29] uh like real vibe code whatever thing. [42:31] It's got two downloads. Anyways, what [42:34] this is doing is this is for the [42:35] interactivity API. So, the idea behind [42:37] it is that if you're working with the [42:39] interactivity API and I open up a [42:40] render.php [42:42] and I can see I I I get told uh oh no, [42:46] where is it? TS. [42:54] Um what it it does for you is it does [42:56] autocomplete. So, you can autocomplete [42:58] each one of the the um directives. But [43:02] something that I'm really proud of is [43:03] that if you have stuff in in in state [43:05] Oh, is this not working now? Of course [43:06] it's not working now. Is this one not [43:08] have state? [43:10] Where is it? TS. No, there's no state. [43:13] Uh item one, [43:17] item [43:18] two. Right. So what should happen here [43:21] is when I hit state, I get prompted with [43:24] the items from the state. So if I have [43:26] callbacks for example or action come on [43:31] actions [43:33] if I go on there we go. So so it's it's [43:36] it's inspecting my uh view my my view uh [43:39] file and finding this. Um [43:43] so the and it uh so I'm super excited [43:46] about this. So if you're interested it's [43:47] it's available for for download if [43:49] you're working with the interactivity a [43:51] API. I'd love some feedback on it. Um [43:54] because what I want to make this what [43:56] one thing that bugs me, not bugs me, but [43:58] I struggle with like remembering all the [43:59] directive names. I struggle with making [44:02] sure I I can remember what the name of [44:04] my of my callbacks are. And so the whole [44:06] point of this is to make it so that's [44:08] not an issue anymore. Right? So now I've [44:10] got that. Um the other thing it does is [44:14] if you've worked if you've screwed up [44:15] the name of your uh of your store, it'll [44:19] actually tell you, hey, there's no store [44:20] name dev inspector. D [44:23] And so you can figure that out, right? [44:26] So it inspects your VTS. It works with [44:28] with JS files, all that stuff. Um, oh, [44:31] and the other thing it does is detects [44:34] duplicate [44:36] um [44:39] duplicate uh directives, which is pretty [44:43] cool. So if you were to do like a like [44:46] like one of these, the other thing it [44:48] does, so there's a there's a couple of [44:50] ways it handles it. So you can actually [44:52] add a you can add a um a unique [44:57] identifier to the end by going like [45:00] three dashes and then say what other one [45:02] or whatever right and so that will [45:04] actually make it valid. [45:07] So yeah I don't know I'm super excited [45:10] about this mostly because I wrote it in [45:11] in in code like after hockey one night. [45:15] So, yeah. [45:19] So, if you're interested, you can [45:21] download it um by getting this. How do I [45:25] Here's where's the store page? [45:28] How do you get to the store page? [45:36] Neoim. Um maybe I don't know. Could look [45:39] into it. How do we get the stupid store [45:42] page? Um, [45:49] copy link. Is this it? [45:54] Yeah, there you go. So, go download go [45:56] and download this. There is a repository [45:58] for it. Um, please let me know if you [46:02] run into any issues or any anything. The [46:05] whole point of this is to be as e to [46:07] make it as easy as possible to adopt the [46:10] interactivity A API. Um, like I said, it [46:12] works with TypeScript. It works with uh [46:14] just regular JavaScript. [46:17] Um, so yeah, [46:20] bad dude, you're doing a ton with it, [46:21] right? That's the Did I Oh, I already [46:24] linked that. Sorry about that. Um, yeah. [46:26] So, I mean, I I'm going to put something [46:28] up on the socials today. I I I know [46:30] there there are some some hardcore um [46:34] interactivity API developers out there. [46:35] I think you're one of them. So, let me [46:37] know. I mean, full disclosure, it like [46:42] Is it uh what's the current state of the [46:44] client side? [46:48] What's the current state of client side [46:50] full page navigation? Um well, it's it's [46:52] it's an experiment. You can add it to [46:54] you can you if you're in if you're in a [46:57] WordPress site. Oh my god. Where's the [46:59] mouse? Where's the mouse? What's going [47:00] on here? Hello. There we go. If we're in [47:04] like in here, we go to Gutenberg, I [47:06] think, and experiments. Now, God be gone [47:09] with you. [47:13] Oh, boy. Okay, I got to go to plugins [47:17] and I have to turn off this [47:20] plugin. You should be able to get if you [47:22] go to experiments and where is it? [47:27] Oh, full page client side navigation. [47:33] And I think it just [47:39] maybe not. Oh yeah, that's working. [47:44] Yeah, so it it works. Um, it's it's uh [47:47] there's a technical reason why it's not [47:48] in core yet, but I I thought I saw [47:50] rumblings that it's coming to core [47:51] pretty quickly, pretty soon. And like [47:52] the transitions API and stuff like that [47:54] might be coming to the admin side, but I [47:56] can't remember where I saw that. Might [47:57] have been one of Felix Arnson's tweets, [47:59] something like like that. Um, yeah. So, [48:04] yes. So, anyways, back to back to the [48:06] thing that I built and I want to talk [48:07] about. Um, if you if there's anything [48:10] that this doesn't do, let me know. If it [48:12] does weird stuff, let me know too [48:13] because because one thing I have it Oh, [48:15] the other thing it does and and I I [48:17] meant to show this is it actually will [48:19] um it it'll detect [48:23] it will detect like if you do um data [48:28] uh w [48:32] P- [48:35] I can type it right context. [48:39] weird that it why is context not in [48:41] there? It what it should be able to do [48:44] is actually [48:46] um [48:48] you should be able it it it can parse [48:51] context in this state in in this state. [48:53] So if I if I were to go context [48:56] dot dot dot [49:00] okay [49:05] revash store cache okay um [49:12] okay well that's not working should have [49:14] been working though [49:19] oops [49:20] that's unfortunate okay Well, [49:24] because what it should be doing is it [49:26] should be able to where is it? Um, [49:31] support directives. [49:35] There is a context parsing. [49:42] Did it not make it in? [49:45] Look at that. [49:52] Huh. Okay. Well, in my um [49:57] Well, if that's not Yeah, I I'll have to [49:59] check that because it was working [50:00] before. This is [50:02] So, in here, if I look at my testing, I [50:05] have um context. Yeah. So, what this [50:09] should be doing is it actually will it's [50:12] supposed to be able to detect this this [50:14] context here. I do this. Okay. See, it's [50:17] actually pulling context in. So, that's [50:19] I have to check and see why that's [50:20] that's not happening in that given [50:22] thing. Uh, but this what it's supposed [50:24] to do is it's supposed to be able to be [50:25] able it's supposed to be able to figure [50:26] out the context that's been passed down. [50:28] Um, so, you know, we will I'll look into [50:32] that. But anyways, it's very like 1.0. [50:36] So, I'd love I'd love feedback. And uh [50:39] oh, and while we're here, I'm going to [50:42] start viewer callins if anyone's in [50:44] interested in hanging out. Uh I'm going [50:47] to make you you have to be followers and [50:48] subscribers now, though. [50:51] Followers or subscribers. And you're [50:52] welcome to jump on the stream with me [50:54] and hang out. Um but this this was fun. [50:58] So I I claude [51:01] code to do this and it just basically it [51:04] just got it. It just did it and it was [51:05] like pretty amazing. took me a bit of [51:08] refining. Uh, and I used I used a nano [51:11] banana to come up with the uh with the [51:14] where is it with [51:18] with my extens with the icon which is [51:20] where is the icon? It's right here. That [51:23] little thing. So, I'm all AI. I'm all in [51:25] on AI. It will not work in PHP Storm, [51:28] Paul, but I've been thinking I don't [51:30] know if PHP Storm does autocomplete. I I [51:33] know it does like snippets, live [51:35] templates, I think they're called. Um, [51:38] but I don't think I don't think you can [51:40] do the same sort of autocomplete stuff. [51:42] But I but I'm not sure. It's been a long [51:44] time since I've uh um [51:49] used um PHP Storm. Okay. Well, I will [51:54] make you know what I'll do. I'm going to [51:55] take I'm going to ask Code to take the [51:58] functionality of this and create a VS uh [52:01] PHP Storm extension um for it. So that [52:06] that'll be fun. [52:09] Yeah. It's like when you're getting into [52:11] like the the AI inception, like when you [52:13] do this, you know, you're like, I'm [52:16] using AI to build a prompt for another [52:18] AI. It's crazy. Um I don't know how long [52:21] it's going to take me to do it, Paul, [52:23] but I will um I will see what I what I [52:27] can do. [52:30] Um, and yeah, if if and if it just [52:32] doesn't work and it's just it's just [52:33] broken, like those those lovely [52:36] individuals that are going to test this [52:37] thing out for me, uh, let me know. Like, [52:39] let me know. Uh, do the Ralph [52:43] Ralph Wigumstrat. [52:45] What is that? [52:52] That was a Ralph Wiggumstrat. I'm not [52:54] googling that. Kevin. [52:57] Oh, Kev, are you going to work campasia? [53:02] Do I want a link? No, I don't want a [53:04] link. Do I want Ah, I don't trust you. I [53:07] trust you. You're not going to send me [53:09] bad things. Send the link. Yeah, send a [53:11] link. Ralph loops are a legit AI thing. [53:19] The Ralph I've never heard of this. [53:21] Okay. Well, I'm I want to learn about it [53:22] then. So So [53:25] put Okay. I'm going to Google this [53:27] offscreen. I I just I'm so scared of the [53:29] internet now. [53:33] Wiggum [53:37] Ralph Wigum strategy. Let's see. [53:44] Iterative autonomous AI development [53:45] meth. Okay, hold on. [53:49] Awesome. Clo.ai. What is this? [53:59] Oh my god. [54:03] Huh. That's pretty cool. [54:07] Okay. I learned something new today. [54:10] It's a real thing. India. I want to [54:12] maybe 50/50. Yeah, I'm I'm going. Well, [54:17] I've been accepted to speak and I think [54:19] I'm going. So, we I I haven't got [54:21] official uh formal yes or or not, but [54:26] if anyone else is going to be there, I'm [54:27] hopeful I there's a good chance I I will [54:29] be there as well. So, be great. Be great [54:32] to hang out [54:35] um [54:36] and hang out and do stuff. [54:40] All right. Um [54:43] I don't really have much else I I was [54:44] going to really go over. Let's see [54:48] snippets. See, we talked snippets, [54:50] talked about PHP only blocks, tell [54:53] rebuild all of our person JS and let it [54:55] run for three months and see what [54:56] happens. Oh my god, you imagine the [54:57] tokens you you'd blast through. [55:02] I also discovered Sununo. Well, I I got [55:06] an account at Sununo and I spent an [55:08] entire day building uh songs for my [55:11] daughter's volleyball team [55:14] and ridiculous like uh um just just [55:20] ridiculous songs. It was so much fun. It [55:22] is so much fun. Go and do it and get [55:25] them. It's so good. [55:32] Yeah. Isn't it amazing? And it's so [55:34] good. So, I I opted for the uh I opted [55:39] for the um [55:41] like I'm I'm I I'm using it for work. [55:45] So, uh let's see. Let's [55:49] just see. Um, [55:53] and like I'm I I'm just playing around [55:57] with it and it is so much fun. [56:00] Like listen listen to the song. Can you [56:02] hear this? [56:10] Turn it up. [56:20] >> And then I went for an East Coast. [56:22] >> This is No, [56:24] >> not that one. Is this one [56:26] >> 90s East Coast rap? [56:38] >> Isn't it so good? blow [56:42] from the north where the gym squeak. We [56:44] ride trailblazers on the back. [56:46] >> I'm going to have to go [56:50] on the baseline [56:52] on the left side. [57:04] She be hitting on speed and gas roll [57:06] shot then a rip defenders crash. [57:10] >> You could hear that, right? Oh yeah. [57:12] Okay. [57:18] Um I heard the worst song ever in the [57:22] store yesterday and it was like it was [57:24] literally called I Love the 80s. I I'd [57:25] never heard of this song before and I I [57:27] I'm listening to it. God, oh man, it's [57:28] horrible. And then uh I realized this [57:32] might be an AI version. Like this could [57:33] be an AI song where someone just said, [57:36] "Write a song about loving the 80s." And [57:38] it sounds like every '8s song I ever [57:39] written. [57:43] Oh my god, that's hilarious. [57:47] Um, what would be really funny is if I [57:50] thought you guys could hear the music [57:51] that I was playing and I was dancing to [57:53] it, but in real life it was just me like [57:55] just doing this with no sound. That [57:58] would have been hysterical. Please tell [58:00] me that didn't happen. Or maybe that did [58:02] happen. [58:03] Gonna put my stream music back on. [58:11] All right. No one wants to jump on [58:14] stream with me. Come on, Kevin. [58:28] Oh, there's Paul. Paul wants in. All [58:30] right. Come on in, Paul. Right. I I I [58:33] have to drop right at noon, but if we [58:35] all just want to pile in and talk about [58:36] whatever, let's do it. I see Paul [59:01] Uh, yes. [59:03] >> Hello. Hello. Hello. Hello. [59:05] >> There he is. [59:09] >> Audio is the audio better today. [59:12] >> I'm just I've just your API plugin. I'm [59:16] getting um the uh [59:23] >> I think you're sending yourself back to [59:25] me there. [59:26] >> Uh AI in PHP Storm to try and do the [59:29] conversion for me. [59:31] >> Oh, nice. [59:33] All right, let's see. Oh, I know what I [59:36] need to do. Sorry, I think that's my [59:37] bad. One second. I'm going to turn off [59:39] the Google Chrome. Can you say something [59:42] again, Paul? [59:48] 1 2 3 4 1 2 3 4 1 2 3 4 [59:54] >> one two [59:56] >> H [59:58] Okay, [60:01] I'm going to say this and then when I [60:03] hear myself, I'm going to start speaking [60:05] again. [60:11] Now ended [60:15] Okay. So, I'm I'm hearing you double. Uh [60:19] I wonder if I turn this off. Wait, turn [60:21] that off. How about now, Paul? [60:26] Oh, that's better. Okay, that's super [60:28] loud, though. Okay. I think I was just [60:31] hearing you. You doubled because I had [60:32] the uh I have the [60:35] audio from the browser source for stream [60:37] together. Anyways, but you can hear me, [60:38] right, Paul? [60:41] Okay. I can't hear you now, though. [60:45] Yes, I can. One, two, three, four. Yes. [60:47] >> Okay, there you go. Perfect. Okay, [60:49] excellent. We'll get this. It's my first [60:50] day with the internet, folks. First day [60:51] with the internet. Alus, why aren't you [60:53] getting in here? Come on. Come on. Let's [60:55] do it, [60:57] Paul. Uh, so, sorry, Paul. So, you're [60:59] going to take that thing that I did and [61:01] you're going to get AI to convert it to [61:03] PHP Storm. [61:09] >> Yes, I am. [61:11] >> Oh, awesome. Enjoy. [61:15] >> Cool. Um, that's great. Well, I'd I'd [61:19] love to see it. I'd love to see what uh [61:21] how it all works. [61:24] >> There's a there's a branch and a pull [61:26] request coming. [61:28] >> I told [61:29] >> Oh, pull request. [61:30] >> Yeah, I told it to make it to merge into [61:33] the same thing and see if we can have [61:34] the one. [61:37] >> Oh. Uh, okay. Well, that that might that [61:40] might break it. [61:42] But but we'll see uh [61:47] just because it uh the the the the way [61:50] it's b the way it's bundling might not [61:52] work but [61:56] let's see it's building it's building a [61:58] pull request right now. That's crazy. [62:00] >> No, not yet. Still coding. [62:04] >> Oh, okay. All right. [62:08] All right. Cool. [62:10] Cool. Cool. Cool. [62:17] >> So, what what's what else has been going [62:18] on, Paul? [62:21] >> Just going I'm working on [62:25] um Let me get a ticket. [62:30] Um allowing [62:33] um allowing [62:35] to static pages to be other CPTs. [62:43] Okay. [62:45] Allowing static pages. [62:48] I don't think I did. Uh oh, you you [62:51] can't you probably can't drop the link. [62:52] Um I'm gonna have to figure out out a [62:54] way to let people drop links. Let me [62:57] just uh Twitch and I'll [63:01] see what I can figure out here. [63:07] What are we doing? moderation settings [63:13] block hyperlinks. [63:15] Uh, okay. Your chat will automatically [63:18] delete posted URLs except for once [63:19] posted by you, moderators, admins, and [63:20] VIPs. Oh, okay. So, I can turn that off. [63:26] And then [63:30] then I have to make people moderators, I [63:32] guess. Mins. [63:36] Okay. [63:42] You know what? I'm I'm going to turn [63:44] links back on and then I think because [63:46] I've also ch changed some chat [63:48] verification. So like chatters need need [63:51] to be like basically [63:54] um [63:58] they they need to be verified. So I I [64:00] don't know. I'm just not going to click [64:02] links. So if you have a link, Paul, just [64:04] just uh drop it in chat. [64:07] Um, [64:09] bad do court. Thanks for hanging out. [64:10] We'll see you next time. And, uh, oh, [64:13] uh, Troy, if you're still around, drop, [64:15] uh, drop your link to your accessibility [64:17] plugin or the accessibility checker in [64:19] the, um, in the chat then so people can [64:22] get it. [64:24] Sorry, Paul. You uh, so what is the [64:28] ticket 19? So, this is a court. This is [64:30] a track ticket. [64:32] >> Yes. [64:33] Okay. [64:39] See what this is. [64:43] Allow custom post types as home and get [64:45] get post return results for more than [64:46] one post type. [64:52] Oh, I see. [64:55] What was that? [65:01] Oh, I see. So, so this is basically [65:03] change what what is this changing the [65:05] like it's just it's retrieving [65:09] Oh, I see. So, so is a get post just is [65:12] it restricted to um [65:24] I should not have done that. I'm going [65:25] to be the PR. [65:27] There we go. So that's T link [65:41] posts allowed on homepage. Oh, I see. [65:43] Okay. So is this a is this filterable? [65:45] Oh, it is filterable. [65:47] >> Get post show and homepage list is true. [65:50] Is this an actual thing [65:52] or is that new? The show and homepage [65:56] >> list. [65:56] >> No, that's new. That's new that [65:59] >> Oh, nice. [66:00] >> That would be because not every CPT is [66:03] appropriate to be on the homepage or be [66:06] the home page. So, [66:08] >> right, [66:08] >> you have it has to be explicitly turned [66:11] on for [66:14] >> interesting. That's cool because that [66:16] that does make sense because you I mean [66:18] there's probably tons of reasons why you [66:20] wouldn't want to use a page or whatever. [66:21] You know, there's lots of things [66:24] um or or a list of posts or whatever. [66:26] That's That's pretty cool. So, what's [66:27] the what's the consensus on this that [66:29] it's uh it's good to go or it's like [66:31] people are into it? [66:33] >> Uh [66:34] >> scroll down to the bottom to find out. [66:35] >> It's um it needs some work. Um I'm [66:38] rewriting it and doing some some uh u [66:41] gooey work [66:43] and fixing a few things. So, [66:46] you know, this week's project is what [66:48] I'm trying to get this to a working [66:51] version with today's code. [66:56] Oh, okay. Cool. [66:59] So, are you working on the pull request [67:01] that Adam was doing or like your own or [67:03] or a different patch? [67:04] >> I've pulled off Adam's work. [67:06] >> Oh, okay. Cool. [67:10] Oh, I see. Cool. Awesome. Well, that's [67:13] pretty cool. I mean, that that'll be a [67:14] nice little change for sure. [67:16] >> Yeah. Adam basically took my patch and [67:19] made it into a GitHub repo at some [67:22] point. [67:22] >> Oh, okay. Cool. Cool. [67:26] That I'm always stealing people's code. [67:28] Just kidding. [67:29] >> And you have a pull request on your API. [67:32] >> I do. Oh, no. Well, I probably won't [67:35] merge it because I don't know what this [67:38] is going to do for like the like Did you [67:41] Did you test this? What's this? Add in. [67:45] Um there's a folder in there with a PHP [67:47] plugin in it. [67:53] Oh my god. Okay. [67:55] So, okay. Hold on. [67:59] Well, [67:59] >> the IDE stuff went as well, which [68:01] shouldn't have done. Sorry for that. [68:03] >> Oh, whatever. That that's that's fine. [68:06] I'm going to just hide all this. So, [68:08] what does this thing do? [68:11] Okay. [68:13] Oh, this is interesting. [68:19] Can Can I just download a zip of this [68:21] particular [68:22] >> Yeah, you can. [68:23] >> Can you download a zip from from this [68:25] branch? [68:26] >> Hi, Blue. I literally ne never done that [68:28] before. How would I do that? Code. Oh, [68:31] yeah. Right there. Uh code spaces. [68:35] >> I know. I would like [68:45] Okay. Well, I'll have to look at it. [68:47] >> Yeah. No, I'm gonna have to try and see [68:48] if it if I if it'll actually run because [68:51] this is [68:54] >> Wow, this is cool. [68:56] Look at all this. Oh my god, there's so [68:58] much stuff here. And so, where is this [69:00] putting this PH? Oh, it's it's putting [69:02] it in inside of a inside of a uh Can I [69:04] look at the code? [69:07] So, I love how it's one commit. [69:10] That's so much stuff [69:14] with 21 files. That's hilarious. [69:17] Uh, that's cool. Okay. Well, I mean, I' [69:20] I'd be really interested to see if if if [69:22] this works because I think PHP Storm is [69:24] definitely something that like there's a [69:27] lot of VS Code extensions out there, but [69:30] um, not all like, you know, there's a [69:32] lot of PHP Storm users as well. Um, do [69:35] you get proper TypeScript support help [69:37] and stuff in PHP Storm? I I I used to [69:39] love PHP Storm. I used it all the time. [69:41] I used to use it all the time, but I [69:42] switched to VS Code a number of years [69:43] ago now. Um so so I'm a little bit uh [69:46] behind on it, but it'd be very cool. So [69:49] it does like autocomplete and all that [69:51] stuff. [69:52] >> All that good stuff. It finds all the [69:55] all the functions and all that stuff. [69:57] >> Okay, great. So, I mean, this would be [70:00] very cool if we could split this out [70:02] into its own [70:04] um [70:06] into its own uh folder inside of this. [70:10] So, did this move everything or did it [70:14] just put a folder beside it? [70:17] >> No, it put a folder beside it. [70:23] >> So, there's a folder. So all that code [70:26] that's in the original repository there [70:28] there's just like a there's a PHP Storm [70:30] folder in there now. [70:32] >> Yes. Yes. [70:33] >> Okay. [70:35] Interesting. [70:36] >> Yep. [70:37] >> Um [70:39] so I wonder if maybe we can put all the [70:49] And it's still by the command pal. This [70:51] is [70:53] um I wonder if you wouldn't mind telling [70:56] your a AI to take all the the the [70:59] existing files and put them in a VS Code [71:01] folder. So So there'll be like [71:04] essentially two folders at at the root [71:06] of the um at the root of the project, [71:10] which would be like VS Code, PHP Storm, [71:13] and then kind of go from there. But [71:16] again, I'm not sure if I'm gonna if I'm [71:18] gonna uh merge this or not, but this is [71:22] I'd like to see if it works, which would [71:23] be cool. So So So tell me if it works [71:26] and how it works and everything. We can [71:27] go from there. [71:35] >> We'll play. See what happens. [71:40] Can you share your screen? Did Did I [71:43] allow that? I I don't know if I allowed [71:45] that or not. [71:56] >> No, disabled my end. H [72:02] maybe I can [72:08] I might have to [72:17] I probably needed to set that up before [72:19] I uh there was a Oh, wait. What's in [72:22] there? Oh, yeah. Can I try that? Can I [72:26] Ah! Oh, hold on. Okay. [72:31] Uh, I need to I need need to set that up [72:34] for another time, but that's cool. Um, [72:36] you can just let me know if it works, [72:37] which would be great. Um, that'd be fun. [72:47] Oh, Troy, what are you saying? Sorry, [72:48] Troy. Uh, I should dive back into some [72:50] old issues I created. Do a bit more [72:51] contributing. Yeah, we like [72:53] contributors. [72:55] Where can I find the snippets link on [72:58] the developer? Oh, the snippets link. [72:59] Yeah, it's right there. Um, [73:02] it's here. Elus, that's for you. [73:07] And we're always looking for new [73:08] snippets. So, snippets and articles and [73:11] all sorts of fun stuff. We're always [73:12] looking for that at the uh for the [73:16] um developer blog. There's the process. [73:18] It's pretty pretty easily, pretty well [73:20] documented. There's a how to how to [73:22] contribute section under the about if [73:24] you're interested in getting involved in [73:25] adding whatever go read that. I think [73:28] there's a uh there's a monthly meeting [73:30] to discuss the content that's like the [73:32] ideas that have been put forward and [73:33] then if they get approved they get you [73:35] can just write it or do it and you can [73:38] go from there. Oh, excuse me. [73:44] All right. What time is it? Well, Paul, [73:47] is it working? [73:48] >> No, not yet. I can't work out how to [73:51] actually load it into the plugins. [73:54] >> Oh, I see. [73:59] I don't think I have Do I have PHP Storm [74:01] set up? I do not. [74:04] All right. I'll probably have to [74:05] download that, try it out. First Tuesday [74:07] of each month, we meet. There you Yeah, [74:10] Troy's on the one of the one of the [74:13] people that approve it. So, sweet talk [74:15] him. Go download his plugin. [74:18] All [74:22] right. Well, I'm gonna have to cut this [74:25] a little bit short today because I have [74:27] a very important email for my daughter's [74:29] volleyball team uh that I have to def [74:32] tell them what hotels we we want to stay [74:34] in and it's first come first serve. So, [74:35] I have to like literally wait by my [74:37] email hovering to click it and go. So, [74:40] it should be coming in shortly. But, I [74:43] want to wait and Paul I want to I want [74:45] to hear just how good it is. If if it's [74:47] good, [74:57] I'll let you know. [74:59] >> All right. [75:08] And um like I said before, if anyone's [75:10] interested in uh jumping on stream, [75:14] doing that [75:16] showing show and tell sort of thing. Um [75:19] in my Discord, there is a show us the [75:21] goods channel. You can drop a message in [75:23] there and we can coordinate something. [75:25] I've got my first one sort of I got my [75:28] first guest lined up, but I don't know [75:30] when we're going to do it yet. And then [75:31] after that, it'd be great. I don't know. [75:33] We could do it every once every couple [75:34] weeks, once a month, something like [75:35] that. People have stuff they want to [75:37] share. I think I think it's cool. It' be [75:40] fun. And maybe we'll turn it into a [75:41] podcast because everyone needs a [75:43] podcast. I don't have one. Paul, do you [75:46] have a p Do you have a podcast, Paul? [75:48] >> Yeah. [75:50] Um, [75:50] >> do you have a podcast? [75:51] >> No, we haven't. I haven't got a podcast. [75:53] >> Oh, [75:56] I was gonna say. [76:00] So, if anyone wants to start a podcast [76:02] with Paul and I, let me know. We'll [76:04] we'll [76:07] definitely do do a show project. Yes. [76:10] Cool. Troy, you're in you're in for that [76:14] because let's do it. You'll be number [76:16] two. [76:19] I think that I think that'll be a ton of [76:20] fun. Okay, awesome. Well, let's get [76:21] organized. We'll um you you let me know [76:24] when you like we'll we we we can talk [76:27] but let's let's get something figured [76:29] out in the next like [76:31] couple of weeks. What like not to be [76:33] live in a couple of weeks but to get it [76:36] figured out when they would work when [76:37] you think it's it's ready when we can go [76:39] through it so you can show it and we can [76:40] also like talk about the the the the [76:44] technical stuff. Nice. Oh, you're [76:46] waiting on some early feedback from me, [76:48] aren't you? [76:51] You know what I I'm I'm going to do I'm [76:53] gonna um I'm gonna my kid and I are [76:56] going to sit down and we're going to [76:57] play it because he's been he's been [76:58] dying to play Dungeons and Dragons and [77:00] it's um this sort of idea. It's not [77:03] Dungeons and Dragons. I didn't I didn't [77:04] let it the cat out of the bag, but [77:05] something along those lines would be [77:08] fun. So, he he would probably love it. [77:14] All right. Well, I will uh yeah, I'll [77:16] definitely play it and I can even play [77:18] it on stream at some point. Maybe when [77:20] you're ready. When it's ready, maybe we [77:21] can do a game. That That'd be fun. Don't [77:23] let him play Flappy Bird. Yeah. If [77:25] anyone wants to get on and and and show [77:27] me their clone of Flappy Bird, I can [77:29] tell you now that I will 100% approve [77:33] that. I I idea. [77:36] Yeah. I sorry I let the cat out of the [77:39] bag, but it's very cool and I'm not [77:41] going to talk about it anymore because I [77:43] love the idea of it. It's this game [77:46] where like you have to throw pigs at [77:50] like structures and they fall down. It's [77:52] crazy. I've never seen it before. [78:01] Oh my god. We're going to make an AF. [78:03] I'm Okay, next. I have my next stream. [78:05] We're going to make a Flappy Bird clone [78:07] using the interactivity API on stream. [78:10] Kevin, [78:12] that's amazing. What better way to get [78:14] back to the Dave426, whoever the hell [78:16] that stupid bot was by not letting him [78:19] get us down. We're going to do it. We're [78:20] doing it next stream. Unless [78:23] Rob and I are are going to be on next [78:25] stream. So, next two streams that's [78:28] going to get done. That's going to be so [78:29] much fun. [78:31] Oh, I'm excited. I'm excited. Sorry, [78:33] Paul. I forgot you were here on the [78:35] stream with me. [78:38] How are you doing over there, Paul? [78:40] >> I'm doing good. I'm I I'm I'm just [78:43] reading the notes of how to do this now [78:45] and I need to use IntellJ ultimate [78:47] edition which I happen to have. So [78:49] that's good. [78:50] >> Oh, all right. Cool. Kevin, that was a [78:53] great idea. [78:54] >> This is actually [78:57] >> it's what? Sorry, [79:04] I didn't hear what you said. Oh, it's [79:06] written in Cotlin. Oh, wow. [79:09] Yeah, that's the thing. It's just like, [79:10] "Build me a thing." They're like, "Sure, [79:12] we're going to write it in C#. [79:14] Now you got to compile it." [79:18] Yay. Do you even compile C#? I I don't [79:21] know. C++ you do, I think. But [79:25] I'm not what you'd call a good [79:28] developer, so who knows? Who knows? [79:33] Um, all right. Well, on that note, Paul, [79:37] I'm gonna have to drop off, but thanks [79:38] so much for drop for for hanging out on [79:41] on camera wi with me. Um, and uh yeah, [79:47] thanks for for streaming with me, y'all, [79:49] and uh for sharing your links now that [79:51] you can share links again and for the [79:53] ideas, the content ideas. This is great. [79:54] We're gonna have so much fun in the next [79:56] few weeks. I'm very excited to do all [79:58] this. Um, and uh, yeah. So Paul, is it [80:04] it's it's it's not doing it. It's not [80:06] compiled yet or built or whatever. [80:08] >> No, I'm still install reinstalling the [80:10] uh IntelliJ because um I hadn't I turned [80:13] it off because I had I stopped using it [80:15] because I thought be a bit lighter and [80:18] just have PHP Storm running. [80:20] >> Yeah. Yeah. [80:22] >> Sure. That's actually one of the reasons [80:23] I moved away from PHP store because it [80:25] felt like such a beast. Like every time [80:26] I I I opened it, it just felt huge and [80:29] bloated and then like VS Code was like [80:31] instantaneous. [80:32] >> Yes. Until you file in all of the [80:34] extensions. Um it's [80:36] >> Well, there's that. [80:37] >> Yeah. And that's the difference is in [80:39] PHP Storm, you've got to configure it [80:41] and add all your other extensions. [80:43] Sorry. In VS Code, you got to do that. [80:46] PH4 Ptorm it's predetermined and bundled [80:49] and you only have to add a few plugins [80:52] to to tweak it whereas not everything [80:55] >> for sure. I I loved PHP Storm. I I will [80:58] say this. I found it much easier and [81:01] better to debug PHP in PHP Storm than in [81:05] VS Code. I found it like very intuitive, [81:08] very easy. like once you got XD bug and [81:10] everything all set up, I found it super [81:12] easy and it and the the inspection like [81:14] everything that you can do is really [81:15] really good. I find VS Code to be okay [81:18] in that regard. Um, but I transitioned [81:22] to VS Code right right around the time [81:23] that I was sort of like getting into a [81:24] lot more JavaScript. So, I wasn't doing [81:27] as much like PHP [81:29] um inception stuff like you know. So, [81:32] and it could just be that I just didn't [81:34] spend enough time to get it set up [81:35] properly. But I found PHP store to be a [81:37] lot more robust with that sort of stuff. [81:40] Um, but then in VS Code side, like it's [81:42] really great for all all the npm and the [81:45] auto formatting and the auto saving and [81:46] like all that sort of stuff. So, I mean, [81:48] they both have their their benefits. It [81:50] really just depends on what you're doing [81:51] with it, right? [81:52] >> Yeah. [81:53] >> Yeah. Yeah. Yeah. PHP is great and and [81:56] that's the other thing. You don't have [81:57] to pay a license for for PHP or for VS [81:59] Code. [82:00] >> No, that's true. It's free. Yeah. [82:02] >> But I'm happy to support them. and [82:04] they're doing good work and they're [82:06] they're the writing. [82:06] >> Oh, for sure. [82:08] >> So, yeah. No, no, no. I mean, it's it's [82:10] it's if if I mean, if it's like it's [82:12] like, you know, if if you're a mechanic, [82:14] you you buy your tools, right? Like this [82:16] this IDE is literally your tool for [82:18] doing your job and making money. So, I [82:20] mean, of course, investing in it is [82:22] makes sense. [82:22] >> And I I ended up with the ultimate [82:25] package. Um, and I the maths um worked [82:29] out better with the um um uh AI tool [82:33] built in because of the ultimate [82:35] package. I the AI tool bundled with it. [82:38] >> So I haven't had I'm not paying extra. [82:40] So it it actually comes out cheaper to [82:42] have PHP [82:43] >> to have the bund the whole bundle not [82:46] just PHP Storm and the uh AI tool. [82:50] >> Oh, I see. Because because PHP like in [82:53] intellisense or what whatever the [82:54] company is intell whatever the company [82:56] is that PHP store I can't remember [82:58] >> nippines like yeah like that they have a [83:01] number of other IDEs for for other other [83:03] things. [83:05] >> So cool. All right. Well, now that uh [83:08] Paul's told us he has the ultimate [83:10] package. Lucky lady your wife just [83:12] joking. Oh, that's a horrible joke. I [83:14] gotta uh I'm gonna I'm gonna leave on [83:16] that very not safe for work tone and [83:20] We can go from there. Paul's not [83:22] laughing. I feel like I offended him. [83:24] >> No, no, you haven't. [83:27] >> It's meant with love and respect, Paul. [83:28] It's a joke. [83:29] >> Yep. [83:30] >> Um, yeah. [83:36] Awkward. Anyhow, um [83:40] Oh, yeah. There's a delay. There's a [83:42] six-month delay in the [83:44] >> Yeah, I know. [83:46] I was I was concentrating slightly on [83:49] opening up the uh the project in [83:53] >> Okay. All right, Paul. Well, I mean, bad [83:56] jokes aside, I hope I haven't offended [83:58] you. That was not the intent. [84:02] I just couldn't I couldn't help myself. [84:04] All right. And on that note, I'm gonna [84:06] I'm gonna say goodbye, friends. And uh [84:08] call in HR. Yeah, Kevin's calling HR. [84:11] Yeah. Um uh and yeah, cool. So, next [84:15] week, I'm not sure what it'll be, but [84:16] it'll be something fun. So, uh, drop in [84:19] and say hi. And, uh, yeah. Anyways, [84:23] Paul, thanks so much for hanging out and [84:24] the for the for the poll request. Thanks [84:27] everyone else for for chilling with me [84:28] today. I'm going to say bye and I will [84:30] talk to you all later. [84:34] If I can find the button. There it is. [84:36] Later.  [[3. Resources/Readwise/Full Document Contents/Articles/Just Chatting and Clicking Random Links!|Full Document Contents]] ## Document Notes --- tags: #wordpress #gutenberg #php-blocks #live-stream author: Ryan (Stream Host) source: Twitch Stream reference: https://www.youtube.com/watch?v=xPskuyyIrps date created: 2024-12-28 16:21 --- # 🏷️ Title: Just chatting and clicking random links! ## 🧰 Action Inbox - [H1] Test Gutenberg 22.4 PHP-only blocks functionality — live demo #gutenberg - [H2] Review VS Code Interactivity API extension feedback — extension launched #interactivity-api - [H3] Consider Talk Devi to Me podcast format — community engagement #devrel ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [Gutenberg 22.4 Release](https://make.wordpress.org/core/handbook/) - [VS Code Marketplace Extension](https://marketplace.visualstudio.com/) ## 📝 Summary - Live stream covering Gutenberg 22.4 PHP-only blocks, VS Code extension demo, and community discussion - Why it matters: Shows practical WordPress block development without JavaScript build processes - Key stakeholders: WordPress developers, block creators, community members - Risks and tradeoffs: Documentation gaps between Gutenberg plugin and core WordPress - Bottom line takeaway: PHP-only blocks now functional in Gutenberg 22.4, new developer tools available ## 📖 Main Content Ryan demonstrates the newly functional PHP-only block registration in Gutenberg 22.4, showing how developers can create blocks using only PHP without JavaScript build processes. He showcases his new VS Code extension for Interactivity API development, discusses documentation challenges in the WordPress ecosystem, and engages with community members about various development topics. The session covers technical implementation details, community feedback on block proliferation, and practical developer tools. Notable is the discussion about Block Editor Handbook documentation being auto-generated from trunk rather than stable releases, causing confusion for developers. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/xPskuyyIrps?t=0) — [H1] Stream introduction and snow day delays - Key idea: Stream nearly cancelled due to heavy snowfall requiring extensive driveway clearing - Evidence: "I woke up to 800 feet of snow in my driveway... took an hour and a half" #### ⏱️ [02:15](https://youtu.be/xPskuyyIrps?t=135) — [H2] Flappy Gate incident recap - Key idea: Previous stream's malicious link incident opened 96 popup windows with inappropriate content - Evidence: "I clicked the link and then... it had opened 96 popup windows and they were all bouncing" #### ⏱️ [08:30](https://youtu.be/xPskuyyIrps?t=510) — [H1] Gutenberg 22.4 PHP-only blocks demonstration - Key idea: New Gutenberg version enables PHP-only block registration without JavaScript - Evidence: "22.4 came out... now we can get these things happening which is really cool" #### ⏱️ [12:45](https://youtu.be/xPskuyyIrps?t=765) — [H2] PHP block attributes and meta fields - Key idea: Block attributes automatically create meta fields based on type definitions - Evidence: "attributes based on the type string, integer, boolean, string and this enum. It was creating meta fields for us" #### ⏱️ [18:20](https://youtu.be/xPskuyyIrps?t=1100) — [H2] Script and style registration in PHP blocks - Key idea: Can register CSS and JavaScript directly in block registration without separate enqueue actions - Evidence: "I don't think we necessarily need to put it on the actions that you would normally encue" #### ⏱️ [25:15](https://youtu.be/xPskuyyIrps?t=1515) — [H1] Icon block development progress with data views - Key idea: Icon block now uses WordPress data views component for improved modal interface - Evidence: "I'm using data views for it. So now when you load this now we have this going on" #### ⏱️ [32:40](https://youtu.be/xPskuyyIrps?t=1960) — [H2] Documentation challenges discussion - Key idea: Block Editor Handbook auto-generates from trunk, creating confusion about feature availability - Evidence: "documentation that represents things that are not in core and that are not in the released version" #### ⏱️ [41:10](https://youtu.be/xPskuyyIrps?t=2470) — [H3] Block proliferation and enterprise concerns - Key idea: Better to disable unneeded blocks than build missing ones for client projects - Evidence: "it's better to have to disable a block than it is to have to build one" #### ⏱️ [46:30](https://youtu.be/xPskuyyIrps?t=2790) — [H1] VS Code Interactivity API extension demo - Key idea: New extension provides autocomplete for WordPress Interactivity API directives and state - Evidence: "when I hit state, I get prompted with the items from the state" #### ⏱️ [52:15](https://youtu.be/xPskuyyIrps?t=3135) — [H2] Extension features walkthrough - Key idea: Extension validates store names, detects duplicates, and parses view.js files - Evidence: "it'll actually tell you, hey, there's no store name dev inspector" #### ⏱️ [58:45](https://youtu.be/xPskuyyIrps?t=3525) — [H3] Talk Devi to Me podcast concept - Key idea: Proposed stream format for developers to showcase their projects - Evidence: "people are going to come on and we're going to talk about the thing they're building" #### ⏱️ [63:20](https://youtu.be/xPskuyyIrps?t=3800) — [H2] AI development tools discussion - Key idea: Used Claude and Nano Banana to build VS Code extension in two days - Evidence: "I built this with Claude Code in like two days and I'm super excited with it" #### ⏱️ [68:40](https://youtu.be/xPskuyyIrps?t=4120) — [H2] Community member Paul joins discussion - Key idea: Real-time collaboration on PHP Storm extension conversion and WordPress core contributions - Evidence: "Paul wants in... you're going to take that thing that I did and you're going to get AI to convert it" ## 📚 References - [Gutenberg Plugin](https://wordpress.org/plugins/gutenberg/) - [WordPress Developer Handbook](https://developer.wordpress.org/) - [VS Code Marketplace](https://marketplace.visualstudio.com/) - [WordPress Interactivity API](https://make.wordpress.org/core/2024/03/04/interactivity-api-dev-note/) ## 🗣️ Paraphrase - Gutenberg 22.4 enables complete PHP-only block development without JavaScript build processes, making WordPress block creation more accessible - Documentation challenges arise from auto-generation based on development trunk rather than stable releases, causing confusion about feature availability - New developer tools like VS Code extensions can significantly improve WordPress Interactivity API adoption through better autocomplete and validation ## 📰 Newsletter 🎉 **PHP-Only Blocks Now Live in Gutenberg 22.4!** Great news for WordPress developers who prefer server-side block development! The latest Gutenberg plugin update makes PHP-only blocks fully functional. You can now register blocks with attributes, styles, and scripts entirely in PHP without touching JavaScript build processes. This is a game-changer for developers who want to create custom blocks but don't want the complexity of modern JS tooling. Simply define your block attributes, and WordPress automatically creates the corresponding meta fields. **New Developer Tool Alert:** Check out the new VS Code extension for WordPress Interactivity API development, featuring intelligent autocomplete for directives and state management. **Resources:** - [Learn WordPress](https://learn.wordpress.org/) - Official training platform - [Developer Docs](https://developer.wordpress.org/) - Technical documentation - [WP-CLI](https://wp-cli.org/) - Command line interface Join the conversation in WordPress community Discords and forums to share your PHP-only block experiments! ## ✅ Action Items #### DevRel - Community engagement: Host "Talk Devi to Me" developer showcase streams - Education: Create tutorials for PHP-only block development workflow - Developer experience: Address documentation gaps between Gutenberg plugin and core - Developer marketing: Promote new VS Code extension for Interactivity API - Community management: Moderate stream chat with improved link filtering #### WordPress - Core: Validate PHP-only blocks functionality across WordPress versions - Documentation: Consider versioned docs to separate trunk from stable releases - Community: Support developers transitioning from JavaScript to PHP-only workflows - Plugins: Review extension approval process for developer productivity tools - Design: Improve data views component integration in block interfaces #### Community - Maintainers: Gather feedback on PHP-only blocks implementation - Contributors: Test new development workflows and report issues - Sponsors: Support developer tool creation and maintenance - Ecosystem: Document best practices for PHP-only block patterns ## 🧪 Hypotheses - PHP-only blocks will increase WordPress block development adoption among backend-focused developers - VS Code extensions can significantly reduce Interactivity API learning curve through better developer experience - Documentation generated from trunk rather than stable releases creates unnecessary developer friction - Community-driven developer tools fill important gaps in official WordPress tooling ### 📊 Methodology - Survey developers about PHP-only blocks adoption rates before and after 22.4 - Track VS Code extension downloads and user feedback metrics - Analyze documentation-related support requests and their resolution patterns - Monitor community Discord discussions for common development pain points ### ❓ Questions - Will PHP-only blocks reduce JavaScript build tooling complexity concerns for new developers? - How can WordPress core better communicate feature availability across plugin and core versions? - What additional developer experience improvements would accelerate Interactivity API adoption? ### 🔮 Future Research - PHP-only blocks performance compared to JavaScript-built blocks - Developer productivity gains from specialized WordPress extensions - Community-driven vs official tooling effectiveness in WordPress ecosystem ### 💡 Implications - Practice: Simplified block development workflows may increase community contributions - Policy: Documentation versioning strategies need reconsideration for developer clarity - Education: Developer onboarding paths can focus more on PHP skills initially - Funding: Community tool development deserves support alongside core WordPress funding ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade (technical developer content) #### 👀 Visual learners - Present: Live screen sharing, code demonstrations, extension interface tours - Improve: Architectural diagrams for PHP-only blocks, data flow visualizations #### 🔊 Aural learners - Present: Live stream format with verbal explanations and community discussion - Improve: Recorded tutorials, podcast format for complex topics #### 🗣️ Verbal learners - Present: Interactive chat, technical terminology explanation, analogies - Improve: Glossary of WordPress-specific terms, comparison tables #### 🧩 Kinesthetic learners - Present: Live coding demonstrations, step-by-step implementation - Improve: Downloadable code samples, hands-on workshops #### 🧠 Logical learners - Present: Sequential development process, cause-and-effect relationships - Improve: Decision trees for block development approaches, performance comparisons #### 🧑‍🤝‍🧑 Social learners - Present: Live chat interaction, community Discord integration - Improve: Collaborative coding sessions, peer code reviews #### 🧘‍♀️ Solitary learners - Present: Individual coding time, personal project development - Improve: Self-paced tutorials, documentation deep-dives #### 🌿 Naturalistic learners - Present: Real-world problem solving, organic community conversations - Improve: Case studies from actual WordPress sites, ecosystem impact analysis ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Live stream with verbal descriptions of visual elements - Improve: Alt text for shared code screenshots, structured heading hierarchy #### Keyboard navigation - Present: Demonstrated VS Code keyboard shortcuts and workflows - Improve: Document keyboard-only development workflows #### Contrast and readability - Present: High contrast code editor themes during demonstrations - Improve: Verify code example visibility across different displays #### Media and captions - Present: Live stream with audio commentary - Improve: Auto-generated captions, post-stream transcriptions available #### Standards reference - Follows WCAG 2.2 AA guidelines for live streaming accessibility ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global community participation through chat and Discord - Improve: Acknowledge different time zones for stream scheduling #### Inclusive language - Present: Gender-neutral technical terminology, welcoming tone - Improve: Define technical jargon consistently, avoid cultural idioms #### Neurodiversity support - Present: Multiple communication channels (audio, chat, visual) - Improve: Provide agenda/outline for streams, consistent structure #### Representation - Present: Diverse community member participation and recognition - Improve: Highlight contributors from different backgrounds and experience levels #### Psychological safety - Present: Respectful handling of technical mistakes, learning-focused environment - Improve: Clear community guidelines, escalation paths for issues ### ✅ Logical Validity #### Strong reasoning - Deductive strength: PHP-only blocks reduce complexity → increased adoption (valid premise, sound conclusion) - Inductive strength: Documentation confusion examples → systemic issue (multiple data points support generalization) - Causal reasoning: Gutenberg 22.4 release → PHP-only blocks functionality (direct causation established) - Analogical strength: VS Code extension success → PHP Storm extension potential (reasonable parallel) #### Fallacies - Appeal to authority: "It's better to have it and not need it" - presented as universal truth without context - Hasty generalization: Documentation issues from single experience - needs broader data #### Tone of voice - Overall tone: Enthusiastic and community-focused with technical expertise, occasional casual humor ### 🛡️ DARVO Analysis - Deny: No denial patterns present in technical discussion - Attack: No attacks on accusers - collaborative problem-solving approach - Reverse victim/offender: Not applicable to technical content - Emotional cues and rhetoric: Positive enthusiasm about community contributions and technical progress ## 🎯 Conclusion - Gutenberg 22.4's PHP-only blocks represent a significant accessibility improvement for WordPress block development - Community-driven developer tools like the Interactivity API extension demonstrate the value of grassroots innovation - Documentation challenges between plugin and core versions need systematic solutions for better developer experience ## 🧱 Refactor Appendix ### 📚 Literature Split Pad ### [H1] PHP-only blocks enable server-side WordPress development > [!quote] [Just chatting and clicking random links!](https://www.youtube.com/watch?v=xPskuyyIrps) by [[Ryan]] via [[Twitch Stream]]. Published 2024-12-28. Accessed 2024-12-28. > "22.4 came out... now we can get these things happening which is really cool" Gutenberg 22.4 enables complete block development without JavaScript build processes. [view highlight](https://youtu.be/xPskuyyIrps?t=510#H1) #gutenberg #php-blocks ID:rw_001 ### [H2] Documentation auto-generation creates developer confusion > [!quote] [Just chatting and clicking random links!](https://www.youtube.com/watch?v=xPskuyyIrps) > "documentation that represents things that are not --- ## Full Transcript [03:48] Hello everybody. Microphone. Microphone. [03:51] Ryan. Need the microphone. Hello [03:52] everybody. [03:54] How's it going today? Hey Paul. Hello. [03:57] Hello Paul. Paul. Hello. [04:01] Um [04:05] yeah. Cool. Hi. How's it going today? [04:07] I'm all over the place. I woke up to 800 [04:10] feet of snow in my driveway. Um, so I've [04:13] been shoveling and snowb blowing the [04:15] snow all morning. Took an hour and a [04:16] half to get our our driveway done. It [04:18] was ridiculous. And it's snowing heavily [04:19] right there now. Uh, yes, you did miss [04:22] the fun last week, Paul. Um, I have [04:24] scrubbed it from the internet, [04:27] but um there's there's a couple of [04:29] shorts up there that that sort of uh um [04:33] had to turn off all your content [04:35] filters. [04:38] Ah, it's going to be one of those. I'm [04:40] never going to live this down. If I [04:42] could ever find my mouse, [04:46] >> that [04:50] that might be the best comment so far. [04:53] Hello from YouTube. I'm sorry I cannot [04:57] pronounce say your username. Um, but hi [05:00] and welcome to the stream. We're over [05:02] here in Twitch hanging out. [05:05] Um, I barely made it into stream today. [05:07] Like I was saying, I had a ton of snow [05:09] out there. My my neighbor uh whose snowb [05:10] blower broke yesterday, I had to go help [05:12] her and her daughter dig out. Uh, too [05:15] too bad. What was the link? Kevin. [05:19] >> Kevin. [05:20] >> Kevin. [05:22] Oh, it was [05:27] >> Kev XB. Um, it was it was it was quite [05:31] the link. I'm sure someone will show up [05:33] in chat and drop it. Uh, but that was it [05:36] was like the most I'll never trust the [05:39] link. In fact, after that I I I changed [05:42] my settings so I don't think anybody can [05:43] drop links in chat [05:46] because I I don't trust myself. [05:49] It was Kevin. [05:52] It was the most intense experience ever. [05:56] I clicked the link and then there was [05:58] like this thing as oh it's a Flappy [05:59] Warrior clone. clicked it and then n [06:01] Okay, so I was scrubbing my computer [06:03] with bleach and uh I I found it had [06:06] opened 96 popup windows and they were [06:09] all bouncing and moving and I and I [06:11] realized that that you guys probably [06:13] didn't hear this because I I don't think [06:14] I had the uh my browser routed in the [06:18] audio, but all the stuff that was being [06:21] shown there was screaming audio so loud [06:24] and so like my reaction was was instant [06:27] fear. I peed a little. It was horrible. [06:29] Uh, and it also downloaded a bunch of [06:31] images to my downloads folder that I'm [06:33] like, you know, [06:36] would never ever want on my computer [06:38] ever. So, yeah, it was uh I they got me. [06:41] They got me. They got me. Anyhow, but [06:45] that's not why that's not why I'm here [06:48] today. [06:52] Oh, [06:53] I think I I've been streaming now for [06:55] about four years. I'm going on five [06:57] years. And uh that's the first time it's [06:59] ever happened. So knock wood. That'll be [07:01] the last time it's it's ever happened. [07:02] It ever happens. Oh, but uh so I don't [07:05] have a lot going on today. Um I am [07:06] looking for there was a new version of [07:08] Gutenberg released which is very cool. [07:10] 22 22.4 came out. So I wanted to see um [07:15] if our PHP only block stuff. Um if you [07:19] remember last week before [07:22] Oh, we got to come up with a flappy bird [07:24] gate. Flappy gate. Let's call it flappy [07:26] gate. We we we we need a name for the [07:28] thing that happened. Um so throw some [07:32] names. You know what? Let's do a poll. [07:34] Actually, throw some names in chat and [07:36] and we'll come up with it. And I'm I'm [07:38] going to do like some emotes and stuff [07:40] and I'm going to really milk this for [07:42] all it's worth. [07:44] And if you haven't seen the short that I [07:47] put together on it, please go look at it [07:49] because I'm very proud of it. I think [07:51] it's very funny. Um, [07:55] let me see if I can find it here. Um, [07:58] it's like a little movie. It's like a [08:00] little movie. Can you guys hear that? [08:02] You guys can't hear that, can I? [08:06] Hold on. Hold on. Hold on. I might have [08:09] to turn on standby. Hold on. We're going [08:12] to show this. Where's my loop back? [08:14] There it is. So, we're going to put [08:15] Chrome on. I'm going to just pause my [08:17] music real quick. And then we're gonna [08:20] >> TypeScript type. [08:21] >> Do I want to click this link? [08:24] >> Oh my god. [08:27] >> Now, somebody way back way back in in [08:30] chat asked me to look at a a a game. I [08:34] got flapped. Who was it? Oh, new bird [08:36] game net. Okay. Stove 423. Are you still [08:38] in chat? Store 423. I don't see you. [08:43] Do I want to click this link? [08:46] Oh, it's Flappy Bird. [08:49] Oh my god. Oh my god. [08:54] >> Do I want to click this link? There we [08:56] go. That's my art. Oh my god. [08:58] >> My art movie. Ah, lost the mouse. Get [09:00] out of here. [09:01] >> That was it. So, yes, I think that's [09:05] that was that was funny. Anyhow, doesn't [09:07] matter. Okay, so what are we doing here [09:10] now? All right, right. Okay, so let's go [09:12] back into my old posts and let's see [09:14] what Okay, so this is my PHP only block. [09:16] So I kind of forget what we were doing [09:17] there. So let's take a look. So the [09:19] block is loading. Okay. So So if we [09:24] remember, let's look. Uh I got to jump [09:26] back over to [09:28] Is it in here? [09:31] I do this every time. I have to go to uh [09:35] to here. I got to go Twitch stream. I [09:37] got to go to VS Code and Okay, here we [09:39] go. So here's our our content only [09:41] block, right? So all we're doing is [09:43] registering of our our blocks directly [09:45] with register block type uh with a [09:48] namespace and then we're adding all of [09:49] these things and so the thing that why [09:51] is this being stupid? How it expected [09:55] six one two three four five six [10:01] one two three four five six now it's [10:04] okay. [10:11] Oh my lordy lordy. Right. Okay. So, [10:15] let's [10:20] anyways. Uh, [10:24] if only somebody could come up with a [10:26] way to format this for me automatically [10:28] so I didn't do this. I'm sure it's [10:30] possible. [10:34] Why is there a period in there? It needs [10:36] to go away. All right. Anyways, uh, I [10:38] have to screw down. So what we were [10:40] doing is we were defining our attributes [10:41] in here and the attributes based on the [10:43] type string, integer, boolean, string [10:46] and this enum. It was creating uh meta [10:49] fields for us. So if if you remember [10:52] last week uh uh 22.3 was still the [10:56] active version of Gutenberg and so now [10:58] we've we we got 22.4 active. It just [11:01] just came out. And so now this PHP only [11:03] blocks thing [11:05] uh now we can we can get these things [11:08] happening which is really cool. So this [11:09] is this is kind of fairly complete like [11:14] fairly complete. I think I think we're [11:16] in a position now where you just install [11:19] the Gutenberg plugin and you're able to [11:21] do PHP only blocks. So um that's super [11:25] powerful. Super powerful. And we also [11:27] discovered that you can still in in quue [11:29] JavaScript [11:31] and add handles and stuff. So what I was [11:33] actually thinking about this was [11:37] I was in queuing I was using I was [11:39] putting this on on the actions that you [11:42] would normally put them on. But I don't [11:44] know if you if you need to do that. I [11:46] think we can just register [11:48] styles like what if we just did this. I [11:50] want to try something here. Going to [11:52] register my styles in the same place [11:54] where I'm registering the block, right? [12:02] Hey. [12:07] Oh, man. It's such a good song. Uh, [12:10] great to see you. Also, [12:13] let's see if this works. So, I I've [12:15] taken out the Oh, I need to get that. [12:18] No, I need to get that CSS file. So, [12:20] we're going to see. So this should be [12:23] registering some CSS [12:26] for us and a script and the script [12:30] is what's okay. So what test CSS what [12:33] does it do? It makes the title big and [12:37] this just alerts something I think. [12:40] What is all this crap? [12:47] Weird. Okay, we're gonna Oh, I know what [12:50] I what I did there. I'm going to do [12:51] that. So what I just want to I want to I [12:53] want it to alert. Hi with two I's and [12:57] two J. Sure. Why not? Why not? You know [12:59] why not? And now we shouldn't have to [13:01] build anything. [13:03] Oh, okay. So that worked. [13:06] That worked multiple times and it's [13:09] doing that. So let's see. So where did I [13:13] So script handles styles handles. [13:19] Oh, I get it. So the script script [13:20] handles. So, [13:22] these are getting loaded on both. That's [13:26] cool. All right. And this one, what is [13:28] this one? What's the editor? So, editor. [13:31] Um, I should be able to do the same [13:33] thing, [13:35] right, with the editor. I should be able [13:36] just to drop it in here. Um, the reason [13:39] I'm doing this is because I don't think [13:41] we necessarily need to, um, you know, [13:44] put it on on on the actions that you [13:46] would normally encue the actions on [13:48] because we're just registering the [13:49] script. And so because the point of it [13:53] is you register these scripts and then [13:55] you can you could define script handles [13:57] and styles and whatnot for for editor [14:00] and for the uh front end with these [14:03] arrays. So you could still get your CSS, [14:07] you can still get your JavaScript into a [14:09] a PHP only block. I think that's pretty [14:11] powerful. Let's just make let's make [14:13] sure it works though. [14:17] We know that works. We know that works. [14:20] It's loading twice though, which I don't [14:21] like. Am I doing it twice? [14:28] That's a good question. Um, that's a [14:30] really good good question. I mean, the [14:32] way that these work is that [14:35] this should only be per block, I would [14:38] imagine. Let's check. Let's take this [14:40] out. Save. [14:43] We'll refresh. [14:46] Uhoh. [14:49] Huh? [14:51] Wonder why? [14:53] Why? Oh. Oh, that makes sense because [14:56] the block is actually being loaded. It's [14:58] just not in there. Okay. Okay. So, let's [15:02] let's put the block back. Can I undo [15:04] what? Custom. [15:07] Uh, what is the name of the block? Crap. [15:11] Yeah, that's that's annoying. Okay, [15:14] that's annoying. [15:16] Okay, screw off. [15:18] That needs to go away. Okay, so we know [15:20] that that works. So, what was the name [15:22] of this block? That's the thing. Twitch [15:23] something or other. Let's find out. We [15:26] called it my custom title. Okay, so [15:27] we're going to do my custom title. So, [15:31] we're going to put that in. So, that's [15:32] getting the CSS there. [15:37] >> It is Troy Shaplin. Okay. So, that's [15:40] getting the CSS. And so now let's put [15:42] this [15:44] let's put this back. [15:47] And that's that and that's loading that [15:49] there. So that does only load on the [15:51] front end. So if I get rid of this and I [15:53] save this and I refresh this. Okay. So [15:57] the JavaScript does is not being loaded [15:59] on on the front end. Um [16:02] which is good. So uh let's see let's [16:05] check the sources too because we can see [16:07] where the sources are. Uh just ignore [16:10] that. I don't know what that is. [16:13] Let's look for sources. Let's look for [16:14] page. Let's look for blocks. Page only [16:17] blocks. [16:19] Um, [16:20] so I I don't see any scripts being [16:25] loaded because the block's not there. So [16:27] I So yes, I know I what? No, no, no, I [16:31] didn't. It's right there. It should be [16:33] alerting. Um, [16:38] what error am I getting? [16:42] weird. Okay. But if we put it back, if I [16:45] put that block back in and I save it and [16:47] I refresh this, I should get that that [16:50] popup. Yeah, I do. Okay. So, now if we [16:51] look at the sources, you can Where are [16:53] the s be content plugins? I was looking [16:56] in the wrong place. Assets. So, we're [16:58] getting JavaScript. Yep. We're getting [17:00] CSS. Yep. Let's take it out again. Save [17:05] it. [17:07] Refresh. [17:10] page content. Okay. No, so it does not [17:14] get loaded on the front end. Um, [17:17] regardless of where you're registering [17:19] it. That's pretty nice. So, yeah, [17:21] because we're not actually in quueing it [17:23] in our in like this code is not incuing [17:25] anything. All this is doing is this is [17:27] registering those. So then once we have [17:29] those those uh those those slugs or [17:32] whatever we're calling them, um you just [17:34] pass them in here and then and then bing [17:37] bong bang, you've got uh porn in your [17:40] chat. That that's that that's a new [17:44] saying that I'm going to start coming [17:45] out with. Um that's like, you know, [17:48] Bob's your uncle, Robert's your father's [17:50] brother. Bang, you got porn in your [17:51] chat. Same thing. See, you like it. I [17:53] love it. Let's do it. [17:56] Um, blast nastier. [17:59] Hello from Portland. Uh, hello from [18:02] Canada, Ontario, Canada. Um, glad you [18:06] could join. Thanks so much for hanging [18:08] out with us today. Are you first time [18:10] chatter? You are first- time chatter. [18:11] Nice. Well, thank you for the chat and [18:14] uh, welcome. Welcome aboard. Welcome [18:17] aboard. Okay, so that's pretty cool. So, [18:19] go and download Gutenberg 22.4 before [18:21] came out I think on Tuesday and now you [18:23] can do blocks is cross keys here. He's [18:25] going to love all this. Um he's going to [18:29] love all this. Uh you know I you know [18:31] what I didn't do? I didn't announce my [18:32] my stream anywhere. I'm going to do [18:35] that. Just going to open up Discord [18:39] and drop some some links in there [18:46] because you know why not? Why not? [18:48] Really? Why not? [19:09] Uh, [19:10] do I have do I have I have this open? [19:12] Yeah. Outreach. So, um, yeah. So, the [19:15] other there's there are something else I [19:17] I I wanted to there's a couple more [19:19] things I I Yeah, I just don't click any [19:20] links. Exactly. Couple more things I [19:23] wanted to uh just chat about today. And [19:27] what were they? Um [19:30] Oh, uh [19:32] oh crap. I had I had all these great [19:34] ideas. New version of Gutenberg came [19:36] out. I think I don't know where the post [19:38] is. I can't find it. Um because that [19:42] that would be good to have. Let me just [19:44] see. Boom. [19:46] Oh, it's it's still in review. Okay. [19:49] It's not quite [19:51] uh [19:53] it's in review. [19:56] Okay. So, it's not quite ready to go. [19:58] So, like every every time that there's a [20:00] version of Gutenberg that comes out, [20:01] there is also a corresponding uh what's [20:03] new in Gutenberg link. Um and uh yes, I [20:07] wanted to uh [20:11] Oh. [20:29] Oh my god. I can't type. Sorry. It's no. [20:31] Okay, cool. Um, right. So, that's that. [20:34] I think I I just messaged Cross Keys [20:36] because he's literally talking about [20:37] this in one of the Discord chats about [20:39] like, "Has anyone done this?" Uh, cool. [20:42] But the other thing is, what is the [20:45] other thing? [20:47] Uh, okay. It's not in there. It's not [20:49] there. It's not there. It's not in [20:49] there. Ply box plug in Gutenber. Oh, [20:52] great. Okay. So, I've been working on [20:54] the icon block again. And I'm super [20:57] excited about the uh about the work that [20:59] we've sort of um uh been able to to to [21:03] get done. So, I I I want to kind of show [21:05] you y'all the some of the um uh some of [21:10] the work. So, uh, the icon block now has [21:14] width and height settings, which is [21:15] super nice because those were merged [21:17] into core. So, I'm I'm using those. Um, [21:20] the other thing now is is I've made some [21:23] changes to the modal. So, the modal that [21:26] that that was in Nyx plugin, which is [21:28] great, was custom. Um, [21:32] oh my god, it's been a week already. [21:33] Yes, it has. Um, so it's been it's been [21:36] custom. It was a custom once, but I'm [21:38] using data views for it. So now when [21:40] when you when you load this now we have [21:42] this going on and I'm super excited [21:45] about this. This is so cool. So um you [21:48] you can sort you can do all kinds of [21:50] things. We can show number you know all [21:52] these things. We can hide certain stuff. [21:54] Um so it's very much a work in progress [21:56] but we're getting so much closer. And [21:59] there's an API for icons that is being [22:02] worked on uh sim simultaneously which is [22:06] a word that I didn't say properly. But [22:09] if we look at my uh my my poll requests [22:13] my poll requests for here the icon block [22:16] I can link to the other one [22:22] right here. You can see where this is [22:24] going. So th this is the work that's [22:27] being done on the uh [22:31] oh I don't know who who [22:36] yeah seems like only yesterday I was [22:38] checking out that link. So this so go [22:40] check out this. So this is going to be [22:42] this is the work that's been done on the [22:44] um on the what you call it the the the [22:46] icon API the ability to register icons. [22:50] So, what that meant for me with the icon [22:52] block is that meant that things got a [22:54] lot simpler because Nyx block does a lot [22:57] of really or did a lot of really cool [22:59] things. Uh, it allowed you to upload [23:01] SVGs. It allowed you to copy and paste [23:04] SVGs, but because we have this API [23:06] coming um and they're very much these [23:08] are very much connected at the hip. So, [23:10] if the API [23:12] doesn't make it to 7.0, this doesn't [23:15] need to be there. Um, then this block [23:18] won't make it to 7.0 0 either, but um [23:21] we're working hard on it. So, it means [23:24] So, anyway, so what it means is that we [23:25] I can remove all that stuff. So, we're [23:27] not going to have the ability to copy [23:28] and paste SVGs. We're not going to have [23:29] the ability to upload SVGs because that [23:32] was always going to be a sticking point [23:34] always because SVGs and core have always [23:36] been a problem because they're very hard [23:38] to validate and they're very easily [23:41] manipulated and they could be attack [23:43] vectors for um hackers and all sorts of [23:46] fun stuff. So, so having core enabled [23:49] that is probably going to be a problem. [23:50] But anyway, so it mean meant that I can [23:53] strip out a ton of code. Uh, yeah. And [23:55] so I I I've been focusing on on this [23:57] thing, which I think is great. It's [23:59] going to be so much fun. It's my first [24:00] real foray foray into data views. Here's [24:03] my tangent interrupting for the stream. [24:04] Okay, bring it. Bring it on. Cross keys. [24:08] Um I I I I wanted to mention but just [24:12] before you you came on we actually had [24:15] um [24:16] 22.4 uh Gutenberg uh came out. [24:22] Uh and so now now all of these all these [24:25] attributes that we were doing before now [24:28] work now now they register the blocks. [24:30] So okay so here here is the question. [24:33] Hey Mr. Gutenberg. Oh my god. Are you [24:35] calling me Mr. Gutenberg? That's [24:38] hilarious. Um, [24:41] you can Well, you can bother anybody. Do [24:45] you have an issue? [24:50] Yes. Yes. There is a really great post [24:52] about about the data view on on on the [24:54] developer blog. I believe it's the the [24:56] developer blog. You can check this out [24:57] right here. Yeah, it just came out. It's [24:59] really great. Go check that out. One [25:01] thing that I found very confusing about [25:04] it was there's a lot of moving parts. [25:06] Um, [25:08] there's a lot of move moving parts with [25:09] this, but once you kind of wrap your [25:10] head around how the pieces fit together, [25:12] it's it's super powerful. [25:15] Yeah, the Goodword Docs already merged [25:17] to the core block editor handbook. Yes, [25:19] there are. That is a correct statement. [25:23] So, if you want to make changes to the [25:26] docs for the block editor handbook, you [25:28] you would do Hey, Mr. Hey, [25:31] Mr. Gutenberg, I need a I need a shirt [25:34] or something that says that. Um, [25:40] hey Philipe, how you doing? [25:43] Um, [25:46] okay. There's a number of things going [25:47] on right here, but I'll answer questions [25:49] as I can. The other thing, all right, [25:52] somewhere there's a person trying to out [25:54] block it or losing his mind because he's [25:55] trying to use the autoregister key and [25:56] it's both doing nothing and throwing no [25:58] errors. Oh, that's what you're saying. [26:00] Okay. First of all, I feel your pain. [26:04] 100% feel your pain. The the the the the [26:09] one one issue that has always been an [26:11] issue with the block editor handbook is [26:13] because it's merged because when things [26:16] are merged, it autogenerates every time [26:19] something's merged in into trunk, you [26:21] get into a position where you have [26:23] documentation that represents things [26:25] that are not in core and that are not in [26:27] the released version of the plug-in, [26:30] right? And it is very frustrating [26:34] 100%. I I get it. Um [26:39] we have discussed a number of things [26:41] about how to how to make that happen. [26:44] The the problem that we run into is it's [26:48] a maintainability issue and this is an [26:50] excuse not a reason 100%. So we had [26:54] talked about having things so [26:56] yes so they get built on merge to trunk [27:03] which is a thing we've talked at length [27:06] my my team internally um when I first [27:09] joined and we really yeah well I mean [27:13] yes it's just the way it is just the way [27:14] it's set up right now doesn't mean it's [27:16] right doesn't mean it can't change but [27:18] it but I wanted to explain it so when I [27:20] merge anything when when But when [27:22] something gets merged to to to trunk in [27:25] Gutenberg within 15 minutes there's a [27:27] cron that runs and it it it builds out [27:30] all the documentation. A lot of that [27:31] documentation is also autogenerated [27:33] based on the source code. So um it's not [27:36] something that's just managed where you [27:38] just go in and you make a change to uh [27:40] to a page. So like if we look at [27:42] Gutenberg [27:44] um uh do I have that open? I don't where [27:47] is it? Gutenberg development. So if we [27:50] look at Gutenberg development here and [27:53] we take a look at let's take a look at [27:55] the docs. So for example docs, right? So [27:59] we're going to have let's use reference [28:01] guides. No, let's go. [28:06] I can never find it. The thing that I'm [28:08] looking for getting started. Oh, I I [28:11] know how it works. Okay, let me go to [28:13] packages. Let me go to Let's go to um [28:17] whatever the block editor. Going to read [28:18] me. So in the read me somewhere down [28:22] here. Why does it look like that? [28:25] Okay. Why does it look like this? [28:28] Something screwed up. Oh, there we go. [28:30] Okay. So, when you see this, what this [28:33] is doing is this is autogenerated by [28:35] this tool that that's called [28:42] Okay, I'll get to your question in a [28:43] second, cross keys, because it's [28:44] nuanced, but yes. So when you see this, [28:47] anything below this line is [28:49] automatically generated by this docgen [28:51] tool. So it takes all the the [28:53] documentation [28:54] and pulls out um so let's see what's [28:58] this function that we're looking at [28:59] block canvas. You know what this let me [29:02] do a better one maybe the core core data [29:05] that might be a better one. So if we [29:07] look in core data you can see that there [29:09] is all these uh some point you'll see [29:12] there so you'll see these add entities. [29:14] So this is an action right and then it [29:16] pulls out all so delete entity record it [29:19] pulls out all the parameters from the [29:20] actual doc block itself. So this is all [29:23] dynamically generated which makes it [29:25] difficult to be able to differentiate [29:27] between core Gutenberg and and in [29:30] development from a from a documentation [29:34] uh point of view. [29:36] Um so to answer Kusky's question [29:41] uh to answer this question why is good [29:43] work and good Gutenberg affecting the [29:44] block edit ed editor docs they should be [29:46] sovereign code braces that you merge [29:48] periodically um [29:51] the block editor handbook is basically [29:53] Gutenberg it's basically all the stuff [29:56] that gets introduced via Gutenberg 2 [29:58] core let's put it that way so I do agree [30:00] with you what what would be really great [30:02] is if we had the ability to toggle [30:05] between um variations of the of the [30:09] documentation. So when Gutenberg or [30:13] sorry when a new version of core is [30:14] released um then we have the docs are [30:18] built from that tag right so so 6.9 [30:23] would would build out the docs that [30:25] would be everything that's inside of of [30:27] core then when there's a new version of [30:29] Gutenberg released every two weeks we [30:31] would build off of that that release or [30:34] that tag or however that's done and then [30:36] we could have one from trunk so you'd [30:38] have essentially three versions of the [30:40] documentation, what's in core, what's in [30:41] Gutenberg, the plug-in, and what's being [30:44] worked on. Um, because I have also run [30:47] into the problem that you've run into. [30:49] I've I it's bit me when I was at Tenup. [30:51] There was this thing called render [30:52] appender for the um innerblocks [30:56] uh component that was in the docs and it [30:58] just didn't work and I couldn't figure [30:59] out why it didn't work and it was [31:00] because it was in it wasn't even in the [31:03] plug-in at the time. It had just been [31:05] merged. So, it's very frustrating. I [31:06] feel your pain. It is something that the [31:08] project has to figure out. And it's it's [31:11] there's there's technical solutions to [31:13] this. It's just a matter of like [31:16] figuring out how it's displayed and how [31:18] it works and getting someone to be like, [31:20] "Yeah, let's change this entirely and [31:22] see how much we can we we can break it." [31:24] So anyways, that's my reason. It's not [31:27] an excuse, but that is that's the the [31:29] history. [31:34] Yeah, you can totally do it. So also [31:37] explains why some of the doc contra each [31:38] other or don't acknowledge parallel [31:39] methods. Yeah. Yeah. [31:46] Yeah. So like like there's there's a lot [31:49] of under the hood stuff as well. Like [31:51] for example, it is a WordPress site. [31:52] What you're looking at the the block [31:54] developer handbook. It is absolutely a [31:56] WordPress site. Those pages are [31:58] generated. They are generated and they [31:59] are inserted. The content is inserted. [32:00] So you need to duplicate every single [32:02] page in that site like twice. you need [32:05] to have a version for core, a version [32:07] for Gutenberg, and a version for cutting [32:09] edge or even just Gutenberg and and [32:12] core. Um, so there's a lot that needs to [32:15] be figured out. It's a massive it'd be a [32:17] massive migration, massive scale, [32:21] you know, but that's a great question. [32:25] Yeah. [32:28] Yeah. [32:31] Oh, the playground devril is asking me a [32:34] playground question. I feel like I'm [32:35] getting sent up or set up. [32:42] I've working on the playground website. [32:44] What what is this? Let's uh this is the [32:47] one. While working on a playground [32:48] website, I noticed a Gutenberg modal [32:51] component using divs. Is there a plan to [32:52] migrate it to a dialogue component [32:55] because it's supported by 90% of the [32:56] browsers and a lot of stuff is [32:57] implemented on the browser side? I don't [32:59] know. That's a good question. H have you [33:00] have you taken a look in at the like I I [33:02] think it's worth opening up an issue. Um [33:08] I think it's definitely worth opening up [33:10] an issue. Let's see. Um let's do search [33:13] and issues because there may not be one [33:16] but and if there isn't I think it's [33:17] worth it's worth looking at. What is it? [33:20] uh [33:22] dialogue [33:25] component. [33:28] I spell it wrong. [33:32] Yep. I don't see any anything. I would [33:35] I' I'd go open an issue and and just [33:38] start the conversation, right? [33:42] The dialogue HTML tag is not in it. [33:53] dialog wrapper. [33:58] Did Did I put dialogue in? Oops. Oops. [34:02] Oh, new block dialog popup. Is this it? [34:22] So there is this issue [34:24] um if you want to take a look that even [34:27] more core core blocks that invited [34:31] themselves in. Um okay is that that [34:36] that's a statement. Yeah. um cross keys [34:40] the the thing about Gutenberg and the [34:42] thing about the the blocks is that [34:46] like [34:49] there's there's a there's I don't know [34:51] this is my opinion but I know that there [34:53] are a ton of blocks right it's just it's [34:56] a okay [34:58] yeah no and and I get it so like back in [35:01] my agency days we were like oh my god we [35:03] didn't do designs for every iteration of [35:05] whatever block right of all the embeds [35:07] of all the whatever all the icons, all [35:09] that stuff. So, it's hard, right? [35:11] Because you because when you're working [35:13] for a client, they have a very specific [35:15] like branding, [35:18] well, branding is the word I'm trying to [35:19] say. Then, like you have to you you have [35:22] to make sure that they can't make their [35:23] buttons rounded if that's if that goes [35:24] against the branding guidelines. So, in [35:27] that in that way, Gutenberg can be very [35:29] very frustrating. But on the on the flip [35:32] side of that is people that just want to [35:33] build a site don't want to be like the [35:36] like they need to have the tools to [35:38] build what they want, right? Like if if [35:41] they don't have if they can't embed [35:43] something on it, like I keep bringing up [35:44] embeds because I know that you're [35:46] talking about embeds in the Discord, but [35:47] I mean like if if they can't do what [35:49] they want to do, they're going to go [35:50] somewhere else, right? Um, so it's it's [35:52] a balancing act between like [35:56] giving authors what they want and and [35:59] then also like, you know, not inundating [36:01] people with with things. So, I mean, I [36:04] don't think it's a bad thing to disable [36:06] the blocks. I mean, it's easier it's [36:08] better, let's think of it this way. In [36:10] my opinion, it's better to have to [36:12] disable a block than it is to have to [36:13] build one that that they don't have [36:15] because disabling blocks is a lot a lot [36:18] less work. [36:20] Full stop. Mic drop. Whatever. I don't [36:22] know. [36:24] Cool. Um, [36:31] yeah, exactly. You just like turn them [36:33] all off and just, you know, bring them [36:36] back as as needed. I mean, like when [36:38] when you're when you're working at the [36:39] enterprise level, when you're working at [36:41] a big level, you're turning off a lot of [36:42] WordPress stuff anyways. Like so many [36:45] themes starters and scaffolds and stuff [36:47] like that, they turn off stuff, you [36:49] know, like maybe they don't want the [36:50] rest API. They just turn it off. Like [36:52] whatever. I mean the public, right? Oh, [36:56] I kind of dated myself because I don't [36:57] think you can turn it off now, but [37:00] unless you do that, the rich content [37:01] equivalent of the Homer Simpson card is [37:03] like, yeah, well, but that's just it, [37:04] right? You have to just get yourself to [37:07] a place where where where you need it. [37:09] So, I love the idea of it's better to [37:12] have it and not need it than to need it [37:14] and not have it, [37:16] you know? So, I don't ever think I'm [37:19] going to use a third like twothirds of [37:21] the blocks that that we're shipped with. [37:23] But that one time when I want it, it's [37:25] there, right? That's what I think. And [37:29] it's not hard to turn stuff off. It's [37:31] way harder [37:33] uh to to build out something and [37:36] maintain it too, right? Because the more [37:38] blocks that core builds, the less blocks [37:39] you have to build and the less blocks [37:41] you have to maintain. And with block [37:43] variations and block bindings and stuff, [37:45] that gets super powerful. [37:49] Yeah, you should absolutely do that, [37:50] Troy. Even if it's a snippet. So, uh, [37:53] the developer blog has like full [37:54] articles like this, but it also has [37:57] snippets which are super helpful. Um, [38:00] like how do I hide how to register a [38:02] blog variation, but hide it from the [38:03] inserter? See, that's what I did, right? [38:07] just little block uh variations. There's [38:09] lots of stuff in there. Uh snippets and [38:10] it's just like small little chunks of [38:12] code that can be helpful. There you go. [38:14] Go check those out. Pretty hardcoded, [38:16] but I've only had to do three CSS hacks [38:18] so far. Yeah. I mean, and if you find [38:20] something that's hardcoded and and and [38:22] you and you've got a valid reason for it [38:24] not to be hardcoded, then I mean, open [38:26] up an issue that it's not it's not like [38:29] you have to live with the way it is. I [38:32] mean, it's an open source project. I [38:33] mean, I realize it's hard to, you know, [38:35] not everybody has the time and and the [38:38] and the inclination to go and do it, and [38:40] I get that and that's cool. But I'm just [38:41] saying if you if you're having the [38:42] issue, someone else probably is. And if [38:44] you open up an issue with a potential [38:46] like, why don't we do it this way? You [38:48] know, like come to to the table with an [38:50] idea, and that's usually the way that [38:52] things get moved forward, right? [38:56] I built something similar in my [38:57] validation plugin when you can run a [38:58] validation in the editor and turn them [39:00] off in the side editor. Shouldn't be [39:01] hard to set that up for blocks. Yeah, [39:02] cool, cool, cool, cool. Um, okay. So, we [39:06] talked about Oh, yeah. So, we talked [39:07] about this. So, yeah, if you're [39:10] interested in following along or you [39:11] have or you have any ideas about this, [39:15] um, then I would love [39:18] I would love your [39:21] feedback on here. That's the issue. [39:24] Yeah, Troy, talk about your validation [39:26] plugin. Oh, I have an idea for a new [39:30] thing. um for the stream and I'm going [39:34] to start it with my with Rob who is um [39:38] with WP Rig and we haven't figured out [39:40] when we're going to do it yet, but I [39:42] he's he's going to come on the stream [39:43] and he's gonna we're gonna he he's going [39:44] to talk we're going to talk about it. [39:46] We're gonna hang out. So, I have this [39:47] idea. I It's a great name for a podcast. [39:49] I think it's called Talk Devi to Me [39:53] and the idea is people are going to come [39:56] on and we're going to talk about the [39:57] thing they're building and they can talk [39:59] Devi to me. So that's the idea. So Troy [40:02] Troy's got a couple of things in the [40:04] works which I I don't know if I'm [40:05] allowed to talk about them or not, but [40:06] his validation plugin, I think you [40:08] should definitely come on and talk about [40:09] it. And that thing you sent me, the [40:11] interactivity API thing that you're [40:13] working on, that would be cool when [40:15] you're ready for that. [40:17] Oh, [40:21] Troy can't send. Okay, so the links are [40:24] getting stripped out. That's that's [40:26] fine. [40:28] Um, [40:30] how can I allow that link? [40:34] Think I might need to change that. [40:36] I removed links for obvious reasons. So, [40:40] if you want to DM, um, [40:45] if you're in the Discord [40:48] Oh, why did AOL do Oh, Kevin, I think [40:50] it's because you're a moderator. [40:53] Yeah, [40:56] I I I I'll have to look look at that. [40:59] But if you're in my Discord, [41:01] um [41:03] drop drop the link in the Discord. Um it [41:07] might even be in there. [41:10] Yeah, if you drop the link in the [41:11] Discord, um [41:14] what you call it, your name is Troy, [41:16] then I can drop it in chat and and [41:18] that'll be fine. or if you want to just [41:20] go to my discord and we and we can share [41:22] stuff there, there's a uh show us the [41:24] goods page where you guys can can uh [41:28] drop your stuff in there. So, if you're [41:29] not on my discord, you can get there [41:33] right here. [41:36] You can you can go there and you're [41:39] welcome to join. It's not super active, [41:41] but I think I might try to channel some [41:43] of my my my link sharing there um just [41:47] to just to keep the porn to a minimum. [41:50] Uh but in anyways, yeah, cool. So, [41:52] that's that's what I was thinking. So, [41:54] if you guys are if anybody's got [41:55] anything that they want to share that [41:56] they want to talk about, um be cool to [41:59] have you on the stream and we and and [42:00] and we can chat about it. Um all right. [42:03] So, the next thing that I want to show [42:05] you guys is something that I've been [42:06] working on. Uh, I built it yesterday and [42:09] it is a extension. Where's my extension? [42:13] Right here. It's called [42:16] and uh [42:18] I I I built this with with Claude Code [42:21] in like two days and I'm super excited [42:22] with it. It's my first real like um [42:29] uh like real vibe code whatever thing. [42:31] It's got two downloads. Anyways, what [42:34] this is doing is this is for the [42:35] interactivity API. So, the idea behind [42:37] it is that if you're working with the [42:39] interactivity API and I open up a [42:40] render.php [42:42] and I can see I I I get told uh oh no, [42:46] where is it? TS. [42:54] Um what it it does for you is it does [42:56] autocomplete. So, you can autocomplete [42:58] each one of the the um directives. But [43:02] something that I'm really proud of is [43:03] that if you have stuff in in in state [43:05] Oh, is this not working now? Of course [43:06] it's not working now. Is this one not [43:08] have state? [43:10] Where is it? TS. No, there's no state. [43:13] Uh item one, [43:17] item [43:18] two. Right. So what should happen here [43:21] is when I hit state, I get prompted with [43:24] the items from the state. So if I have [43:26] callbacks for example or action come on [43:31] actions [43:33] if I go on there we go. So so it's it's [43:36] it's inspecting my uh view my my view uh [43:39] file and finding this. Um [43:43] so the and it uh so I'm super excited [43:46] about this. So if you're interested it's [43:47] it's available for for download if [43:49] you're working with the interactivity a [43:51] API. I'd love some feedback on it. Um [43:54] because what I want to make this what [43:56] one thing that bugs me, not bugs me, but [43:58] I struggle with like remembering all the [43:59] directive names. I struggle with making [44:02] sure I I can remember what the name of [44:04] my of my callbacks are. And so the whole [44:06] point of this is to make it so that's [44:08] not an issue anymore. Right? So now I've [44:10] got that. Um the other thing it does is [44:14] if you've worked if you've screwed up [44:15] the name of your uh of your store, it'll [44:19] actually tell you, hey, there's no store [44:20] name dev inspector. D [44:23] And so you can figure that out, right? [44:26] So it inspects your VTS. It works with [44:28] with JS files, all that stuff. Um, oh, [44:31] and the other thing it does is detects [44:34] duplicate [44:36] um [44:39] duplicate uh directives, which is pretty [44:43] cool. So if you were to do like a like [44:46] like one of these, the other thing it [44:48] does, so there's a there's a couple of [44:50] ways it handles it. So you can actually [44:52] add a you can add a um a unique [44:57] identifier to the end by going like [45:00] three dashes and then say what other one [45:02] or whatever right and so that will [45:04] actually make it valid. [45:07] So yeah I don't know I'm super excited [45:10] about this mostly because I wrote it in [45:11] in in code like after hockey one night. [45:15] So, yeah. [45:19] So, if you're interested, you can [45:21] download it um by getting this. How do I [45:25] Here's where's the store page? [45:28] How do you get to the store page? [45:36] Neoim. Um maybe I don't know. Could look [45:39] into it. How do we get the stupid store [45:42] page? Um, [45:49] copy link. Is this it? [45:54] Yeah, there you go. So, go download go [45:56] and download this. There is a repository [45:58] for it. Um, please let me know if you [46:02] run into any issues or any anything. The [46:05] whole point of this is to be as e to [46:07] make it as easy as possible to adopt the [46:10] interactivity A API. Um, like I said, it [46:12] works with TypeScript. It works with uh [46:14] just regular JavaScript. [46:17] Um, so yeah, [46:20] bad dude, you're doing a ton with it, [46:21] right? That's the Did I Oh, I already [46:24] linked that. Sorry about that. Um, yeah. [46:26] So, I mean, I I'm going to put something [46:28] up on the socials today. I I I know [46:30] there there are some some hardcore um [46:34] interactivity API developers out there. [46:35] I think you're one of them. So, let me [46:37] know. I mean, full disclosure, it like [46:42] Is it uh what's the current state of the [46:44] client side? [46:48] What's the current state of client side [46:50] full page navigation? Um well, it's it's [46:52] it's an experiment. You can add it to [46:54] you can you if you're in if you're in a [46:57] WordPress site. Oh my god. Where's the [46:59] mouse? Where's the mouse? What's going [47:00] on here? Hello. There we go. If we're in [47:04] like in here, we go to Gutenberg, I [47:06] think, and experiments. Now, God be gone [47:09] with you. [47:13] Oh, boy. Okay, I got to go to plugins [47:17] and I have to turn off this [47:20] plugin. You should be able to get if you [47:22] go to experiments and where is it? [47:27] Oh, full page client side navigation. [47:33] And I think it just [47:39] maybe not. Oh yeah, that's working. [47:44] Yeah, so it it works. Um, it's it's uh [47:47] there's a technical reason why it's not [47:48] in core yet, but I I thought I saw [47:50] rumblings that it's coming to core [47:51] pretty quickly, pretty soon. And like [47:52] the transitions API and stuff like that [47:54] might be coming to the admin side, but I [47:56] can't remember where I saw that. Might [47:57] have been one of Felix Arnson's tweets, [47:59] something like like that. Um, yeah. So, [48:04] yes. So, anyways, back to back to the [48:06] thing that I built and I want to talk [48:07] about. Um, if you if there's anything [48:10] that this doesn't do, let me know. If it [48:12] does weird stuff, let me know too [48:13] because because one thing I have it Oh, [48:15] the other thing it does and and I I [48:17] meant to show this is it actually will [48:19] um it it'll detect [48:23] it will detect like if you do um data [48:28] uh w [48:32] P- [48:35] I can type it right context. [48:39] weird that it why is context not in [48:41] there? It what it should be able to do [48:44] is actually [48:46] um [48:48] you should be able it it it can parse [48:51] context in this state in in this state. [48:53] So if I if I were to go context [48:56] dot dot dot [49:00] okay [49:05] revash store cache okay um [49:12] okay well that's not working should have [49:14] been working though [49:19] oops [49:20] that's unfortunate okay Well, [49:24] because what it should be doing is it [49:26] should be able to where is it? Um, [49:31] support directives. [49:35] There is a context parsing. [49:42] Did it not make it in? [49:45] Look at that. [49:52] Huh. Okay. Well, in my um [49:57] Well, if that's not Yeah, I I'll have to [49:59] check that because it was working [50:00] before. This is [50:02] So, in here, if I look at my testing, I [50:05] have um context. Yeah. So, what this [50:09] should be doing is it actually will it's [50:12] supposed to be able to detect this this [50:14] context here. I do this. Okay. See, it's [50:17] actually pulling context in. So, that's [50:19] I have to check and see why that's [50:20] that's not happening in that given [50:22] thing. Uh, but this what it's supposed [50:24] to do is it's supposed to be able to be [50:25] able it's supposed to be able to figure [50:26] out the context that's been passed down. [50:28] Um, so, you know, we will I'll look into [50:32] that. But anyways, it's very like 1.0. [50:36] So, I'd love I'd love feedback. And uh [50:39] oh, and while we're here, I'm going to [50:42] start viewer callins if anyone's in [50:44] interested in hanging out. Uh I'm going [50:47] to make you you have to be followers and [50:48] subscribers now, though. [50:51] Followers or subscribers. And you're [50:52] welcome to jump on the stream with me [50:54] and hang out. Um but this this was fun. [50:58] So I I claude [51:01] code to do this and it just basically it [51:04] just got it. It just did it and it was [51:05] like pretty amazing. took me a bit of [51:08] refining. Uh, and I used I used a nano [51:11] banana to come up with the uh with the [51:14] where is it with [51:18] with my extens with the icon which is [51:20] where is the icon? It's right here. That [51:23] little thing. So, I'm all AI. I'm all in [51:25] on AI. It will not work in PHP Storm, [51:28] Paul, but I've been thinking I don't [51:30] know if PHP Storm does autocomplete. I I [51:33] know it does like snippets, live [51:35] templates, I think they're called. Um, [51:38] but I don't think I don't think you can [51:40] do the same sort of autocomplete stuff. [51:42] But I but I'm not sure. It's been a long [51:44] time since I've uh um [51:49] used um PHP Storm. Okay. Well, I will [51:54] make you know what I'll do. I'm going to [51:55] take I'm going to ask Code to take the [51:58] functionality of this and create a VS uh [52:01] PHP Storm extension um for it. So that [52:06] that'll be fun. [52:09] Yeah. It's like when you're getting into [52:11] like the the AI inception, like when you [52:13] do this, you know, you're like, I'm [52:16] using AI to build a prompt for another [52:18] AI. It's crazy. Um I don't know how long [52:21] it's going to take me to do it, Paul, [52:23] but I will um I will see what I what I [52:27] can do. [52:30] Um, and yeah, if if and if it just [52:32] doesn't work and it's just it's just [52:33] broken, like those those lovely [52:36] individuals that are going to test this [52:37] thing out for me, uh, let me know. Like, [52:39] let me know. Uh, do the Ralph [52:43] Ralph Wigumstrat. [52:45] What is that? [52:52] That was a Ralph Wiggumstrat. I'm not [52:54] googling that. Kevin. [52:57] Oh, Kev, are you going to work campasia? [53:02] Do I want a link? No, I don't want a [53:04] link. Do I want Ah, I don't trust you. I [53:07] trust you. You're not going to send me [53:09] bad things. Send the link. Yeah, send a [53:11] link. Ralph loops are a legit AI thing. [53:19] The Ralph I've never heard of this. [53:21] Okay. Well, I'm I want to learn about it [53:22] then. So So [53:25] put Okay. I'm going to Google this [53:27] offscreen. I I just I'm so scared of the [53:29] internet now. [53:33] Wiggum [53:37] Ralph Wigum strategy. Let's see. [53:44] Iterative autonomous AI development [53:45] meth. Okay, hold on. [53:49] Awesome. Clo.ai. What is this? [53:59] Oh my god. [54:03] Huh. That's pretty cool. [54:07] Okay. I learned something new today. [54:10] It's a real thing. India. I want to [54:12] maybe 50/50. Yeah, I'm I'm going. Well, [54:17] I've been accepted to speak and I think [54:19] I'm going. So, we I I haven't got [54:21] official uh formal yes or or not, but [54:26] if anyone else is going to be there, I'm [54:27] hopeful I there's a good chance I I will [54:29] be there as well. So, be great. Be great [54:32] to hang out [54:35] um [54:36] and hang out and do stuff. [54:40] All right. Um [54:43] I don't really have much else I I was [54:44] going to really go over. Let's see [54:48] snippets. See, we talked snippets, [54:50] talked about PHP only blocks, tell [54:53] rebuild all of our person JS and let it [54:55] run for three months and see what [54:56] happens. Oh my god, you imagine the [54:57] tokens you you'd blast through. [55:02] I also discovered Sununo. Well, I I got [55:06] an account at Sununo and I spent an [55:08] entire day building uh songs for my [55:11] daughter's volleyball team [55:14] and ridiculous like uh um just just [55:20] ridiculous songs. It was so much fun. It [55:22] is so much fun. Go and do it and get [55:25] them. It's so good. [55:32] Yeah. Isn't it amazing? And it's so [55:34] good. So, I I opted for the uh I opted [55:39] for the um [55:41] like I'm I'm I I'm using it for work. [55:45] So, uh let's see. Let's [55:49] just see. Um, [55:53] and like I'm I I'm just playing around [55:57] with it and it is so much fun. [56:00] Like listen listen to the song. Can you [56:02] hear this? [56:10] Turn it up. [56:20] >> And then I went for an East Coast. [56:22] >> This is No, [56:24] >> not that one. Is this one [56:26] >> 90s East Coast rap? [56:38] >> Isn't it so good? blow [56:42] from the north where the gym squeak. We [56:44] ride trailblazers on the back. [56:46] >> I'm going to have to go [56:50] on the baseline [56:52] on the left side. [57:04] She be hitting on speed and gas roll [57:06] shot then a rip defenders crash. [57:10] >> You could hear that, right? Oh yeah. [57:12] Okay. [57:18] Um I heard the worst song ever in the [57:22] store yesterday and it was like it was [57:24] literally called I Love the 80s. I I'd [57:25] never heard of this song before and I I [57:27] I'm listening to it. God, oh man, it's [57:28] horrible. And then uh I realized this [57:32] might be an AI version. Like this could [57:33] be an AI song where someone just said, [57:36] "Write a song about loving the 80s." And [57:38] it sounds like every '8s song I ever [57:39] written. [57:43] Oh my god, that's hilarious. [57:47] Um, what would be really funny is if I [57:50] thought you guys could hear the music [57:51] that I was playing and I was dancing to [57:53] it, but in real life it was just me like [57:55] just doing this with no sound. That [57:58] would have been hysterical. Please tell [58:00] me that didn't happen. Or maybe that did [58:02] happen. [58:03] Gonna put my stream music back on. [58:11] All right. No one wants to jump on [58:14] stream with me. Come on, Kevin. [58:28] Oh, there's Paul. Paul wants in. All [58:30] right. Come on in, Paul. Right. I I I [58:33] have to drop right at noon, but if we [58:35] all just want to pile in and talk about [58:36] whatever, let's do it. I see Paul [59:01] Uh, yes. [59:03] >> Hello. Hello. Hello. Hello. [59:05] >> There he is. [59:09] >> Audio is the audio better today. [59:12] >> I'm just I've just your API plugin. I'm [59:16] getting um the uh [59:23] >> I think you're sending yourself back to [59:25] me there. [59:26] >> Uh AI in PHP Storm to try and do the [59:29] conversion for me. [59:31] >> Oh, nice. [59:33] All right, let's see. Oh, I know what I [59:36] need to do. Sorry, I think that's my [59:37] bad. One second. I'm going to turn off [59:39] the Google Chrome. Can you say something [59:42] again, Paul? [59:48] 1 2 3 4 1 2 3 4 1 2 3 4 [59:54] >> one two [59:56] >> H [59:58] Okay, [60:01] I'm going to say this and then when I [60:03] hear myself, I'm going to start speaking [60:05] again. [60:11] Now ended [60:15] Okay. So, I'm I'm hearing you double. Uh [60:19] I wonder if I turn this off. Wait, turn [60:21] that off. How about now, Paul? [60:26] Oh, that's better. Okay, that's super [60:28] loud, though. Okay. I think I was just [60:31] hearing you. You doubled because I had [60:32] the uh I have the [60:35] audio from the browser source for stream [60:37] together. Anyways, but you can hear me, [60:38] right, Paul? [60:41] Okay. I can't hear you now, though. [60:45] Yes, I can. One, two, three, four. Yes. [60:47] >> Okay, there you go. Perfect. Okay, [60:49] excellent. We'll get this. It's my first [60:50] day with the internet, folks. First day [60:51] with the internet. Alus, why aren't you [60:53] getting in here? Come on. Come on. Let's [60:55] do it, [60:57] Paul. Uh, so, sorry, Paul. So, you're [60:59] going to take that thing that I did and [61:01] you're going to get AI to convert it to [61:03] PHP Storm. [61:09] >> Yes, I am. [61:11] >> Oh, awesome. Enjoy. [61:15] >> Cool. Um, that's great. Well, I'd I'd [61:19] love to see it. I'd love to see what uh [61:21] how it all works. [61:24] >> There's a there's a branch and a pull [61:26] request coming. [61:28] >> I told [61:29] >> Oh, pull request. [61:30] >> Yeah, I told it to make it to merge into [61:33] the same thing and see if we can have [61:34] the one. [61:37] >> Oh. Uh, okay. Well, that that might that [61:40] might break it. [61:42] But but we'll see uh [61:47] just because it uh the the the the way [61:50] it's b the way it's bundling might not [61:52] work but [61:56] let's see it's building it's building a [61:58] pull request right now. That's crazy. [62:00] >> No, not yet. Still coding. [62:04] >> Oh, okay. All right. [62:08] All right. Cool. [62:10] Cool. Cool. Cool. [62:17] >> So, what what's what else has been going [62:18] on, Paul? [62:21] >> Just going I'm working on [62:25] um Let me get a ticket. [62:30] Um allowing [62:33] um allowing [62:35] to static pages to be other CPTs. [62:43] Okay. [62:45] Allowing static pages. [62:48] I don't think I did. Uh oh, you you [62:51] can't you probably can't drop the link. [62:52] Um I'm gonna have to figure out out a [62:54] way to let people drop links. Let me [62:57] just uh Twitch and I'll [63:01] see what I can figure out here. [63:07] What are we doing? moderation settings [63:13] block hyperlinks. [63:15] Uh, okay. Your chat will automatically [63:18] delete posted URLs except for once [63:19] posted by you, moderators, admins, and [63:20] VIPs. Oh, okay. So, I can turn that off. [63:26] And then [63:30] then I have to make people moderators, I [63:32] guess. Mins. [63:36] Okay. [63:42] You know what? I'm I'm going to turn [63:44] links back on and then I think because [63:46] I've also ch changed some chat [63:48] verification. So like chatters need need [63:51] to be like basically [63:54] um [63:58] they they need to be verified. So I I [64:00] don't know. I'm just not going to click [64:02] links. So if you have a link, Paul, just [64:04] just uh drop it in chat. [64:07] Um, [64:09] bad do court. Thanks for hanging out. [64:10] We'll see you next time. And, uh, oh, [64:13] uh, Troy, if you're still around, drop, [64:15] uh, drop your link to your accessibility [64:17] plugin or the accessibility checker in [64:19] the, um, in the chat then so people can [64:22] get it. [64:24] Sorry, Paul. You uh, so what is the [64:28] ticket 19? So, this is a court. This is [64:30] a track ticket. [64:32] >> Yes. [64:33] Okay. [64:39] See what this is. [64:43] Allow custom post types as home and get [64:45] get post return results for more than [64:46] one post type. [64:52] Oh, I see. [64:55] What was that? [65:01] Oh, I see. So, so this is basically [65:03] change what what is this changing the [65:05] like it's just it's retrieving [65:09] Oh, I see. So, so is a get post just is [65:12] it restricted to um [65:24] I should not have done that. I'm going [65:25] to be the PR. [65:27] There we go. So that's T link [65:41] posts allowed on homepage. Oh, I see. [65:43] Okay. So is this a is this filterable? [65:45] Oh, it is filterable. [65:47] >> Get post show and homepage list is true. [65:50] Is this an actual thing [65:52] or is that new? The show and homepage [65:56] >> list. [65:56] >> No, that's new. That's new that [65:59] >> Oh, nice. [66:00] >> That would be because not every CPT is [66:03] appropriate to be on the homepage or be [66:06] the home page. So, [66:08] >> right, [66:08] >> you have it has to be explicitly turned [66:11] on for [66:14] >> interesting. That's cool because that [66:16] that does make sense because you I mean [66:18] there's probably tons of reasons why you [66:20] wouldn't want to use a page or whatever. [66:21] You know, there's lots of things [66:24] um or or a list of posts or whatever. [66:26] That's That's pretty cool. So, what's [66:27] the what's the consensus on this that [66:29] it's uh it's good to go or it's like [66:31] people are into it? [66:33] >> Uh [66:34] >> scroll down to the bottom to find out. [66:35] >> It's um it needs some work. Um I'm [66:38] rewriting it and doing some some uh u [66:41] gooey work [66:43] and fixing a few things. So, [66:46] you know, this week's project is what [66:48] I'm trying to get this to a working [66:51] version with today's code. [66:56] Oh, okay. Cool. [66:59] So, are you working on the pull request [67:01] that Adam was doing or like your own or [67:03] or a different patch? [67:04] >> I've pulled off Adam's work. [67:06] >> Oh, okay. Cool. [67:10] Oh, I see. Cool. Awesome. Well, that's [67:13] pretty cool. I mean, that that'll be a [67:14] nice little change for sure. [67:16] >> Yeah. Adam basically took my patch and [67:19] made it into a GitHub repo at some [67:22] point. [67:22] >> Oh, okay. Cool. Cool. [67:26] That I'm always stealing people's code. [67:28] Just kidding. [67:29] >> And you have a pull request on your API. [67:32] >> I do. Oh, no. Well, I probably won't [67:35] merge it because I don't know what this [67:38] is going to do for like the like Did you [67:41] Did you test this? What's this? Add in. [67:45] Um there's a folder in there with a PHP [67:47] plugin in it. [67:53] Oh my god. Okay. [67:55] So, okay. Hold on. [67:59] Well, [67:59] >> the IDE stuff went as well, which [68:01] shouldn't have done. Sorry for that. [68:03] >> Oh, whatever. That that's that's fine. [68:06] I'm going to just hide all this. So, [68:08] what does this thing do? [68:11] Okay. [68:13] Oh, this is interesting. [68:19] Can Can I just download a zip of this [68:21] particular [68:22] >> Yeah, you can. [68:23] >> Can you download a zip from from this [68:25] branch? [68:26] >> Hi, Blue. I literally ne never done that [68:28] before. How would I do that? Code. Oh, [68:31] yeah. Right there. Uh code spaces. [68:35] >> I know. I would like [68:45] Okay. Well, I'll have to look at it. [68:47] >> Yeah. No, I'm gonna have to try and see [68:48] if it if I if it'll actually run because [68:51] this is [68:54] >> Wow, this is cool. [68:56] Look at all this. Oh my god, there's so [68:58] much stuff here. And so, where is this [69:00] putting this PH? Oh, it's it's putting [69:02] it in inside of a inside of a uh Can I [69:04] look at the code? [69:07] So, I love how it's one commit. [69:10] That's so much stuff [69:14] with 21 files. That's hilarious. [69:17] Uh, that's cool. Okay. Well, I mean, I' [69:20] I'd be really interested to see if if if [69:22] this works because I think PHP Storm is [69:24] definitely something that like there's a [69:27] lot of VS Code extensions out there, but [69:30] um, not all like, you know, there's a [69:32] lot of PHP Storm users as well. Um, do [69:35] you get proper TypeScript support help [69:37] and stuff in PHP Storm? I I I used to [69:39] love PHP Storm. I used it all the time. [69:41] I used to use it all the time, but I [69:42] switched to VS Code a number of years [69:43] ago now. Um so so I'm a little bit uh [69:46] behind on it, but it'd be very cool. So [69:49] it does like autocomplete and all that [69:51] stuff. [69:52] >> All that good stuff. It finds all the [69:55] all the functions and all that stuff. [69:57] >> Okay, great. So, I mean, this would be [70:00] very cool if we could split this out [70:02] into its own [70:04] um [70:06] into its own uh folder inside of this. [70:10] So, did this move everything or did it [70:14] just put a folder beside it? [70:17] >> No, it put a folder beside it. [70:23] >> So, there's a folder. So all that code [70:26] that's in the original repository there [70:28] there's just like a there's a PHP Storm [70:30] folder in there now. [70:32] >> Yes. Yes. [70:33] >> Okay. [70:35] Interesting. [70:36] >> Yep. [70:37] >> Um [70:39] so I wonder if maybe we can put all the [70:49] And it's still by the command pal. This [70:51] is [70:53] um I wonder if you wouldn't mind telling [70:56] your a AI to take all the the the [70:59] existing files and put them in a VS Code [71:01] folder. So So there'll be like [71:04] essentially two folders at at the root [71:06] of the um at the root of the project, [71:10] which would be like VS Code, PHP Storm, [71:13] and then kind of go from there. But [71:16] again, I'm not sure if I'm gonna if I'm [71:18] gonna uh merge this or not, but this is [71:22] I'd like to see if it works, which would [71:23] be cool. So So So tell me if it works [71:26] and how it works and everything. We can [71:27] go from there. [71:35] >> We'll play. See what happens. [71:40] Can you share your screen? Did Did I [71:43] allow that? I I don't know if I allowed [71:45] that or not. [71:56] >> No, disabled my end. H [72:02] maybe I can [72:08] I might have to [72:17] I probably needed to set that up before [72:19] I uh there was a Oh, wait. What's in [72:22] there? Oh, yeah. Can I try that? Can I [72:26] Ah! Oh, hold on. Okay. [72:31] Uh, I need to I need need to set that up [72:34] for another time, but that's cool. Um, [72:36] you can just let me know if it works, [72:37] which would be great. Um, that'd be fun. [72:47] Oh, Troy, what are you saying? Sorry, [72:48] Troy. Uh, I should dive back into some [72:50] old issues I created. Do a bit more [72:51] contributing. Yeah, we like [72:53] contributors. [72:55] Where can I find the snippets link on [72:58] the developer? Oh, the snippets link. [72:59] Yeah, it's right there. Um, [73:02] it's here. Elus, that's for you. [73:07] And we're always looking for new [73:08] snippets. So, snippets and articles and [73:11] all sorts of fun stuff. We're always [73:12] looking for that at the uh for the [73:16] um developer blog. There's the process. [73:18] It's pretty pretty easily, pretty well [73:20] documented. There's a how to how to [73:22] contribute section under the about if [73:24] you're interested in getting involved in [73:25] adding whatever go read that. I think [73:28] there's a uh there's a monthly meeting [73:30] to discuss the content that's like the [73:32] ideas that have been put forward and [73:33] then if they get approved they get you [73:35] can just write it or do it and you can [73:38] go from there. Oh, excuse me. [73:44] All right. What time is it? Well, Paul, [73:47] is it working? [73:48] >> No, not yet. I can't work out how to [73:51] actually load it into the plugins. [73:54] >> Oh, I see. [73:59] I don't think I have Do I have PHP Storm [74:01] set up? I do not. [74:04] All right. I'll probably have to [74:05] download that, try it out. First Tuesday [74:07] of each month, we meet. There you Yeah, [74:10] Troy's on the one of the one of the [74:13] people that approve it. So, sweet talk [74:15] him. Go download his plugin. [74:18] All [74:22] right. Well, I'm gonna have to cut this [74:25] a little bit short today because I have [74:27] a very important email for my daughter's [74:29] volleyball team uh that I have to def [74:32] tell them what hotels we we want to stay [74:34] in and it's first come first serve. So, [74:35] I have to like literally wait by my [74:37] email hovering to click it and go. So, [74:40] it should be coming in shortly. But, I [74:43] want to wait and Paul I want to I want [74:45] to hear just how good it is. If if it's [74:47] good, [74:57] I'll let you know. [74:59] >> All right. [75:08] And um like I said before, if anyone's [75:10] interested in uh jumping on stream, [75:14] doing that [75:16] showing show and tell sort of thing. Um [75:19] in my Discord, there is a show us the [75:21] goods channel. You can drop a message in [75:23] there and we can coordinate something. [75:25] I've got my first one sort of I got my [75:28] first guest lined up, but I don't know [75:30] when we're going to do it yet. And then [75:31] after that, it'd be great. I don't know. [75:33] We could do it every once every couple [75:34] weeks, once a month, something like [75:35] that. People have stuff they want to [75:37] share. I think I think it's cool. It' be [75:40] fun. And maybe we'll turn it into a [75:41] podcast because everyone needs a [75:43] podcast. I don't have one. Paul, do you [75:46] have a p Do you have a podcast, Paul? [75:48] >> Yeah. [75:50] Um, [75:50] >> do you have a podcast? [75:51] >> No, we haven't. I haven't got a podcast. [75:53] >> Oh, [75:56] I was gonna say. [76:00] So, if anyone wants to start a podcast [76:02] with Paul and I, let me know. We'll [76:04] we'll [76:07] definitely do do a show project. Yes. [76:10] Cool. Troy, you're in you're in for that [76:14] because let's do it. You'll be number [76:16] two. [76:19] I think that I think that'll be a ton of [76:20] fun. Okay, awesome. Well, let's get [76:21] organized. We'll um you you let me know [76:24] when you like we'll we we we can talk [76:27] but let's let's get something figured [76:29] out in the next like [76:31] couple of weeks. What like not to be [76:33] live in a couple of weeks but to get it [76:36] figured out when they would work when [76:37] you think it's it's ready when we can go [76:39] through it so you can show it and we can [76:40] also like talk about the the the the [76:44] technical stuff. Nice. Oh, you're [76:46] waiting on some early feedback from me, [76:48] aren't you? [76:51] You know what I I'm I'm going to do I'm [76:53] gonna um I'm gonna my kid and I are [76:56] going to sit down and we're going to [76:57] play it because he's been he's been [76:58] dying to play Dungeons and Dragons and [77:00] it's um this sort of idea. It's not [77:03] Dungeons and Dragons. I didn't I didn't [77:04] let it the cat out of the bag, but [77:05] something along those lines would be [77:08] fun. So, he he would probably love it. [77:14] All right. Well, I will uh yeah, I'll [77:16] definitely play it and I can even play [77:18] it on stream at some point. Maybe when [77:20] you're ready. When it's ready, maybe we [77:21] can do a game. That That'd be fun. Don't [77:23] let him play Flappy Bird. Yeah. If [77:25] anyone wants to get on and and and show [77:27] me their clone of Flappy Bird, I can [77:29] tell you now that I will 100% approve [77:33] that. I I idea. [77:36] Yeah. I sorry I let the cat out of the [77:39] bag, but it's very cool and I'm not [77:41] going to talk about it anymore because I [77:43] love the idea of it. It's this game [77:46] where like you have to throw pigs at [77:50] like structures and they fall down. It's [77:52] crazy. I've never seen it before. [78:01] Oh my god. We're going to make an AF. [78:03] I'm Okay, next. I have my next stream. [78:05] We're going to make a Flappy Bird clone [78:07] using the interactivity API on stream. [78:10] Kevin, [78:12] that's amazing. What better way to get [78:14] back to the Dave426, whoever the hell [78:16] that stupid bot was by not letting him [78:19] get us down. We're going to do it. We're [78:20] doing it next stream. Unless [78:23] Rob and I are are going to be on next [78:25] stream. So, next two streams that's [78:28] going to get done. That's going to be so [78:29] much fun. [78:31] Oh, I'm excited. I'm excited. Sorry, [78:33] Paul. I forgot you were here on the [78:35] stream with me. [78:38] How are you doing over there, Paul? [78:40] >> I'm doing good. I'm I I'm I'm just [78:43] reading the notes of how to do this now [78:45] and I need to use IntellJ ultimate [78:47] edition which I happen to have. So [78:49] that's good. [78:50] >> Oh, all right. Cool. Kevin, that was a [78:53] great idea. [78:54] >> This is actually [78:57] >> it's what? Sorry, [79:04] I didn't hear what you said. Oh, it's [79:06] written in Cotlin. Oh, wow. [79:09] Yeah, that's the thing. It's just like, [79:10] "Build me a thing." They're like, "Sure, [79:12] we're going to write it in C#. [79:14] Now you got to compile it." [79:18] Yay. Do you even compile C#? I I don't [79:21] know. C++ you do, I think. But [79:25] I'm not what you'd call a good [79:28] developer, so who knows? Who knows? [79:33] Um, all right. Well, on that note, Paul, [79:37] I'm gonna have to drop off, but thanks [79:38] so much for drop for for hanging out on [79:41] on camera wi with me. Um, and uh yeah, [79:47] thanks for for streaming with me, y'all, [79:49] and uh for sharing your links now that [79:51] you can share links again and for the [79:53] ideas, the content ideas. This is great. [79:54] We're gonna have so much fun in the next [79:56] few weeks. I'm very excited to do all [79:58] this. Um, and uh, yeah. So Paul, is it [80:04] it's it's it's not doing it. It's not [80:06] compiled yet or built or whatever. [80:08] >> No, I'm still install reinstalling the [80:10] uh IntelliJ because um I hadn't I turned [80:13] it off because I had I stopped using it [80:15] because I thought be a bit lighter and [80:18] just have PHP Storm running. [80:20] >> Yeah. Yeah. [80:22] >> Sure. That's actually one of the reasons [80:23] I moved away from PHP store because it [80:25] felt like such a beast. Like every time [80:26] I I I opened it, it just felt huge and [80:29] bloated and then like VS Code was like [80:31] instantaneous. [80:32] >> Yes. Until you file in all of the [80:34] extensions. Um it's [80:36] >> Well, there's that. [80:37] >> Yeah. And that's the difference is in [80:39] PHP Storm, you've got to configure it [80:41] and add all your other extensions. [80:43] Sorry. In VS Code, you got to do that. [80:46] PH4 Ptorm it's predetermined and bundled [80:49] and you only have to add a few plugins [80:52] to to tweak it whereas not everything [80:55] >> for sure. I I loved PHP Storm. I I will [80:58] say this. I found it much easier and [81:01] better to debug PHP in PHP Storm than in [81:05] VS Code. I found it like very intuitive, [81:08] very easy. like once you got XD bug and [81:10] everything all set up, I found it super [81:12] easy and it and the the inspection like [81:14] everything that you can do is really [81:15] really good. I find VS Code to be okay [81:18] in that regard. Um, but I transitioned [81:22] to VS Code right right around the time [81:23] that I was sort of like getting into a [81:24] lot more JavaScript. So, I wasn't doing [81:27] as much like PHP [81:29] um inception stuff like you know. So, [81:32] and it could just be that I just didn't [81:34] spend enough time to get it set up [81:35] properly. But I found PHP store to be a [81:37] lot more robust with that sort of stuff. [81:40] Um, but then in VS Code side, like it's [81:42] really great for all all the npm and the [81:45] auto formatting and the auto saving and [81:46] like all that sort of stuff. So, I mean, [81:48] they both have their their benefits. It [81:50] really just depends on what you're doing [81:51] with it, right? [81:52] >> Yeah. [81:53] >> Yeah. Yeah. Yeah. PHP is great and and [81:56] that's the other thing. You don't have [81:57] to pay a license for for PHP or for VS [81:59] Code. [82:00] >> No, that's true. It's free. Yeah. [82:02] >> But I'm happy to support them. and [82:04] they're doing good work and they're [82:06] they're the writing. [82:06] >> Oh, for sure. [82:08] >> So, yeah. No, no, no. I mean, it's it's [82:10] it's if if I mean, if it's like it's [82:12] like, you know, if if you're a mechanic, [82:14] you you buy your tools, right? Like this [82:16] this IDE is literally your tool for [82:18] doing your job and making money. So, I [82:20] mean, of course, investing in it is [82:22] makes sense. [82:22] >> And I I ended up with the ultimate [82:25] package. Um, and I the maths um worked [82:29] out better with the um um uh AI tool [82:33] built in because of the ultimate [82:35] package. I the AI tool bundled with it. [82:38] >> So I haven't had I'm not paying extra. [82:40] So it it actually comes out cheaper to [82:42] have PHP [82:43] >> to have the bund the whole bundle not [82:46] just PHP Storm and the uh AI tool. [82:50] >> Oh, I see. Because because PHP like in [82:53] intellisense or what whatever the [82:54] company is intell whatever the company [82:56] is that PHP store I can't remember [82:58] >> nippines like yeah like that they have a [83:01] number of other IDEs for for other other [83:03] things. [83:05] >> So cool. All right. Well, now that uh [83:08] Paul's told us he has the ultimate [83:10] package. Lucky lady your wife just [83:12] joking. Oh, that's a horrible joke. I [83:14] gotta uh I'm gonna I'm gonna leave on [83:16] that very not safe for work tone and [83:20] We can go from there. Paul's not [83:22] laughing. I feel like I offended him. [83:24] >> No, no, you haven't. [83:27] >> It's meant with love and respect, Paul. [83:28] It's a joke. [83:29] >> Yep. [83:30] >> Um, yeah. [83:36] Awkward. Anyhow, um [83:40] Oh, yeah. There's a delay. There's a [83:42] six-month delay in the [83:44] >> Yeah, I know. [83:46] I was I was concentrating slightly on [83:49] opening up the uh the project in [83:53] >> Okay. All right, Paul. Well, I mean, bad [83:56] jokes aside, I hope I haven't offended [83:58] you. That was not the intent. [84:02] I just couldn't I couldn't help myself. [84:04] All right. And on that note, I'm gonna [84:06] I'm gonna say goodbye, friends. And uh [84:08] call in HR. Yeah, Kevin's calling HR. [84:11] Yeah. Um uh and yeah, cool. So, next [84:15] week, I'm not sure what it'll be, but [84:16] it'll be something fun. So, uh, drop in [84:19] and say hi. And, uh, yeah. Anyways, [84:23] Paul, thanks so much for hanging out and [84:24] the for the for the poll request. Thanks [84:27] everyone else for for chilling with me [84:28] today. I'm going to say bye and I will [84:30] talk to you all later. [84:34] If I can find the button. There it is. [84:36] Later. ## Highlights - just came out. And so now this PHP only blocks thing uh now we can we can get these things happening which is really cool. So this is this is kind of fairly complete like fairly complete. I think I think we're in a position now where you just install the Gutenberg plugin and you're able to do PHP only blocks. So um that's super powerful. Super powerful. And we also discovered that you can still in in quue JavaScript ([View Highlight](https://read.readwise.io/read/01kfngv3anxmpy9esecg3gbac8)) - Tags: 👻 ai highlighted - Okay, cool. Um, right. So, that's that. I think I I just messaged Cross Keys because he's literally talking about this in one of the Discord chats about like, "Has anyone done this?" Uh, cool. But the other thing is, what is the other thing? Uh, okay. It's not in there. It's not there. It's not there. It's not in there. Ply box plug in Gutenber. Oh, great. Okay. So, I've been working on the icon block again. And I'm super excited about the uh about the work that we've sort of um uh been able to to to ([View Highlight](https://read.readwise.io/read/01kfngv3by4wk00e5ksa14brvh)) - Tags: 👻 ai highlighted - guides. No, let's go. I can never find it. The thing that I'm looking for getting started. Oh, I I know how it works. Okay, let me go to packages. Let me go to Let's go to um whatever the block editor. Going to read me. So in the read me somewhere down here. Why does it look like that? Okay. Why does it look like this? Something screwed up. Oh, there we go. ([View Highlight](https://read.readwise.io/read/01kfngv3e933exzf6kt7ds92dt)) - Tags: 👻 ai highlighted - and we can chat about it. Um all right. So, the next thing that I want to show you guys is something that I've been working on. Uh, I built it yesterday and it is a extension. Where's my extension? Right here. It's called and uh I I I built this with with Claude Code in like two days and I'm super excited with it. It's my first real like um uh like real vibe code whatever thing. ([View Highlight](https://read.readwise.io/read/01kfngv3nt5sb1grd68z44f4wx)) - Tags: 👻 ai highlighted - to hang out um and hang out and do stuff. All right. Um I don't really have much else I I was going to really go over. Let's see snippets. See, we talked snippets, talked about PHP only blocks, tell rebuild all of our person JS and let it run for three months and see what happens. Oh my god, you imagine the tokens you you'd blast through. ([View Highlight](https://read.readwise.io/read/01kfngv43mg13b5dr1s3g3qqq7)) - Tags: 👻 ai highlighted - you're going to get AI to convert it to PHP Storm. >> Yes, I am. >> Oh, awesome. Enjoy. >> Cool. Um, that's great. Well, I'd I'd love to see it. I'd love to see what uh how it all works. >> There's a there's a branch and a pull request coming. >> I told >> Oh, pull request. ([View Highlight](https://read.readwise.io/read/01kfngv4cb736k25w2thd6v48e)) - Tags: 👻 ai highlighted - people are into it? >> Uh >> scroll down to the bottom to find out. >> It's um it needs some work. Um I'm rewriting it and doing some some uh u gooey work and fixing a few things. So, you know, this week's project is what I'm trying to get this to a working version with today's code. Oh, okay. Cool. So, are you working on the pull request ([View Highlight](https://read.readwise.io/read/01kfngv4kndxs2a3h6549ytykt)) - Tags: 👻 ai highlighted - yeah. Right there. Uh code spaces. >> I know. I would like Okay. Well, I'll have to look at it. >> Yeah. No, I'm gonna have to try and see if it if I if it'll actually run because this is >> Wow, this is cool. Look at all this. Oh my god, there's so much stuff here. And so, where is this ([View Highlight](https://read.readwise.io/read/01kfngv4xwvf3pvrr17qgzwx1v)) - Tags: 👻 ai highlighted - Uh, I need to I need need to set that up for another time, but that's cool. Um, you can just let me know if it works, which would be great. Um, that'd be fun. Oh, Troy, what are you saying? Sorry, Troy. Uh, I should dive back into some old issues I created. Do a bit more contributing. Yeah, we like contributors. Where can I find the snippets link on the developer? Oh, the snippets link. Yeah, it's right there. Um, ([View Highlight](https://read.readwise.io/read/01kfngv54jvvppzq505qnwv2qv)) - Tags: 👻 ai highlighted - to discuss the content that's like the ideas that have been put forward and then if they get approved they get you can just write it or do it and you can go from there. Oh, excuse me. All right. What time is it? Well, Paul, is it working? >> No, not yet. I can't work out how to actually load it into the plugins. >> Oh, I see. I don't think I have Do I have PHP Storm ([View Highlight](https://read.readwise.io/read/01kfngv5mngdy9qpjyrvjwg94a)) - Tags: 👻 ai highlighted