New Concept: National Championships at WordCamps  [[3. Resources/Readwise/Full Document Contents/Articles/New Concept National Championships at WordCamps|Full Document Contents]] ## Document Notes --- tags: [wordpress, wordcamp, performance] author: Dave Loodts source: make.wordpress.org reference: [https://make.wordpress.org/community/2026/02/02/new-concept-national-championships-at-wordcamps/](https://make.wordpress.org/community/2026/02/02/new-concept-national-championships-at-wordcamps/) date created: 2026-02-15 10:00 --- # 🏷️ Title: New concept: National Championships at WordCamps ## 🧭 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 - Include links cited in or relevant to the article. ## 📝 Summary - Dave Loodts proposes a hands-on, gamified “National Championship Performance Optimization” format for WordCamps, tested at WordCamp Netherlands. - It matters because many talks are passive and light on real dashboards, code, and tools; this format centers practical learning. - Stakeholders: WordCamp organizers, sponsors (e.g., Kinsta), tool vendors, attendees (new and experienced). - Risks: sponsor/product-mention guideline tensions, scaling hosting, and score integrity. - Bottom line: structured, playful optimization challenges can boost engagement, learning, and community energy at WordPress events. ## 📖 Main Content - Core idea: Traditional WordCamp talks are inspiring but passive and often avoid concrete product demos. Loodts designs a shared, hands-on challenge: 24 identical deliberately “crappy” WordPress sites that participants must speed up within 40 minutes. - Framing: Branded as a light, humorous “National Championship” mainly to draw attendees in a tough time slot and compete with a big-name speaker; emphasis is on participation over winning. - Mechanics: Identical sites on a strong managed host (Kinsta), caching disabled to guarantee poor baseline scores, and bulk-licensed popular plugins so attendees don’t use personal licenses. A tight schedule includes briefing, micro-training, optimization sprint, winner announcement, solution review, and raffle of WordPress teddy bears as prizes. - Tooling: A custom Lovable-built scoreboard where teams self-enter mobile/desktop PageSpeed scores plus screenshots, triggering a short national anthem clip with each submission; a Lovable-built prize wheel for raffles. - Outcomes: Both newcomers and experienced attendees enjoyed the format; newcomers valued hands-on practice and post-challenge debriefs, while veterans called it a highlight of the camp. - Tensions & ethics: Loodts acknowledges skirting WordCamp product-mention guidelines with Kinsta branding in the sites and promo video, arguing that when educational and community benefits far outweigh commercial interests, that tradeoff is justified. - Scalability: Hosting is the bottleneck for larger events (60–150+ attendees). He suggests exploring WordPress Playground-based challenges and AI-driven visual-diff scoring for design challenges to make the concept more portable. ### 🗒️ Notes - Author’s motivation: enjoys WordCamps since 2014 but misses “practical, hands-on information” like “code” and “screenshots or videos of admin dashboards.” - Constraint: WordCamp rules discourage product presentations/mentions, which conflicts with how real-world WordPress work relies on plugins like WooCommerce and WP Rocket. - Audience dynamics: traditional talks are passive; workshops help but often isolate participants on their own sites rather than a shared problem. - Concept genesis: create a shared, high-energy, hands-on session where “everyone works on exactly the same thing” → National Championships Performance Optimization. - Implementation: - 24 identical, intentionally slow WordPress sites. - Task: “transform this crappy site into a lightning-fast one.” - Deployed at WordCamp Netherlands with better-than-expected enthusiasm and results. - Vibe and branding: - Title “National Championship” chosen to compete with a major speaker and an early-day-two timeslot. - Emphasis on lightness and fun, recalling the author’s fries costume at WordCamp Antwerp 2018. - Imposter-syndrome awareness; environment designed so “participating matters more than winning.” - Prizes: - Main prize: WordPress teddy bears, which drove significant excitement. - Two winners selected by performance; remaining bears raffled via a prize wheel. - Timeboxed format: - 10 min: briefing. - 5 min: ultra-fast performance training with tips. - 40 min: optimization challenge. - 5 min: congratulate winners. - 15 min: review solutions and workflows, let participants share learnings. - 5 min: raffle draw. - Participant experience: - Newcomers loved hands-on practice even with modest scores, and learned from listening to others’ approaches. - Experienced attendees considered it a highlight of the camp. - High room energy sustained by a dedicated MC and proactive sponsor support. - Hosting & sponsors: - Kinsta provided a nearly top-tier hosting package free. - To make sites truly “crappy,” support was asked to disable caching and optimizations. - Author added Kinsta logo and product placement as a thank-you, acknowledging that this technically conflicts with WordCamp guidelines but arguing for “reading between the lines” when community benefit is high. - Tool and license logistics: - Requirements: fast site duplication and robust performance for 24 sites and ~40+ active testers. - Multiple popular WordPress tool vendors provided temporary bulk licenses; all sites deleted the next day to avoid retention issues. - Scoring & tools: - Initial idea: automate Google PageSpeed scoring via API, but parallelism limits made it too slow. - Final solution: Lovable-based manual-entry scoreboard with proof screenshots and an honesty pledge. - Fun twist: each score submission triggers a 10-second national anthem clip. - Prize wheel also built in Lovable in about 10 minutes, presented as an example of “embrace AI” for quick tooling. - Future variations: - Scaling performance challenges beyond ~40 participants is hard due to hosting constraints. - Alternative: design or layout challenges using WordPress Playground recipes and AI-based visual comparison to determine whose design best matches a reference. - Invitation: - Author offers to share the WordPress install, Lovable scoreboard, and details with anyone wanting to run a similar challenge at a meetup or WordCamp, via WordPress Slack DMs. ## 📚 References - New concept: National Championships at WordCamps (original article) — make.wordpress.org/community - WordCamp Central — https://central.wordcamp.org - WordPress Playground — https://developer.wordpress.org/playground - Kinsta (managed WordPress hosting sponsor) — https://kinsta.com - Google PageSpeed Insights — https://pagespeed.web.dev - Lovable (AI app builder used for scoreboard and prize wheel) — https://lovable.dev ## 🗣️ Paraphrase - Loodts argues that adding a playful, competitive, but low-stakes performance-optimization challenge to WordCamps can convert passive, abstract sessions into shared, hands-on learning experiences, even for beginners. By pre-building slow demo sites, securing strong hosting and temporary licenses, and wrapping everything in a high-energy format with goofy prizes, organizers can create a highlight session that respects community values while bending traditional no-product norms slightly in favor of educational impact. - He details logistics—timeboxing, MC support, hosting requirements, scoring mechanisms, and potential Playground/AI-powered variants—to make it replicable at other meetups and WordCamps, and invites organizers to reuse his materials and adapt the form > [!note]+ Document Notes > tags: [wordpress, wordcamp, performance] > author: Dave Loodts > source: make.wordpress.org > reference: [https://make.wordpress.org/community/2026/02/02/new-concept-national-championships-at-wordcamps/](https://make.wordpress.org/community/2026/02/02/new-concept-national-championships-at-wordcamps/) > date created: 2026-02-15 10:00 > > # 🏷️ Title: New concept: National Championships at WordCamps > <!-- deep-read:sections start --> ## 🧭 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 - Include links cited in or relevant to the article. ## 📝 Summary - Dave Loodts proposes a hands-on, gamified “National Championship Performance Optimization” format for WordCamps, tested at WordCamp Netherlands. - It matters because many talks are passive and light on real dashboards, code, and tools; this format centers practical learning. - Stakeholders: WordCamp organizers, sponsors (e.g., Kinsta), tool vendors, attendees (new and experienced). - Risks: sponsor/product-mention guideline tensions, scaling hosting, and score integrity. - Bottom line: structured, playful optimization challenges can boost engagement, learning, and community energy at WordPress events. ## 📖 Main Content - Core idea: Traditional WordCamp talks are inspiring but passive and often avoid concrete product demos. Loodts designs a shared, hands-on challenge: 24 identical deliberately “crappy” WordPress sites that participants must speed up within 40 minutes. - Framing: Branded as a light, humorous “National Championship” mainly to draw attendees in a tough time slot and compete with a big-name speaker; emphasis is on participation over winning. - Mechanics: Identical sites on a strong managed host (Kinsta), caching disabled to guarantee poor baseline scores, and bulk-licensed popular plugins so attendees don’t use personal licenses. A tight schedule includes briefing, micro-training, optimization sprint, winner announcement, solution review, and raffle of WordPress teddy bears as prizes. - Tooling: A custom Lovable-built scoreboard where teams self-enter mobile/desktop PageSpeed scores plus screenshots, triggering a short national anthem clip with each submission; a Lovable-built prize wheel for raffles. - Outcomes: Both newcomers and experienced attendees enjoyed the format; newcomers valued hands-on practice and post-challenge debriefs, while veterans called it a highlight of the camp. - Tensions & ethics: Loodts acknowledges skirting WordCamp product-mention guidelines with Kinsta branding in the sites and promo video, arguing that when educational and community benefits far outweigh commercial interests, that tradeoff is justified. - Scalability: Hosting is the bottleneck for larger events (60–150+ attendees). He suggests exploring WordPress Playground-based challenges and AI-driven visual-diff scoring for design challenges to make the concept more portable. ### 🗒️ Notes - Author’s motivation: enjoys WordCamps since 2014 but misses “practical, hands-on information” like “code” and “screenshots or videos of admin dashboards.” - Constraint: WordCamp rules discourage product presentations/mentions, which conflicts with how real-world WordPress work relies on plugins like WooCommerce and WP Rocket. - Audience dynamics: traditional talks are passive; workshops help but often isolate participants on their own sites rather than a shared problem. - Concept genesis: create a shared, high-energy, hands-on session where “everyone works on exactly the same thing” → National Championships Performance Optimization. - Implementation: - 24 identical, intentionally slow WordPress sites. - Task: “transform this crappy site into a lightning-fast one.” - Deployed at WordCamp Netherlands with better-than-expected enthusiasm and results. - Vibe and branding: - Title “National Championship” chosen to compete with a major speaker and an early-day-two timeslot. - Emphasis on lightness and fun, recalling the author’s fries costume at WordCamp Antwerp 2018. - Imposter-syndrome awareness; environment designed so “participating matters more than winning.” - Prizes: - Main prize: WordPress teddy bears, which drove significant excitement. - Two winners selected by performance; remaining bears raffled via a prize wheel. - Timeboxed format: - 10 min: briefing. - 5 min: ultra-fast performance training with tips. - 40 min: optimization challenge. - 5 min: congratulate winners. - 15 min: review solutions and workflows, let participants share learnings. - 5 min: raffle draw. - Participant experience: - Newcomers loved hands-on practice even with modest scores, and learned from listening to others’ approaches. - Experienced attendees considered it a highlight of the camp. - High room energy sustained by a dedicated MC and proactive sponsor support. - Hosting & sponsors: - Kinsta provided a nearly top-tier hosting package free. - To make sites truly “crappy,” support was asked to disable caching and optimizations. - Author added Kinsta logo and product placement as a thank-you, acknowledging that this technically conflicts with WordCamp guidelines but arguing for “reading between the lines” when community benefit is high. - Tool and license logistics: - Requirements: fast site duplication and robust performance for 24 sites and ~40+ active testers. - Multiple popular WordPress tool vendors provided temporary bulk licenses; all sites deleted the next day to avoid retention issues. - Scoring & tools: - Initial idea: automate Google PageSpeed scoring via API, but parallelism limits made it too slow. - Final solution: Lovable-based manual-entry scoreboard with proof screenshots and an honesty pledge. - Fun twist: each score submission triggers a 10-second national anthem clip. - Prize wheel also built in Lovable in about 10 minutes, presented as an example of “embrace AI” for quick tooling. - Future variations: - Scaling performance challenges beyond ~40 participants is hard due to hosting constraints. - Alternative: design or layout challenges using WordPress Playground recipes and AI-based visual comparison to determine whose design best matches a reference. - Invitation: - Author offers to share the WordPress install, Lovable scoreboard, and details with anyone wanting to run a similar challenge at a meetup or WordCamp, via WordPress Slack DMs. ## 📚 References - New concept: National Championships at WordCamps (original article) — make.wordpress.org/community - WordCamp Central — https://central.wordcamp.org - WordPress Playground — https://developer.wordpress.org/playground - Kinsta (managed WordPress hosting sponsor) — https://kinsta.com - Google PageSpeed Insights — https://pagespeed.web.dev - Lovable (AI app builder used for scoreboard and prize wheel) — https://lovable.dev ## 🗣️ Paraphrase - Loodts argues that adding a playful, competitive, but low-stakes performance-optimization challenge to WordCamps can convert passive, abstract sessions into shared, hands-on learning experiences, even for beginners. By pre-building slow demo sites, securing strong hosting and temporary licenses, and wrapping everything in a high-energy format with goofy prizes, organizers can create a highlight session that respects community values while bending traditional no-product norms slightly in favor of educational impact. - He details logistics—timeboxing, MC support, hosting requirements, scoring mechanisms, and potential Playground/AI-powered variants—to make it replicable at other meetups and WordCamps, and invites organizers to reuse his materials and adapt the format, treating sponsors as enablers of community-centric learning rather than pure advertisers. ## 📰 Newsletter WordPress events keep evolving—and Dave Loodts’ “National Championship Performance Optimization” at WordCamp Netherlands shows how far we can push the format. Instead of another slide-heavy talk, 40+ attendees raced to turn 24 identical, intentionally slow sites into speed demons, supported by Kinsta hosting, bulk-licensed plugins, and an AI-built scoreboard and prize wheel. Newcomers got genuine hands-on practice; veterans traded optimization tricks in a live debrief. The twist: prizes were WordPress teddy bears, and every score submission briefly blasted a national anthem, keeping the room buzzing. If you’re organizing a meetup or WordCamp, this format is a ready-made workshop: shared demo sites, clear scoring, and a fun narrative that lowers imposter syndrome. Pair it with resources like WordPress Playground for design challenges, and tap managed hosting sponsors to handle the load. Interested in running your own performance “championship”? Reach out on WordPress Slack to adapt the install, scoreboard, and runbook—and turn your next event slot into the session everyone talks about. ## ✅ Action Items #### DevRel - Developer advocacy: Publish a step-by-step guide and sample repo for running a performance challenge (site baseline, instrumentation, scoring). Offer to co-host a session at key regional WordCamps. - Education: Turn the 5-minute “super quick performance training” into a reusable slide deck + Learn.WordPress.org workshop, with exercises tied to the challenge. - Developer experience: Provide example configs for common stacks (Kinsta, other hosts) and scripts to reset demo sites between runs. - Developer marketing: Build a campaign that showcases performance wins from real events (before/after scores, lessons learned) while keeping sponsor presence subtle. - Community management: Draft a facilitation guide for MCs and volunteers: timekeeping, encouraging quieter participants, handling edge cases (score disputes, technical issues). - Internal/external/cross-project: Align with Core Performance and Training teams so the challenge reinforces current best practices and uses consistent guidance. #### OSPO - Policy & Governance: Clarify how product visibility in educational sessions interacts with event guidelines; document a pattern for “sponsor-enabled, education-first” activations. - License Compliance: Provide a standard template for temporary bulk-license agreements used in short-lived demo environments. - Security Management: Define a minimal-hardening baseline for demo sites, even when they’re short-lived (user roles, limited plugins, no real data). - Software Inventory: Maintain an internal catalog of “event stacks” (host + plugins + configs) with owners and a refresh schedule. - Developer Support: Offer office hours to event teams planning technical challenges—architecture, risk assessment, and guideline compliance. - Community Engagement: Explore co-funding models with hosts and vendors for educational challenge formats that can be reused across multiple events. - Strategic Alignment: Track KPIs such as number of events running challenges, participant satisfaction, and resulting contributions (e.g., performance-related tickets, docs). #### Community - Maintainers: Run “roadmap clinics” after challenges to connect observed performance issues with Core and plugin roadmaps. - Contributors: Promote the challenge as a “gateway” activity; share follow-up contributor paths for performance-focused work. - Sponsors: Offer transparent reports on challenge impact (attendance, feedback, learning outcomes) to justify continued sponsorship without turning sessions into ads. - Ecosystem: Coordinate cross-event sharing of challenge kits (Playground recipes, demo content, scoring tools) and document incidents/lessons learned. #### WordPress - Core: Use challenge outcomes (common bottlenecks, misconfigurations) to inform Core performance priorities and documentation. - Core Performance: Provide a recommended checklist and metrics (LCP, TTFB, CLS) for local challenges; publish a reference “crappy” site blueprint. - Core AI: Explore AI-based scoring helpers—e.g., visual diff for design challenges or automated interpretation of Lighthouse reports. - **Core Program Team:** Create an optional “hands-on challenge” track type in WordCamp handbooks, with guidance on room setup, safety, and scaling. - Mobile: Experiment with a mobile-focused variant (improving Core/App UX for constrained devices) at mobile meetups. - Playground: Develop official recipes for challenge-ready demo sites and simple score dashboards embedded in Playground-led sessions. - Community: Add a “challenge format” section to the WordCamp Organizer Handbook, including sample scripts, consent language, and sponsor coordination. - Training: Build lesson plans that pair theory (performance fundamentals) with a local challenge lab. - Marketing: Highlight these challenges in WordPress.org and WordCamp recaps as examples of modern, hands-on community events. - Support: Capture frequent performance issues uncovered during challenges and reflect them in support docs and FAQs. - Design: Provide a design-challenge kit leveraging Playground and AI visual diff for visual consistency scoring. - Documentation: Add a “Run a Performance Challenge” guide to DevHub/HelpHub linking to event tooling and best practices. - Photos: Encourage photo teams to document challenge sessions (with consent) as new, engaging visual assets. - TV: Record and publish recap segments explaining the format and key performance lessons. - Polyglots: Localize any shared materials (scoreboard UI, instructions, slides) to broaden adoption. - Accessibility: Ensure challenge sites and tools are accessible; add performance guidance that doesn’t conflict with accessibility (e.g., avoiding intrusive animations). - Meta: Support simple integrations (e.g., linking event session pages to challenge resources, sharing generic Playground recipes). - CLI: Offer WP-CLI scripts to reset demo content, run basic performance checks, or switch plugin sets quickly. - Hosting: Collaborate on a standard “event challenge” hosting profile with safe defaults and monitoring. - Tide: Optionally incorporate Tide scores or principles into post-challenge learning segments. - Openverse: Provide sample media assets for demo sites that are performance-conscious and license-compliant. - Themes: Ship a “slow baseline” theme configuration guide and a “fixed version” to demonstrate improvements. - Plugins: Partner with plugin authors to show best-practice configurations during debriefs, not as pitches. #### The WPOCC - Programs: Pilot microgrants to cover hosting and prize costs for local challenges that share openly reusable materials. - Projects: Sponsor documentation sprints to turn one-off challenge setups into polished, reusable kits. - Funding experiments: Test matched-grant models where hosts or vendors co-fund educational challenges tied to measurable learning outcomes. ### FAIR - Technical independence: Encourage local hosting or Playground setups where possible; document how to reproduce the stack with minimal proprietary lock-in. - Policies and covenants: Draft simple covenants clarifying that sponsor visibility is contingent on education-first design and data minimization. - Productized governance artifacts: Turn successful challenge formats into shareable playbooks with clear roles, success criteria, and metrics. ## 🧪 Hypotheses - H1: Hands-on performance challenges at WordCamps increase attendee-reported learning outcomes compared to traditional talks or Q&A sessions. - H2: Newcomers experience reduced imposter syndrome after participating in a low-stakes, gamified challenge with shared baselines. - H3: Sessions with shared demo sites generate more post-event collaboration (Slack discussions, follow-up contributions) than sessions focused on individual sites. - H4: Sponsor-supported hosting for technical challenges can comply with community norms if commercial signals remain secondary to educational value. - H5: AI-assisted tooling (scoreboards, visual diff, prize wheels) lowers organizer effort enough to make challenge formats sustainable. ### 📊 Methodology - Study design: Run controlled comparisons across multiple WordCamps and meetups: some with performance challenges, some with conventional talks on similar topics. - Data sources: - Pre/post-session surveys: perceived learning, confidence, and imposter syndrome scores. - Behavioral metrics: number of follow-up contributions, Slack messages, and shared resources. - Session telemetry: attendance, retention (who stays through debrief), and NPS-style ratings. - Analyses: - Compare mean learning and confidence scores between session types using t-tests or ANOVA. - Track correlation between challenge participation and subsequent community engagement. - Qualitative coding of free-text feedback on sponsor presence and potential discomfort. ### ❓ Questions - How far can event organizers go with sponsor visibility in technical sessions before attendees feel it crosses into advertising? - What minimum hosting specs are needed for 20, 50, 100+ simultaneous participants without degraded experience? - Which performance metrics are most intuitive and motivating for mixed-experience audiences? - Can Playground-based challenges deliver comparable learning outcomes without dedicated hosting? - How can we ensure accessibility and inclusion (e.g., visual/hearing impairments, low-end devices) in timed technical competitions? ### 🔮 Future Research - Develop and test standardized challenge kits (performance, security hardening, design systems) across different regions and event sizes. - Explore AI-based scoring systems that combine performance metrics with UX/accessibility checks. - Investigate long-term impact: do participants in such challenges become more active contributors or organizers? - Examine cultural differences: do competitive formats resonate equally across regions, or do some communities prefer collaborative, non-competitive variants? ### 💡 Implications - Practice: WordCamp organizers can broaden their toolkit beyond talks and panels with repeatable, high-engagement technical labs. - Policy: WordPress event guidelines might need clearer language on educational uses of sponsor infrastructure and product mentions. - Security: Structured challenges could extend beyond performance to security, backup, or upgrade drills, improving operational literacy. - Education: Learn.WordPress.org and Training teams can integrate challenge-based modules into learning paths. - Funding: Sponsors can support deeper learning experiences rather than only logo exposure, provided governance keeps incentives aligned. ### 🧠 Learning Styles Assessment - Reading level estimate: Roughly B2–C1 on CEFR; conversational but assumes familiarity with WordPress/WordCamp jargon. #### 👀 Visual learners - Present: Implied screenshots and dashboards; references to promo video and scoreboard UI. - Improve: Add annotated before/after performance graphs, flow diagrams for the challenge schedule, and sample scoreboard views. #### 🔊 Aural learners - Present: Session relies on in-room MC energy and brief training talk. - Improve: Publish a short audio or video explainer; offer recorded walkthroughs of the challenge format and performance concepts. #### 🗣️ Verbal learners - Present: Narrative storytelling about the event; clear explanation of constraints and goals. - Improve: Add explicit glossaries for performance metrics and a short FAQ. #### 🧩 Kinesthetic learners - Present: Strong—participants actively modify sites and see impact immediately. - Improve: Provide optional take-home mini-challenges or checklists for attendees’ own sites. #### 🧠 Logical learners - Present: Structured time plan and defined scoring system. - Improve: Include tables of baseline vs improved metrics and explicit reasoning about tradeoffs (e.g., plugin choices vs. native features). #### 🧑‍🤝‍🧑 Social learners - Present: Group challenge, MC-led energy, shared debrief discussion. - Improve: Add small team formats, peer review of approaches, and follow-up discussion prompts. #### 🧘‍♀️ Solitary learners - Present: Limited, as the format is highly social and timeboxed. - Improve: Provide written handouts, self-paced Playground versions, and reflection questions. #### 🌿 Naturalistic learners - Present: No direct environmental framing. - Improve: Connect performance optimizations to energy usage, hosting efficiency, and sustainable web design. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Not specifically described; WordPress.org content generally has basic heading structure. - Improve: Ensure challenge instructions, scoreboard, and prize wheel have clear headings, labels, and descriptive link text. #### Keyboard navigation - Present: Web-based tools likely support basic keyboard use, but not guaranteed. - Improve: Test scoreboard and wheel for full keyboard operability; ensure visible focus states. #### Contrast and readability - Present: WordPress.org typically meets baseline contrast guidelines. - Improve: Confirm contrast and font sizes in custom tools; avoid color-only state indicators. #### Text resizing and reflow - Present: Core sites are responsive; custom Lovable apps need testing. - Improve: Verify reflow up to 200% zoom; consider prefers-reduced-motion in animations. #### Media and captions - Present: Promo video mentioned; no details on captions. - Improve: Add captions and transcripts to any promo or explainer videos; avoid autoplay in crowded rooms. #### Forms and interactions - Present: Score submission form and prize wheel UI. - Improve: Provide clear labels, error messages, and large, accessible click targets. #### Standards reference - Map tool and page improvements to WCAG 2.2 AA, particularly 1.4.x (contrast), 2.1.x (keyboard), 2.2.x (enough time), and 3.3.x (input assistance). ### 🌍 DEIB Assessment #### Cultural breadth - Present: “National Championship” framing and national anthem clips; primarily local-national framing. - Improve: Ensure challenges can be adapted to local cultures; be cautious with national symbols in diverse, international audiences. #### Inclusive language - Present: Generally casual, inclusive tone; acknowledges imposter syndrome. - Improve: Avoid in-jokes that assume deep community familiarity; define jargon. #### Neurodiversity support - Present: Clear structure and timeboxing can help some participants. - Improve: Provide written agendas, allow opt-out from noisy elements (music), and avoid overloading with simultaneous stimuli. #### Representation - Present: Little detail on participant demographics. - Improve: Intentionally encourage diverse participation and highlight a variety of winners and stories in recaps. #### Psychological safety - Present: Message that “participating matters more than winning”; emphasis on fun. - Improve: Offer non-competitive variants or team modes; make it explicit that low scores are expected and welcome. ### ✅ Logical Validity #### Strong reasoning - Inductive: From one successful event, author cautiously suggests repeatability and offers a replicable process (time plan, tools, hosting constraints). - Causal: Reasonably links stronger hosting and tooling support to smoother challenge execution. - Normative: Argues that educational and community benefits can justify limited product visibility, grounded in concrete contributions from sponsors. #### Fallacies - Possible hasty generalization: Treating one “highlight” session as evidence that the format will work everywhere; could be strengthened with more data points. - Potential bias: Self-reported impact from participants and personal enthusiasm may overstate general appeal; acknowledging this explicitly would help. #### Tone of voice - Informal, humorous, self-deprecating; uses anecdotes (fries costume, teddy bears, anthem sound effects) to lower barriers and make experimentation feel safe. ### 🛡️ DARVO Analysis - Deny: No denial of harm; instead, a partial acknowledgment of bending guidelines around product placement. - Attack: No attacks on organizers or critics; tone is cooperative and reflective. - Reverse victim/offender: Mild risk of framing strict guideline adherence as an obstacle to fun, but author mostly accepts responsibility (“I take full credit for that”) rather than casting himself as a victim. ## 🎯 Conclusion Loodts’ “National Championships” format shows how WordCamps can become more hands-on, communal, and fun by centering shared technical challenges over passive listening. With careful hosting, lightweight AI tooling, and thoughtful sponsor involvement, organizers can deliver high-impact learning while preserving community values. Next steps for readers: consider piloting a small-scale performance or design challenge at your local meetup, document the process, and share back successful patterns. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] Hands-on WordCamp challenges boost engagement > [!quote] [New concept: National Championships at WordCamps](https://make.wordpress.org/community/2026/02/02/new-concept-national-championships-at-wordcamps/) by [[Dave Loodts]] via [[make.wordpress.org]]. Published 2026-02-02. Accessed 2026-02-15. > “A lot of people told me afterwards that this was one of the highlights of their WordCamp.” Two lines: context and use. Cite data if relevant. [view highlight](https://make.wordpress.org/community/2026/02/02/new-concept-national-championships-at-wordcamps/#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] Sponsor-enabled formats must stay education-first > [!quote] [New concept: National Championships at WordCamps](https://make.wordpress.org/community/2026/02/02/new-concept-national-championships-at-wordcamps/) > “As long as the outcome benefits waaayyy more joy, fun, hands-on learning, community mindset then commercial interest, i’ll go for it.” Two lines: context and use. [view highlight](https://make.wordpress.org/community/2026/02/02/new-concept-national-championships-at-wordcamps/#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] Shared demo sites increase WordCamp learning - When attendees work on identical demo sites, they can compare approaches and outcomes more directly. - Links: [[WordCamp-Formats]] [[Challenge-Based-Learning]] #### [Z2] Sponsor infrastructure can safely power challenges - Sponsor-provided hosting and tools are acceptable when governed by education-first rules and transparency. - Links: [[Open-Source-Governance]] [[Community-Sponsorship]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Draft a reusable “Run a Performance Challenge” guide for WordCamp organizers — context/https://make.wordpress.org/community/2026/02/02/new-concept-national-championships-at-wordcamps/ #fleeting #inbox - [F2] Prototype a Playground-based design challenge with AI visual diff scoring — context/https://make.wordpress.org/community/2026/02/02/new-concept-national-championships-at-wordcamps/ #fleeting #inbox - [F3] Clarify WordCamp guidelines on sponsor visibility in educational technical sessions — context/https://make.wordpress.org/community/2026/02/02/new-concept-national-championships-at-wordcamps/ #fleeting #inbox --- <!-- deep-read:sections end --> ## Highlights - The more experienced WordCampers enjoyed it too, and said it was definitely something worth repeating. A lot of people told me afterwards that this was one of the highlights of their WordCamp. You honestly can’t ask for a better compliment. ([View Highlight](https://read.readwise.io/read/01khfmxt1hypvp5jbp5vs9mzx8)) - Tags: 👻 ai highlighted ## New highlights added February 14, 2026 at 11:24 PM - The more experienced WordCampers enjoyed it too, and said it was definitely something worth repeating. A lot of people told me afterwards that this was one of the highlights of their WordCamp. You honestly can’t ask for a better compliment. ([View Highlight](https://read.readwise.io/read/01khfmxt1hypvp5jbp5vs9mzx8)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 12:24 AM - The more experienced WordCampers enjoyed it too, and said it was definitely something worth repeating. A lot of people told me afterwards that this was one of the highlights of their WordCamp. You honestly can’t ask for a better compliment. ([View Highlight](https://read.readwise.io/read/01khfmxt1hypvp5jbp5vs9mzx8)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 1:25 AM - The more experienced WordCampers enjoyed it too, and said it was definitely something worth repeating. A lot of people told me afterwards that this was one of the highlights of their WordCamp. You honestly can’t ask for a better compliment. ([View Highlight](https://read.readwise.io/read/01khfmxt1hypvp5jbp5vs9mzx8)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 2:24 AM - The more experienced WordCampers enjoyed it too, and said it was definitely something worth repeating. A lot of people told me afterwards that this was one of the highlights of their WordCamp. You honestly can’t ask for a better compliment. ([View Highlight](https://read.readwise.io/read/01khfmxt1hypvp5jbp5vs9mzx8)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 3:24 AM - The more experienced WordCampers enjoyed it too, and said it was definitely something worth repeating. A lot of people told me afterwards that this was one of the highlights of their WordCamp. You honestly can’t ask for a better compliment. ([View Highlight](https://read.readwise.io/read/01khfmxt1hypvp5jbp5vs9mzx8)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 4:24 AM - The more experienced WordCampers enjoyed it too, and said it was definitely something worth repeating. A lot of people told me afterwards that this was one of the highlights of their WordCamp. You honestly can’t ask for a better compliment. ([View Highlight](https://read.readwise.io/read/01khfmxt1hypvp5jbp5vs9mzx8)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 5:24 AM - The more experienced WordCampers enjoyed it too, and said it was definitely something worth repeating. A lot of people told me afterwards that this was one of the highlights of their WordCamp. You honestly can’t ask for a better compliment. ([View Highlight](https://read.readwise.io/read/01khfmxt1hypvp5jbp5vs9mzx8)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 6:24 AM - The more experienced WordCampers enjoyed it too, and said it was definitely something worth repeating. A lot of people told me afterwards that this was one of the highlights of their WordCamp. You honestly can’t ask for a better compliment. ([View Highlight](https://read.readwise.io/read/01khfmxt1hypvp5jbp5vs9mzx8)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 7:24 AM - The more experienced WordCampers enjoyed it too, and said it was definitely something worth repeating. A lot of people told me afterwards that this was one of the highlights of their WordCamp. You honestly can’t ask for a better compliment. ([View Highlight](https://read.readwise.io/read/01khfmxt1hypvp5jbp5vs9mzx8)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 8:25 AM - The more experienced WordCampers enjoyed it too, and said it was definitely something worth repeating. A lot of people told me afterwards that this was one of the highlights of their WordCamp. You honestly can’t ask for a better compliment. ([View Highlight](https://read.readwise.io/read/01khfmxt1hypvp5jbp5vs9mzx8)) - Tags: 👻 ai highlighted ## New highlights added February 15, 2026 at 12:03 PM - The more experienced WordCampers enjoyed it too, and said it was definitely something worth repeating. A lot of people told me afterwards that this was one of the highlights of their WordCamp. You honestly can’t ask for a better compliment. ([View Highlight](https://read.readwise.io/read/01khfmxt1hypvp5jbp5vs9mzx8)) - Tags: 👻 ai highlighted