WP Café #122 | Building Email Templates 😫  🔗 **Source:** [WP Café #122 | Building Email Templates 😫](https://www.youtube.com/watch?v=ZE03u1-JqO0) > [!note]+ Document Notes > tags: > - #wordpress > - #emailtemplates > - #agencylife > - #plugincustomization > - #webdevelopment > - #clientmanagement > - #pricingstrategy > - #knowledgebase > - #AItools > Author: Mark Wilkinson & Keith Devon > Source: WP Café Podcast Episode 122: Building email templates 😫 (YouTube) > Reference: https://www.youtube.com/watch?v=ZE03u1-JqO0 > date created: 2025-06-10 18:30 > > # Title: Building HTML Email Templates and Agency Life Challenges – WP Café #122 Notes > <!-- deep-read:sections start --> ## 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 - 🔍 SEO Evaluation - 🎯 Conclusion ### References: - WP Café Episode 122 (YouTube): https://www.youtube.com/watch?v=ZE03u1-JqO0 - Content Notify Plugin by Jack McConnell: https://wordpress.org/plugins/content-notify/ - Jonathan Stark on Value-Based Pricing: https://thestarkman.com/value-based-pricing/ - WordPress.com AI Website Builder Announcement: https://wordpress.com/ai-website-builder ## 📝 Summary: This episode dives deep into the real-world struggles of building and customizing HTML email templates for clients within a WordPress agency context. Mark Wilkinson and Keith Devon share their frustrations with archaic email rendering standards, plugin limitations (Content Notify), and the challenge of quoting and pricing work they have little prior experience with. They also discuss managing live product bugs (job relay queue system), knowledge retention for repetitive fixes, and their skepticism toward new AI tools such as WordPress.com’s AI website builder. Throughout, themes of client trust, transparency in quoting, and the tension between fixed and hourly pricing models emerge as central challenges for agencies. ## 📖 Main Content: Mark and Keith start by reflecting on typical agency life, with a focus on the often overlooked pain points in WordPress project delivery—specifically around email template building. They describe how modern web standards are still unsupported by many email clients, forcing developers into "table inception" HTML structures that are brittle and hard to maintain. Their attempts to customize the Content Notify plugin expose its limitations in email template flexibility, ultimately forcing code hacks to achieve desired outcomes. A significant portion of the discussion revolves around the difficulty of quoting and pricing custom work when the scope and complexity are unclear upfront. They weigh the pros and cons of hourly versus value-based pricing, emphasizing the importance of client trust and transparency. The duo also wrestle with the tension of delivering quality within tight budgets and uncertain timelines. Beyond email templates, they recount troubleshooting a memory limit error in a background job processing system (job relay), illustrating the unpredictable nature of live system debugging and the need for staged rollouts to minimize client impact. Finally, Mark and Keith share their ambivalence about AI tools—highlighting a failed attempt to use WordPress.com's AI website builder, which repeatedly times out, reinforcing skepticism about premature AI adoption in web development workflows. ### 🗒️ Notes #### 🎬 [0:03 - 2:00] Introduction and Agency Life Context - Hosts Mark Wilkinson and Keith Devon introduce WP Café episode 122 focused on email template building. - Brief chat about gardening and personal life to humanize the episode. - Early mention of AI discussions and their potential impact on development workflows. #### 🎬 [2:17 - 4:00] AI and Personal Communication Concerns - Keith expresses unease about AI's role in personal communication, noting discomfort with AI-generated emails feeling inauthentic. - Mark agrees but suggests deeper AI discussion is for another episode. #### 🎬 [4:00 - 7:30] Debugging Memory Issues in Job Relay Background Processing - Mark shares a frustrating experience fixing a memory limit error after deploying a queue system for job processing. - The issue didn’t appear locally but manifested on the live server, necessitating rollback and careful staged reintroduction for clients. #### 🎬 [7:58 - 14:00] Email Template Challenges and Content Notify Plugin Limitations - Keith reveals email templating remains archaic in 2025, requiring nested tables for consistent rendering across clients. - Content Notify plugin allows only minimal template customization; complex overrides not supported without hacking core plugin code. - Initial success in local environment does not translate to good rendering in Gmail, leading to significant frustration. #### 🎬 [14:30 - 16:30] Attempts with Online Drag-and-Drop Email Builders - Trying to use tools like Campaign Monitor and Mailchimp's drag-and-drop editors produces overly complex HTML unsuitable for direct plugin use. - After days of work, they revert to simple branding tweaks to meet client expectations. #### 🎬 [16:30 - 22:00] Pricing and Quoting Work with Unclear Scope - Hourly rates vs. fixed pricing debated, with uncertainty on how to quote when tasks could take vastly different times. - Trust in developer expertise highlighted as key for client willingness to accept hourly pricing. - A paid scoping phase is suggested to better estimate and avoid surprises, but real challenges remain in scoping unknown tasks. #### 🎬 [22:00 - 26:00] Client Budget Transparency and Managing Expectations - Clients often don’t disclose budgets, complicating quoting and prioritization. - Discussion about managing client expectations and offering options for custom builds vs. plugin configurations. #### 🎬 [26:00 - 34:00] Knowledge Retention, Documentation, and Learning from Mistakes - Both hosts express frustration about not remembering solutions to previously solved bugs or coding issues. - Suggest blogging or creating a knowledge base as a solution, but discipline and searchability are challenges. - Emphasizes documenting major fixes rather than every minor tweak to maintain sanity and productivity. #### 🎬 [34:00 - 38:00] WordPress.com AI Website Builder Experience - Mark shares failed attempts to use WordPress.com’s new AI website builder, which times out and produces no output. - Speculation about AI facade vs. human workers; frustration with the technology’s immaturity and reliability. ## 📖 References: - WP Café Episode 122 Transcript & Video: https://www.youtube.com/watch?v=ZE03u1-JqO0 - Content Notify Plugin: https://wordpress.org/plugins/content-notify/ - Jonathan Stark Value-Based Pricing: https://thestarkman.com/value-based-pricing/ - WordPress.com AI Website Builder: https://wordpress.com/ai-website-builder ## 🗣️ Paraphrase: 1. Original: "Email templating is horrific... you still have to do table inception, tables wrapped in tables wrapped in tables. It’s horrific." Paraphrase: Crafting email templates remains a frustrating ordeal because modern HTML and CSS standards aren't fully supported in email clients. Developers must resort to deeply nested tables, making the markup complex and hard to maintain. 2. Original: "But how do you quote for that work when you haven't done it? We had a stab, but completely failed miserably at getting the right quote." Paraphrase: Estimating the time and cost for unfamiliar projects is tough. Without prior experience, attempts to quote accurately often fall short, leading to misaligned client expectations and project challenges. ## 📰 Newsletter: Hey WordPress fans! This week on WP Café, Mark and Keith share the gritty realities of agency life tackling HTML email templates — a surprisingly tough nut to crack due to outdated email client standards. They dive into plugin limits, frustrating client requests, and the tricky art of pricing projects with unknown scopes. Plus, they battle a pesky memory bug in their job relay system and test drive WordPress.com’s AI website builder (spoiler: it’s still a work in progress). Whether you’re quoting your first project or debugging tricky templates, this episode serves up authentic insights and laughs from the WordPress trenches. Check it out here: [WP Café #122](https://www.youtube.com/watch?v=ZE03u1-JqO0). ## ✅ Action Items: - Share the realities of email template challenges with community contributors to set realistic expectations. - Advocate for better documentation and flexible plugin architectures that enable easier email customization. - Develop workshops or tutorials focused on quoting and pricing strategies for small agency projects. - Create knowledge base frameworks or encourage blogging for WordPress developers to capture solutions and lessons learned. - Monitor and test emerging AI tools in the WordPress ecosystem, offering feedback on usability and reliability. - Align these efforts with inclusive community education, supporting newcomers and fostering transparency in client communications. - Integrate learnings into OSPO initiatives promoting sustainable open source and equitable contributor engagement. ## 🧪 Hypotheses: - Agencies with structured knowledge bases and documentation experience fewer repeated bugs and reduced troubleshooting time. - Transparent client communication and paid scoping phases increase project satisfaction and reduce scope creep in WordPress projects. - Plugin architectures that enable full template overrides reduce developer frustration and improve customization outcomes. - Early AI adoption in web development will initially face adoption barriers due to reliability issues and unclear use cases. ### 📊 Methodology: - Conduct surveys of WordPress agencies on knowledge management practices and client communication strategies. - Case studies comparing projects with and without paid scoping phases for cost/time accuracy. - Technical audits of email template plugins assessing customization flexibility. - Usability testing of AI website builders with diverse developer groups. ### ❓ Questions: - How do agencies balance hourly vs. fixed pricing for small, uncertain projects? - What are the most effective strategies to educate clients on scope and budget transparency? - How can open source projects improve plugin design to support extensive template customization? - What early lessons can be drawn from WordPress.com’s AI website builder rollout? ### 🔮 Future Research: - Longitudinal studies on the impact of documentation habits on agency efficiency and client satisfaction. - Experimental frameworks for pricing models in open-source agency work. - Development of improved email templating standards and tools optimized for WordPress ecosystems. - Investigation into AI adoption barriers and enablers in CMS platforms. ### 💡 Implications: - Improved education and documentation can lead to better project outcomes and community growth. - Enhancing plugin flexibility empowers developers and reduces technical debt. - Clearer pricing frameworks foster trust and sustainable agency-client relationships. - AI tool maturation offers potential but requires cautious, community-driven development. ### 🧠 Learning Styles Assessment: - Visual Learners: - Present: Minimal visuals; mostly conversational audio/video content. - Improve: Add flowcharts of email templating structure or plugin customization options. - Aural Learners: - Present: Podcast format suits auditory learners well. - Improve: Provide downloadable transcripts or audio summaries. - Verbal Learners: - Present: Rich dialogue with practical examples and industry terminology. - Improve: Include more analogies or storytelling elements to simplify complex topics. - Physical Learners: - Present: Descriptions of hands-on coding and debugging tasks. - Improve: Suggest interactive workshops or coding exercises. - Logical Learners: - Present: Clear problem-solution discussions and stepwise debugging processes. - Improve: Incorporate diagrams showing cause-effect of plugin behavior or code flow. - Social Learners: - Present: Encouragement of community discussion via live comments and social media. - Improve: Create forums or group challenges based on episode topics. - Solitary Learners: - Present: Reflection on personal frustrations and strategies for knowledge management. - Improve: Provide journaling prompts or personal project planning templates. - Naturalistic Learners: - Present: Brief gardening references, lightly connecting nature and tech. - Improve: Use nature metaphors for system complexity or growth phases. ### 📊 Accessibility Assessment: - Screen Reader Compatibility: Audio transcript available, but some technical terms may require alt-text explanations. - Keyboard Navigation: YouTube platform supports keyboard navigation; podcast website details unknown. - Contrast and Readability: Clear audio and captions; written content should maintain high contrast and legible fonts. - Text Resizing: Transcripts and web content should allow responsive text scaling. ### 🌍 DEIB Assessment: - Cultural Relevance: Podcast content primarily UK-centric agency context; could include diverse cultural examples. - Inclusive Language: Gender-neutral, professional tone throughout. - Neurodiversity Support: Clear structure with short segments supports focus; more explicit summaries could help. - Representation: Hosts are male; involving more diverse voices would enhance inclusivity. - Psychological Safety: Open discussion of frustrations and uncertainties encourages a welcoming atmosphere. ### ✅ Logical validity: - **Sound Deductive Reasoning**: Clear cause-effect in debugging memory limit errors strengthens credibility ([4:00](https://www.youtube.com/watch?v=ZE03u1-JqO0&t=240), [6:08](https://www.youtube.com/watch?v=ZE03u1-JqO0&t=368)). - **Strong Inductive Reasoning**: Use of personal experiences to generalize common agency challenges enhances relatability ([7:58](https://www.youtube.com/watch?v=ZE03u1-JqO0&t=478)). - **Balanced and Nuanced Views**: Acknowledging pros and cons of hourly vs fixed pricing offers a well-rounded discussion ([18:28](https://www.youtube.com/watch?v=ZE03u1-JqO0&t=1108)). - **Logical Flow**: The episode smoothly transitions from technical problems to pricing and client management, aiding listener comprehension. - No major fallacies detected; the tone is reflective and honest rather than argumentative. Suggestions: Adding data or broader surveys would bolster inductive claims. ### 🔍 DARVO Analysis: - **Deny**: No denial of issues; hosts openly admit frustrations and limitations. - **Attack**: No ad hominem or attacking language towards clients or tools; critiques are constructive. - **Reverse Victim and Offender**: Not present; hosts take responsibility and express vulnerability. Tone: Cooperative, humble, and self-reflective, promoting trust and openness. ### 🔍 SEO Evaluation: - **Keywords**: Keywords like “WordPress email templates,” “agency life,” “plugin customization,” and “pricing strategies” appear naturally. - **Meta Description**: Not explicit in transcript but could be added for episode page. - **Title Tag**: Clear and relevant to content. - **Headers**: Properly structured in show notes and web posts. - **Content Length**: In-depth at ~39 minutes; transcript supports detailed content. - **Internal/External Links**: References to plugins, pricing experts, and WordPress AI tools provided. - **URL Structure**: YouTube URL clear and concise. - **Image Optimization**: N/A for audio content. - **Mobile Optimization**: YouTube and podcast platforms support responsive design. - **User Engagement**: Calls to action for comments and sharing are present. - **Schema Markup**: Episode pages could benefit from podcast schema. - **Social Sharing**: Enabled on YouTube and social platforms. ## 🎯 Conclusion: WP Café episode 122 offers a candid, detailed look at the everyday challenges faced by WordPress agencies—especially building and customizing email templates with outdated standards and limited plugin flexibility. Mark and Keith’s transparent dialogue about pricing, client communication, and knowledge management resonates with developers and agency owners alike. Their experience troubleshooting live system bugs underscores the unpredictable nature of agency workflows. The episode also captures early skepticism and hope regarding AI’s role in web development. Overall, the discussion highlights the need for better tooling, clearer pricing strategies, and stronger documentation to support sustainable and inclusive growth in the WordPress ecosystem. <!-- deep-read:sections end --> [[3. Resources/Readwise/Full Document Contents/Articles/WP Café #122 Building Email Templates 😫|Full Document Contents]] ## Highlights - Hello everybody and welcome to episode number 122 of the WP Cafe Show with myself, Mark Wilkinson, and as always, I am joined by my co-host, Keith Devon. We're both from High-Rise Digital, a tiny agency that builds WordPress websites and products. And this is the WP Cafe Show where we talk about the unfiltered, real-life agency life that the two of us kind of go through and discuss WordPress topics that relate to that. Today we're diving into HTML template building. We're looking at various other things, including quoting for work. A bit of an update on some work we talked about in previous episodes as well. ([View Highlight](https://read.readwise.io/read/01jxe28s8eyq6mq04z15nnjk3a))