Advertise on podcast: No Script Show

On the podcast today we’re tackling the future of website creation in the age of AI. The conversation focused on what AI means for website owners and creators, whether chatbots that generate stunning sites in seconds are the next big thing or a risky trap. Several points were raised, including the long history of AI hype cycles, the actual abilities (and serious limits) of large language models (LLMs), and the broader, sometimes eccentric philosophies driving Silicon Valley’s biggest players. We start off with a historical and sociopolitical perspective, referencing new books like AI Snake Oil, The Reverse Centaur’s Guide to Life After AI, and The Nerd Reich. One concept discussed was how AI predictions often fall short, sometimes doing little more than flipping a coin, and how this hasn’t stopped big tech from chasing hype (and investment) over tangible results. The discussion explored what LLMs can actually do for web professionals: outlining content, explaining code, and serving as a speedy second pair of eyes, but also highlighted what these models can’t touch: local insight, real business nuance, long-term accountability, and authentic creativity. A key theme that emerged was the growing risk of “automation blindness” and the erosion of real skills as more practitioners become dependent on AI tools. There’s also a pragmatic look at current debates among web creators: Will AI automate away the easy jobs? Do clients only care about quick results? Does AI make everyone creative, or just more dependent on platforms? Towards the end, the episode dives into an LLM-generated “manifesto” for web professionals, covering everything from treating generated code with caution to focusing on judgment over keystrokes, and championing platform independence for clients. If you’ve ever wondered where your role as a web creator fits in a world of generative AI, and how to balance automation with meaning and community, this episode is for you.

On the podcast today, we’re diving into the “rule of least power”, a cornerstone idea from the World Wide Web Consortium (W3C) that’s shaped how we build for the open web. The conversation focused on why you should often choose the simplest, least powerful technology for the job. The episode starts with a practical introduction: the rule’s roots in the thinking of Tim Berners-Lee (the often-cited founder of the web), Occam’s razor, and the ever-relevant KISS (“Keep It Simple, Stupid”) principle. One concept discussed was how the rule of least power encourages us to reach for HTML and CSS first, before introducing the extra complexity of JavaScript or heavy frameworks, and why that’s kept the web interoperable, accessible, and remarkably resilient. A key theme that emerged was the ongoing tug-of-war between innovation and over-complication. The discussion explored how trends in web development, including the rise of JavaScript-heavy sites and app-like experiences, at times have upturned this principle, but also how modern CSS has been reclaiming ground from JavaScript. Several points were raised, including practical ways for website owners and WordPress professionals to make decisions that keep their projects future-proof, portable, and easy to maintain. If you want to understand why simplicity leads to better web experiences, how to avoid locking your content in, and what this all means for WordPress practitioners, this episode is for you. 00:00 Rediscovering HTML and web passion 03:35 Philosophy and creativity on the web 08:03 Interoperability limitations and challenges 10:42 Jeff Atwood's 2007 blog post 16:13 Discussing declarative solutions in CSS 18:34 AI improving web design challenges 21:32 Overuse of web animations 23:32 Importance of HTML and CSS 27:15 Designing a trustworthy user interface 33:11 Distrust of big tech companies 34:05 Critique of new tech impacts

On the podcast today, we’re diving into the world of modern web standards and what it means to build truly resilient, future-proof sites. The conversation focused on the foundations of web standards, what they are, why they’re essential, and how they shape the way we build sites now. Starting off with a look at the evolution of web standards, from the early days of the W3C and the chaotic browser wars, the discussion explored how we could easily have ended up with a far more closed and proprietary web, and just how fortunate we are that open standards prevailed. We also got into the ongoing importance of semantic HTML, accessibility, and progressive enhancement. Several points were raised, including how separating content, presentation, and behaviour leads to more maintainable and robust sites, and how modern standards reduce technical debt, improve performance, and keep projects accessible to more people for longer. Towards the end we talk about the very real temptation to use flashy new features or proprietary solutions, and the balance that site owners and developers need to strike between innovation and resilience. The discussion moved through the core principles of web standards, from responsive design to security and privacy, and how even non-technical site owners can encourage best practices, focus on meaningful structure, and regularly review for outdated or fragile tech. If you’re interested in the big-picture values that underpin a robust, open web, are curious about how standards make your sites better for everyone, or want to know how to future-proof your projects without getting lost in technical jargon, this episode is for you.

On the podcast today David Waumsley and Nathan Wrigley dive into the world of agile development, focusing on how websites can, and perhaps should, be treated as living products that evolve over time, rather than as static, one-off deliverables. David and Nathan unpack what agile development really means for web designers and website owners, explaining the mindset shift needed to move away from the “perfect launch” mentality and toward an approach built on small, continual improvements. We start by hearing about the core principles of agile, starting with a minimum viable product, iterating in small increments, and letting real-world feedback drive decisions. There’s discussion around the history of agile, tracing its roots back to the Agile Manifesto and how its values, like “individuals and interactions over processes and tools” and “responding to change over following a plan”, challenge traditional, rigid development models. You’ll also hear why adopting agile isn’t just about following a specific scrum process, but about embracing a collaborative, flexible mindset that helps reduce risk, keeps your site responsive to change, and ultimately delivers more value to users. David and Nathan share how agile practices are being applied far beyond software, touching fields as diverse as marketing, education, and banking, and what this means for client relationships and project delivery in web development. If you’ve ever struggled with projects that derail, clients worried about “scope creep,” or the stress of hard deadlines, this episode will challenge your assumptions. It’ll give you practical insights into putting agile into practice: from choosing what features to launch first, to capturing feedback and letting go of what’s not useful. If you’re ready to rethink how you approach web projects for happier clients and better results, this episode is for you. 00:00 Discussing agile development approach 04:44 Understanding continuous software development 06:36 Benefits of Incremental Development 10:31 Understanding Agile Principles 16:18 The benefits of an agile approach 17:58 Agile manifesto and methodology discussion 22:45 Launching a Usable Website Quickly 25:44 Misunderstandings about Agile process 29:06 Agile principles in web development 30:03 Wrapping up the episode

On the podcast today we have a conversation all about inclusive design. In this episode, we break down what inclusive design is, why it matters, its historical evolution, core principles, and how website owners and designers can apply it to their own projects. We begin by discussing the fundamental nature of the web as a platform where, unlike the offline world, inclusivity can often be achieved at minimal cost simply by following standards, an opportunity the industry has too often overlooked. David shares insights from the Website Owner’s Manual, describing the “five pillars” behind building better sites, and why inclusive design sits at the top. We go on to explore how inclusive design goes beyond basic accessibility compliance, actively seeking out who might be excluded and working to remove those barriers, treating diversity as a default rather than an edge case. Nathan reflects on how the (often invisible) difficulties that people face online are less likely to be addressed due to a lack of visible cues and legal pressure. Corporate approaches from tech giants like Microsoft, Google, and Apple are discussed, along with the reality for smaller web professionals who might struggle to justify the investment. David argues that if web standards and good code are prioritised from the outset, inclusive websites don't have to create extra burdens. The conversation then turns to history, tracing the evolution from post-war “barrier-free design” to modern inclusive design, and how concepts like dignity and flexibility are at the heart of truly accessible user experiences. We try to unpack the ethical, reputational, and practical advantages for brands that embrace inclusivity, and point out that, often, what benefits people with specific access needs ends up benefiting everyone. Practical advice for website owners and designers follows, such as using semantic HTML, testing with real users and assistive technology, avoiding reliance on colour alone, and picking images and content that genuinely reflect a diverse audience. We caution against deceptive “dark patterns” and warn of the pitfalls of delegating too much to AI or generic page builders, emphasising the importance of human-centred design thinking. Throughout, the need for ongoing, collaborative practices is highlighted, inclusive design is a process, not a checkbox. We close with a reminder that, when done right, inclusive design not only costs less in the long run but pays dividends for everyone, users and creators alike. If you’ve ever wondered how to make your websites work better for everyone (and not just tick boxes), this episode will give you actionable insights, some history, and plenty to reflect on for your next project.

What Is Content Design? It's a discipline created by Sarah Richards (now Winters) while transforming GOV.UK from hundreds government websites into a single resource. It has been adopted by other governments such as the US, Australia, and New Zealand. Meta (Facebook) formally switched to content design, embedding content designers across every product team. Companies like Shopify, Atlassian, Apple, Google, and Microsoft have followed. Why It Matters. Most websites are written inside out - reflecting what the organisation wants to say. Content design flips that and starts with what users are actually trying to do.

On the podcast today we have David Waumsley and Nathan Wrigley. David and Nathan are diving into the world of website owner’s manuals, a concept inspired by Paul Boag’s influential book, but brought firmly into the present day, with a focus on everyday website owners, small businesses, and web designers who care about empowering their clients. Drawing on decades of experience building and managing websites, David has crafted an in-depth, living document inside Canva (but designed to be platform-agnostic) that aims to give website owners a comprehensive guide for project management, strategic planning, and brand assets. If you’ve ever struggled with unclear communication between designer and client, or wished for more independence in managing your website, this episode is for you. David and Nathan discuss the evolution from classic brand style guides, documents focused primarily on logos and colours, to holistic website owner's manuals that cover business objectives, brand voice, technology choices, accessibility, and governance. Along the way, they revisit the lessons learned from early web design days and address the friction that so often arises between technical experts and business owners. They walk through the structure of David’s owner’s manual, over 50 pages and growing, detailing pipeline steps like mission and messaging, technology requirements, visual identity, and even legal and ethical considerations. This is not just theory, they share practical tips for real-time collaboration, asset management, and making the manual a valuable resource whether you’re starting your first one-page site or scaling up. If you want your web projects to start on the right foot, and avoid common pitfalls when building for yourself or your clients, you’ll find plenty of actionable advice in this episode. And if you’ve never created a style guide or website manual before, David and Nathan break down the whys and hows, helping you build more sustainable, maintainable, and independent online presences. Whether you’re a designer, a business owner, or simply interested in better website planning, this conversation will give you a roadmap for approaching digital projects with clarity and confidence. 00:00 Website Owner's Manual Concept 05:45 "Platform-Agnostic Presentation Approach" 07:53 Website Style Guide & Design Tools 12:52 "Problem-Solving Before Product Building" 15:43 Website Navigation & Client Guidance 19:31 Document Structure Overview 23:27 "Building Trust for Rankings" 25:20 "Building a Clear Brand Identity" 29:11 "Content & Voice Guidelines" 32:48 Authentic Brand Voice Matters 35:24 "Website Content and Writing Guidelines" 37:54 Visuals: Complement, Not Replacement 43:57 "Design Systems: Test and Simplify" 46:34 "Accessible Web Design Priorities" 49:50 Branding Across Platforms 53:46 Website Analytics and Governance Insights 54:36 Website Review and Compliance Tips 58:01 "Creating a Central Resource Hub"

UntitledAre you a small business owner thinking about getting a website? In this episode, David Waumsley and Nathan Wrigley break down the real traps and trade-offs of using no code website builders versus hand coding your site. - How the commercial website builder market is taking over—and what that means for business owners - The surprising decline of hand-coded websites and why HTML still matters - The hidden costs and limitations of using platforms like Wix and Squarespace - A practical walkthrough of building a simple one-page business site from scratch - Why simplicity, clear messaging, and owning your code can set you apart from the competition Want to avoid vendor lock-in and make smarter website choices? Dive in for actionable advice and real-world examples.

This episode looks into how platforms lure us in, lock us down, and extract value from everyone and how small, independent websites can push back. What this episode covers The 3 stages of Enshittification (Cory Doctorow’s framework applied to web platforms) Real‑world examples: Facebook, Amazon, Google How interoperability was intentionally broken and antitrust was weakened The hidden human labour and exploitation behind “AI magic” The rise and hangover of vibe coding (Karpathy, YC, GitClear findings) Why AI‑generated codebases are brittle and hard to maintain Tim Berners‑Lee, the fight to keep the web in public ownership, and why the web is for everyone Practical ways web designers and developers can reclaim agency: Static sites and the “dumb web” IndieWeb and POSSE (Publish on your Own Site, Syndicate Elsewhere) Using AI as a tool, not a master If you’ve been feeling uneasy about AI hype, social media, and the state of the modern web, this episode might help connect the dots and point to a healthier, more human direction for making websites. Mentioned in this episode Cory Doctorow – Enshittification: Why Everything Suddenly Got Worse and What to Do About It Karen Hao – Empire of AI: Dreams and Nightmares in Sam Altman’s OpenAI Yanis Varoufakis – Technofeudalism Tim Berners‑Lee – This Is for Everyone Ed Zitron – Better Offline (podcast & newsletter) Carl Brown – Internet of Bugs (YouTube channel) IndieWeb & POSSE (Publish on your Own Site, Syndicate Everywhere)

On the podcast today we have David Waumsley and Nathan Wrigley. David and Nathan have been helping local businesses build websites for years, gaining insight into the world of digital marketing and the challenges faced by small business owners, from vets and accountants to electricians and therapists. In this episode, they turn their attention to Google Ads, demystifying pay-per-click advertising for those new to it. With the rapid shift from traditional marketing, think local papers and radio, to digital options, spending your marketing budget wisely is more important than ever. David begins by sharing his experiences supporting clients as they navigate Google Ads: requests to set up tracking scripts, questions about campaign managers, and a recent odd appointment with Google’s own support team. There’s skepticism, are Google’s new beginner-friendly moves as helpful as they seem? As Google adapts to challenges in its search dominance, the duo explore what this means for newcomers. Nathan and David then break down the landscape. Why is Google so powerful? What do statistics about return on investment actually mean, and why do most small businesses lose money? They discuss the differences between traditional and digital marketing, explaining why driving more traffic is pointless unless your offer really connects. Using the story of Bob Smith, a landscape gardener, they illustrate common mistakes, like sending ad traffic to generic homepages and neglecting the power of targeted messaging and landing pages. They contrast this with the marketing-savvy approach of Bob’s wife, Mary, who uses landing pages, keyword research, urgency, and lower-risk conversion options to boost results. The conversation digs deeper into Google Ads practicalities: negative keywords, location targeting, conversion tracking, and why “set it and forget it” just doesn’t work. There’s talk of budgets and timelines, and the importance of time and skill regardless of whether you DIY or hire an expert, along with the red flags to look for if you do. Finally, David and Nathan round off with a checklist for getting started: optimise your Google Business profile, learn about local service ads, invest in onsite SEO, and always start by clarifying your business problem before jumping in. If you’re a local business owner, or guiding one through the world of online advertising, this episode is packed with actionable advice, real-world stories, and critical perspectives on how to avoid costly mistakes with Google Ads.

Nathan Wrigley and David Waumsley are the hosts of the No Script Show, and in this episode, they’re diving into the vast topic of website forms. Forms, as they point out, are what make the web interactive, without them, you can’t do things like search, comment, shop online, or even book an appointment. But adding forms, especially to static websites, can be a lot more involved than it first appears. They start by sharing their personal journeys and frustrations with forms, both as web developers and as people helping clients with website interactivity. They discuss the explosion in the number of static and hybrid sites, and the need for third-party form solutions if you’re not using a dynamic platform like WordPress. The conversation ranges from specific client expectations, like the belief that ‘if you build a booking form, bookings will magically come’, to why forms can be both a blessing and a pain to administer. They unpack when you might actually need a form, and look into some eye-opening statistics about contact forms, such as how they typically convert much less than direct clickable emails or phone numbers. Along the way, Nathan and David look at alternatives to forms, like WhatsApp links and website chat, and why simply putting a phone number on the site could sometimes be the best UX decision of all. For those who do need a form, the hosts provide an overview of the different options available, from DIY setups using third-party endpoints like FormSpark, all the way up to full-featured SaaS form builders such as Jotform, Paperform, and Tally. They touch on accessibility, cost, performance, spam issues, and how keeping things simple can often be the smartest move. If you want to understand the real value, challenges, and modern choices for website forms, whether you run static sites, work with WordPress, or are helping clients decide what’s best, this episode is for you.

This is the fourth episode in our ongoing series about the different components that make up a website, and today we’re diving deep into the world of testimonials, block quotes, pull quotes, and the cite element, and why so many of us are probably coding them all wrong. Nathan and David take a look at how these quote elements are handled from technical, design, accessibility, and SEO perspectives. Inspired by resources like Kevin Powell’s “Is HTML the Hardest Language?” and the work of Hayden Pickering, they set out to demystify the (often confusing) specifics of semantic HTML, particularly around quotes and citations. We start with the basics: where quotes show up, be it testimonials for credibility, comments for engagement, or pull quotes for stylistic flair, and debate what pull quotes really are. Then, they walk through the evolution of HTML specifications, the ongoing confusion around the best markup for quotations, and how expert voices like Hayden Pickering and Adrian Roselli suggest different, sometimes contradictory approaches to structuring quotes, citations, and testimonials. You’ll learn why using blockquote for pull quotes isn’t recommended, and why the cite element doesn’t always do what you think, or anything useful at all. David and Nathan talk through common patterns for testimonials (with author images, company names, and more), how to structure them for maximum meaning and accessibility, and why major platforms like WordPress often stray from the specification. The episode also covers the practicalities: how to rationalise your code, how to use article and aside elements when appropriate, and even touches on the perennial pull quote debate, are they worth the trouble (especially for screen readers and responsive layouts)? If you’ve ever wondered how to properly mark up quotes and testimonials in your HTML, and how to future-proof your work for accessibility and SEO, this episode is for you.

This is the third episode in the series exploring the different components that make up a website, and today’s focus is on the often-overlooked but vitally important head element in HTML. Nathan and David kick things off by admitting that, like many web professionals, they haven’t thought deeply about the head for quite some time, despite its massive impact on performance, accessibility, and SEO. Drawing from their own experiences as CMS users and enthusiasts, they dig into what the head is, the key tags you can (and must) use, and which practices are still essential in modern web development. They cover everything from the basic meta tags you need for setting character encoding, viewport scaling, and page titles, to why the order of scripts and styles in your head can dramatically affect site speed and user experience. David explains some of the technical nuances, like choosing between inline styles and external stylesheets and recent updates that now allow for SVG favicons with light and dark mode support, thanks to the latest version of Safari. They also discuss SEO considerations, such as canonical tags, language declarations, and social sharing metadata, along with hands-on tips to help you validate your sites and avoid common mistakes, like using special characters in titles that may trip up screen readers or search engines. If you build or maintain websites and haven’t recently double-checked your head element, this episode is well worth your time. By the end, Nathan and David will have you rethinking and refreshing your approach to the head of your HTML, ensuring you’re setting up your sites for the best possible technical, SEO, and accessibility outcomes.

On the podcast today, we’re joined by Paul Lacey. Paul has been working in web design and development since 1999, and in that time he’s witnessed the evolution of the industry from the early days without CSS, through the dot-com boom, to the modern era of design systems. He’s put together his own design systems for professional and client work, and brings first-hand, practical experience to our chat. Paul joins our regular hosts, Nathan Wrigley and David Waumsley, to help demystify what “design systems” actually are, and why they might matter to all of us, not just the largest organisations. We kick things off by uncovering the surprisingly varied definitions of design systems, including perspectives from the Nielsen Norman Group and Figma. The conversation quickly turns to what design systems look like in real-world settings: are they just libraries of reusable components, or do they go deeper than the visual layer to include things like code, documentation, and accessibility? Paul, David, and Nathan talk through the differences between style guides, design tokens, component libraries, and pattern libraries, and where the lines between them blur. We touch on how design systems operate in organisations of all sizes, from solo freelancers to giant institutions like the UK government, and how the goal of a design system isn’t just making things look good, but improving collaboration, maintaining consistency, and supporting accessibility. If you’ve ever wondered how to get started with a design system, whether to build your own or adapt an off-the-shelf solution, or why some systems succeed while others become overly complex, this episode is for you. We also talk about the long-term benefits and pitfalls: does consistency stifle creativity? How do design systems need to evolve alongside technology? And how do they stay resilient in an ever-changing industry? If you’re curious about design systems—or want to build more efficient, accessible, and lasting websites—this episode is packed with insights, practical tips, and plenty of honest stories about what happens when theory meets practice.

On the podcast today, David and Nathan are back with the second episode in their new series, where they break down the key components that make up a website. Today, they’re talking about website navigation, and asking the surprisingly sticky question: why is it so bloody awful? David has done a deep dive into the ins and outs of navigation, putting together an exhaustive list of all the pieces involved. Nathan admits he used to take a much simpler approach, just add the top-level links and hope Google did the rest, but David’s research proves there’s a lot more going on beneath the surface. They start by exploring the shifting meaning of terms like “menu,” “navigation,” and “nav,” both from a developer and a user’s perspective. Is it a noun? Is it a verb? Is it a technical role? As they discovered, even big names in UX like the Nielsen Norman Group can’t seem to agree. From there, they walk through the many different types of website navigation: main links, hamburger menus, even on desktop, breadcrumbs, dropdowns (on hover or click), mega menus, and more. And it’s not just the styles that are confusing, there’s a tangle of terminology too, with “dropdowns,” “flyouts,” and “pull downs” meaning different things to different people. David and Nathan share their frustrations with modern navigation: hidden menu items, ambiguous links, and the accessibility pitfalls of complicated dropdowns. They talk about why menus can be especially tricky on mobile, and how easy it is for even pros to get lost in their own site’s nav. David explains his approach of keeping things simple, stopping at HTML and CSS wherever possible, and only grudgingly adding JavaScript when absolutely needed. They then explore the design, SEO, and accessibility issues that come with modern navigation patterns: from accidentally hiding important links from both users and Google, to building mega menus that are impossible to navigate by keyboard, to the sheer overwhelm of too many choices. The conversation is packed with real-world frustrations, rants about hover-based menus, and practical tips on creating accessible, user-friendly website navigation. If you’ve ever been baffled by your own website’s menu, or just want to build smarter, simpler navigation that works for everyone, this episode is for you.