WP Café #132 | WordPress Is Actually Amazing  🔗 **Source:** [WP Café #132 | WordPress Is Actually Amazing](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=2s) > [!note]+ Document Notes > tags: [WordPress, Block Editor, Agency] > author: [MISSING] > source: [WP Café Show] > reference: [https://www.youtube.com/watch?v=_PNsYG9gyzY] > date created: > > # 🏷️ Title: WP Café #132 | WordPress is actually amazing > > 🧰 **Action Inbox** > - [H1] Record a 3-minute Site Editor demo — context/https://www.youtube.com/watch?v=_PNsYG9gyzY&t=451 #articleseed > - [H3] Write “Editor-first change flow” guide — context/https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1420 #xref > - [H4] Publish “Shortcode block vs HTML block” fix — context/https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1659 #addendum > - [H6] Create a “Block theme by default” starter — context/https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1339 #articleseed > - [H7] Draft a productized “One-week WP site” offer — context/https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1757 #articleseed > - [H8] Pilot interview-led copy workflow with TTS — context/https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1966 #articleseed > - [H9] Compile evidence on lifetime licenses — context/https://www.youtube.com/watch?v=_PNsYG9gyzY&t=2268 #xref > - [H10] Prep “WordPress perception vs reality” talk — context/https://www.youtube.com/watch?v=_PNsYG9gyzY&t=917 #share > <!-- 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 - Two agency owners discuss WordPress strengths and pain points. - The block editor surprises clients and reduces developer handoffs. - Shortcodes misbehave in the shortcode block but work in HTML block. - Full site editing adoption continues; hybrid themes fade. - Pricing models and “build-in-a-week” services spark debate. - Bottom line: WordPress delivers power with sane workflows when configured well. ## 📖 Main Content - Hosts defend modern WordPress and show real client reactions. - The block editor supports patterns, grids, and site parts editing. See docs. (https://wordpress.org/documentation/article/wordpress-block-editor/) - Site Editor enables template and footer changes without code pushes. (https://wordpress.org/documentation/article/site-editor/) - They report a shortcode rendering issue in the shortcode block. The HTML block avoids `wpautop` artifacts. (https://developer.wordpress.org/reference/functions/wpautop/, https://developer.wordpress.org/plugins/shortcodes/) - Agencies shift toward block themes and away from hybrid approaches. (https://developer.wordpress.org/themes/block-themes/) - Productized offerings and value pricing appear viable. See Ditching Hourly. (https://podcast.ditchinghourly.com/) - Bullhorn’s public Jobs API enables direct listings pipelines. (https://developer.bullhorn.com/) - Lifetime licenses may reduce support contact frequency; the tradeoffs remain situational. Barn2 discusses pricing openly. (https://barn2.com/blog/, https://x.com/katiekeith) - Uncertainties: lifetime license sustainability varies; community marketing for WordPress needs clarity. ### 🗒️ Notes #### ⏱️ [00:07:31](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=451) Client demo and perception shift ### [H1] Block editor demo impresses new stakeholder > [!quote] [WP Café #132 | WordPress is actually amazing](https://www.youtube.com/watch?v=_PNsYG9gyzY) by [[WP Café Show]] via [[YouTube]]. Published [MISSING]. Accessed . > “Has she ever worked with the block editor before? No, she hasn't.” Simple demos change risk perception and reduce churn risk. [view highlight](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=451) #share #articleseed ID:rw_yt_0731 ### [H2] Editing footers in editor signals site control > [!quote] [WP Café #132 | WordPress is actually amazing](https://www.youtube.com/watch?v=_PNsYG9gyzY) > “And this is where you edit your footer.” Editing site parts builds client confidence and autonomy. [view highlight](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=451) #xref ID:rw_yt_0731b #### ⏱️ [00:08:52](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=532) Page builders vs core experience ### [H3] Page builders skew WordPress expectations > [!quote] [WP Café #132 | WordPress is actually amazing](https://www.youtube.com/watch?v=_PNsYG9gyzY) > “they just think that's what it is.” Clarify “core vs builder” to reset expectations. [view highlight](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=532) #articleseed ID:rw_yt_0852 #### ⏱️ [00:22:19](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1339) Full site editing adoption ### [H6] Team adopts block themes for new builds > [!quote] [WP Café #132 | WordPress is actually amazing](https://www.youtube.com/watch?v=_PNsYG9gyzY) > “we are providing full site editing.” Default to block themes; reserve hybrids for edge cases. [view highlight](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1339) #xref ID:rw_yt_2219 #### ⏱️ [00:23:55](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1435) Editor-first maintenance ### [H3b] Editor changes beat code pushes for content > [!quote] [WP Café #132 | WordPress is actually amazing](https://www.youtube.com/watch?v=_PNsYG9gyzY) > “I'd rather edit a footer template in the editor.” Use the Site Editor for non-code content changes. [view highlight](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1435) #xref ID:rw_yt_2355 #### ⏱️ [00:25:59](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1559) Shortcode rendering issue ### [H4] Shortcode block adds unwanted paragraphs > [!quote] [WP Café #132 | WordPress is actually amazing](https://www.youtube.com/watch?v=_PNsYG9gyzY) > “it is full of empty paragraph tags break tags etc.” `wpautop` formatting can pollute markup in that context. [view highlight](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1559) #addendum ID:rw_yt_2559 #### ⏱️ [00:27:44](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1664) Workaround ### [H5] HTML block renders shortcode cleanly > [!quote] [WP Café #132 | WordPress is actually amazing](https://www.youtube.com/watch?v=_PNsYG9gyzY) > “use the HTML block... it literally removes all of the break tags.” Prefer HTML block for shortcode output in templates. [view highlight](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1664) #articleseed ID:rw_yt_2744 #### ⏱️ [00:29:17](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1757) Productized services ### [H7] One-week site builds signal productization > [!quote] [WP Café #132 | WordPress is actually amazing](https://www.youtube.com/watch?v=_PNsYG9gyzY) > “she builds websites in a week.” Time-boxed delivery clarifies scope and value. [view highlight](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1757) #articleseed ID:rw_yt_2917 #### ⏱️ [00:32:46](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1966) Copy process ### [H8] Interview-led copy beats client-written drafts > [!quote] [WP Café #132 | WordPress is actually amazing](https://www.youtube.com/watch?v=_PNsYG9gyzY) > “The way they write about themselves is terrible.” Transcribed interviews capture authentic voice and benefits. [view highlight](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=1966) #articleseed ID:rw_yt_3246 #### ⏱️ [00:37:48](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=2268) Pricing signals ### [H9] Lifetime customers contact support less often > [!quote] [WP Café #132 | WordPress is actually amazing](https://www.youtube.com/watch?v=_PNsYG9gyzY) > “lifetime customers contact support less often and for no longer” Consider lifetime pricing where data supports sustainability. [view highlight](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=2268) #xref ID:rw_yt_3748 #### ⏱️ [00:15:17](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=917) Industry narrative ### [H10] WordPress still faces perception problems > [!quote] [WP Café #132 | WordPress is actually amazing](https://www.youtube.com/watch?v=_PNsYG9gyzY) > “WordPress obviously has a image problem” Address myths with simple, verifiable demos. [view highlight](https://www.youtube.com/watch?v=_PNsYG9gyzY&t=917) #share ID:rw_yt_1517 ## 📚 References - WordPress Block Editor overview — https://wordpress.org/documentation/article/wordpress-block-editor/ - Site Editor user guide — https://wordpress.org/documentation/article/site-editor/ - Block themes documentation — https://developer.wordpress.org/themes/block-themes/ - Shortcodes reference — https://developer.wordpress.org/plugins/shortcodes/ - `wpautop` reference — https://developer.wordpress.org/reference/functions/wpautop/ - Bullhorn Developer Center — https://developer.bullhorn.com/ - Ditching Hourly podcast — https://podcast.ditchinghourly.com/ - Barn2 blog (pricing/lifetime posts) — https://barn2.com/blog/ - Video — https://www.youtube.com/watch?v=_PNsYG9gyzY ## 🗣️ Paraphrase - The hosts argue WordPress is strong when teams use native tools well. - They share fixes, service models, and pricing ideas to improve outcomes. ## 📰 Newsletter - WordPress keeps surprising clients when we showcase the Site Editor. - Try the HTML block for shortcodes in templates to avoid stray `<p>` tags. - Thinking about productized services? Time-box a one-week build and document scope. - Pricing chat: lifetime licenses may work when data says support stays low. - Links: Block Editor docs, Site Editor guide, shortcode tips, and Ditching Hourly. ## ✅ Action Items #### DevRel - Ship a short Site Editor demo with captions and a checklist. - Create “Shortcode in HTML block” snippet with before/after screenshots. - Add a “Perception vs reality” slide to talks with measured metrics. #### OSPO - Document “editor-first changes” policy for content-only updates. - Track plugin license types across estates; note renewal risk. - Maintain an approved API list including Bullhorn with data flow diagrams. #### Community - Host a meetup segment on native patterns and templates. - Pair contributors on block-theme conversions with office hours. - Publish a support playbook for lifetime vs annual customers. #### WordPress - Core: triage shortcode block formatting issues with clear repro steps. - Core Performance: profile editor pages with popular plugin stacks. - Core AI: draft guardrails for caption generation and alt-text QA. - **Core Program Team:** schedule UX walkthroughs for Site Editor pitfalls. - Playground: template-editing labs focused on footers and headers. - Training: lesson on “Grid + Patterns” for non-dev editors. - Marketing: run a “This is WordPress now” campaign with real clips. - Documentation: clarify shortcode block vs HTML block behaviors. - Accessibility: validate template editing flows with screen readers. - Meta: add “native vs builder” comparison explainer on .org. #### The WPOCC - Fund microgrants for block-theme conversions and docs sprints. - Run governance clinics on plugin pricing transparency. ### FAIR - Draft pricing covenants with sunset clauses and public metrics. - Publish provenance guidelines for editor changes and API integrations. ## 🧪 Hypotheses - H1: Live demos increase client retention for agencies using block themes. - H2: Using HTML block for shortcodes lowers formatting bugs by 80%. - H3: Interview-led copy boosts conversion rates versus client-written copy. - H4: Lifetime licenses reduce annual support tickets per customer. ### 📊 Methodology - Run A/B demos across new leads; track close and churn. - Instrument shortcode outputs; compare bug counts per block type. - Test landing page variants: interview-derived copy vs baseline. - Analyze support tickets by license cohort over 12 months. ### ❓ Questions - Where should WordPress explain “core vs builder” most effectively? - Which editor controls still block common site patterns? - What license mix best balances revenue and support capacity? ### 🔮 Future Research - Map editor UX gaps to plugin patterns and mitigations. - Evaluate structured patterns libraries for repeatable layouts. - Study lifetime pricing effects on MRR and valuation. ### 💡 Implications - Agencies can shorten cycles with editor-first workflows. - Productized offerings simplify scope and improve margin clarity. - Transparent pricing builds trust and reduces sales friction. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade ~10 based on sentence length. #### 👀 Visual learners - Present: screenshots of editor, patterns, before/after. - Improve: add grid and template diagrams with captions. #### 🔊 Aural learners - Present: conversational podcast-style video. - Improve: 3-minute narrated summary and downloadable audio. #### 🗣️ Verbal learners - Present: clear definitions for Site Editor and patterns. - Improve: analogies comparing builders to core tools. #### 🧩 Kinesthetic learners - Present: encourage Playground hands-on edits. - Improve: stepwise labs with checklists and success criteria. #### 🧠 Logical learners - Present: pros/cons of license models and workflows. - Improve: decision trees for “editor vs code change.” #### 🧑‍🤝‍🧑 Social learners - Present: open Q&A and comments. - Improve: cohort practice sessions with peer review. #### 🧘‍♀️ Solitary learners - Present: written summaries and links. - Improve: self-check quizzes and reflection prompts. #### 🌿 Naturalistic learners - Present: none explicit. - Improve: sustainability of open ecosystems and community funding. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: headings and structure in this note. - Improve: confirm alt text and region landmarks in demos. #### Keyboard navigation - Present: standard focus behavior in editor. - Improve: test skip links and tab order in templates. #### Contrast and readability - Present: adequate contrast in examples. - Improve: enforce 4.5:1 and line-height guidance in style guides. #### Text resizing and reflow - Present: responsive editor UI. - Improve: verify 200% zoom and reduced motion support. #### Media and captions - Present: YouTube auto-captions. - Improve: edited captions and downloadable transcripts. #### Forms and interactions - Present: none central here. - Improve: accessible error messages and target sizes in examples. #### Standards reference - Map gaps to WCAG 2.2 AA; track fixes. ### 🌍 DEIB Assessment #### Cultural breadth - Present: UK agency context. - Improve: multi-region examples and multilingual notes. #### Inclusive language - Present: mostly neutral phrasing. - Improve: add plain-language glossaries and avoid idioms. #### Neurodiversity support - Present: chunked sections and predictable structure. - Improve: icon+text labels and consistent patterns in demos. #### Representation - Present: limited speaker diversity on screen. - Improve: balanced quoting and inclusive imagery. #### Psychological safety - Present: respectful tone. - Improve: publish participation guidelines and escalation paths. ### ✅ Logical Validity #### Strong reasoning - Inductive: client demo reactions imply improved satisfaction ([H1], [H2]). - Pragmatic: editor-first changes reduce deployment overhead ([H3b]). - Empirical: HTML block workaround matches observed output ([H5]). #### Fallacies - Possible hasty generalization: lifetime licenses lower support broadly ([H9]). - Fix: scope to one vendor’s data and request replication. - Survivorship bias risk: productized week builds cited from one example ([H7]). - Fix: compare across markets and tech stacks. #### Tone of voice - Conversational, practitioner-focused, with candid admissions and fixes. ### 🛡️ DARVO Analysis - Deny: none apparent. - Attack: none; critique stays on tooling, not people. - Reverse victim/offender: none detected. - Emotional cues: practical frustration with blocks; optimistic outcomes. ## 🎯 Conclusion - Modern WordPress works well when teams lean into native tools. - Prioritize simple demos, editor-first changes, and measured pricing. - Share repeatable fixes like the HTML block workaround. - Keep teaching the difference between core WordPress and builders. ## 🏷️ Tag Coverage #articleseed: 4 • #xref: 3 • #share: 2 • #bmf: 0 • #addendum: 1 ## 🧱 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] 5–10-word present-tense claim > [!quote] [{Title or entity}]({ARTICLE_URL}) by [[{Author or [MISSING]}]] via [[{Site or [MISSING]}]]. Published {DATE_OR_[MISSING]}. Accessed . > “Short quote, verbatim, ≤25 words.” Two lines: context and use. Cite data if relevant. [view highlight]({ARTICLE_URL}#H1) #xref #articleseed ID:rw_[MISSING] ### [H2] 5–10-word present-tense claim > [!quote] [{Title or entity}]({ARTICLE_URL}) > “Short quote, verbatim, ≤25 words.” Two lines: context and use. [view highlight]({ARTICLE_URL}#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] 5–10-word present-tense claim - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[Parent-Concept]] [[Related-Idea]] #### [Z2] 5–10-word present-tense claim - Scope/condition in one line. - Pointer to page/time or dataset. - Links: [[Parent-Concept]] [[Related-Idea]] --- ### ✏️ 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] Short action — context/{ARTICLE_URL} #fleeting #inbox - [F2] Short action — context/{ARTICLE_URL} #fleeting #inbox - [F3] Short action — context/{ARTICLE_URL} #fleeting #inbox --- <!-- deep-read:sections end --> [[3. Resources/Readwise/Full Document Contents/Articles/WP Café #132 WordPress Is Actually Amazing|Full Document Contents]] ## Highlights - there's a there's a sort of of a premise to why that is the case. I'll come to that in a minute. Uh a little bit about short codes. Um uh you've added I think you've added something about productized web services. >> Y >> um various other little things as well. >> So we'll get on to that. Uh where should we start? What do you reckon? >> Let's start with the headline topic. >> Okay. >> Well, we call it kind of WordPress is amazing in our show notes. It's defending WordPress. So it's it's kind of >> a little bit of both. And I think this ([View Highlight](https://read.readwise.io/read/01k8e5ye8bakkyvdt1dm85stcv)) - Tags: 👻 ai highlighted - used WordPress before. >> Yeah. >> And when when we sort of introduced the fact we're going to do this demo or we've used WordPress before, >> there was a bit of a not like a negativity, you know, like WordPress before. So clearly her experience of WordPress was was was nothing to do with the block editor. Of course, I'm I'm suspecting it was one of the big page builders and that's what people who come from that, you know, if that's all you've seen in a WordPress website, that's what you think ([View Highlight](https://read.readwise.io/read/01k8e5ye9ft24ab5s00m1knpe8)) - Tags: 👻 ai highlighted - literally like, "Oh my goodness, wow." It's like, yeah, I mean, this is four, five year old, nearly sixy old technology now that people are still amazed amazed at that and and amazed that it's WordPress that's that's doing that. It's like there there's a real there's a real problem in this industry and I think it's the problem Matt was trying to solve to be fair to him with the Gutenberg project is that WordPress almost has too many flavors and you don't really know what you're getting when you get a WordPress ([View Highlight](https://read.readwise.io/read/01k8e5yebyzhrpcwz7yms9hcng)) - Tags: 👻 ai highlighted - website. Whereas if we can if we can find a way to show off what you get out of the box and what it's capable of, I don't know. I think that could help us win a whole lot more work. Um I think so. Yeah, whether that's assets that we create personally or we do it as a community or both or I I don't know. >> I think yeah, I think there could be something that belongs to WordPress that we can use. Um but that isn't there at the moment. So I think we're going to have to build something or make something. Mark, thank you. says, "Make ([View Highlight](https://read.readwise.io/read/01k8e5yee4n24dfp3xz13aeg0z)) - Tags: 👻 ai highlighted - So we could probably do show what we can do today to our current clients. >> Yeah, I don't disagree with that for sure. But I'm thinking like we've we've recently lost a client who's just just launched their new website now with their new partner using WordPress. So they're not, you know, they haven't moved platforms. Um, didn't leave them in bad terms or anything like that. It was obviously fine. But what we built for them obviously it was an old technology because what what they had up until the new one launched, you know, a few few weeks ago was an old ACF flexible ([View Highlight](https://read.readwise.io/read/01k8e5yeh4m5aaeq6n5x72k3qg)) - Tags: 👻 ai highlighted - what people care about and they just care is it going to look nice? Is it going to work well? Can I add content if I need to kind of thing and maybe Sam's right that we should deemphasize WordPress to some extent. I'm not convinced by that yet, but it's certainly an angle. It's certainly something that you could do and that people do do. >> Yeah, it's an interesting idea. Definitely. Mark agrees with Sam. The first stage isn't to sell WordPress. It is to sell how you solve the client's problems. Yep. Yep. Don't disagree with that. Um, ([View Highlight](https://read.readwise.io/read/01k8e5yem92n356fxztw9ep8p6)) - Tags: 👻 ai highlighted - understand that you can you can put a price against? So, I listened to this and it is a lady from the States and she uh she builds websites in a week. That's her that's her thing. Um, and I like that as well because a week sounds like a decent amount of time. She does it in Squarespace. She talks about the fact that she chose Squarespace because it's the easiest for her to do quickly and it's easiest for her clients. Um, she wasn't bashing other platforms, but like in her experience, it was the best, ([View Highlight](https://read.readwise.io/read/01k8e5yesvfcbc7abczctmsnq2)) - Tags: 👻 ai highlighted - helps them build it in Squarespace. They pay for Squarespace, their own account, I guess. >> Yeah. >> And then Yeah. Yeah. Nice and clean, I guess. >> It's It's clean, but that that kind of model does doesn't drive well with me and how I want to do things. >> Yeah. >> No, I Yeah, I'd agree with that. But yeah, >> but then it's the balance between like, do you want 50 people on a support contract? >> You know, if you're building one website a week, you've got to you you've got to ([View Highlight](https://read.readwise.io/read/01k8e5yf1hk7jtqzh39cfq4xbr)) - Tags: 👻 ai highlighted - >> haven't bought for the last couple of years and it always a good opportunity." But yeah, WordPress I just I I kind of don't understand the Black Friday thing in the WordPress world. But there there you go. Like who's who's waiting around to for a deal before they buy Gravity Forms? It just seems odd to me, >> but it seems to work. People do it. So, >> yeah. Well, yeah. >> Um, last one from from me. I saw this on Twitter. Uh, lifetime licenses are worth ([View Highlight](https://read.readwise.io/read/01k8e5yf5wgs9ree79zdk0w4b9)) - Tags: 👻 ai highlighted