No Script Show

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.