Episode
Ep17. Should we be offering clients a CMS?
- Podcast
- No Script Show
- Published
- Mar 19, 2025
- Duration seconds
- 3364
- Processing state
not_requested
Actions
POST https://stenobird.com/v1/public/podcasts/no-script-show-6719676/episodes/ep17-should-we-be-offering-clients-a-cms/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/no-script-show-6719676/ep17-should-we-be-offering-clients-a-cms.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
On the podcast today, we have Paul Lacey, an experienced UK designer deeply entrenched in the world of WordPress. With years of experience working with agencies and clients, Paul will help us tackle the question: should we be offering clients a Content Management System (CMS)? Paul brings a wealth of knowledge, having transitioned from a small agency owner to a freelance web consultant. He focuses on building websites and consulting, steering clear of marketing but fully embracing the technological side. We delve into the challenges and decisions surrounding the use of CMSs like WordPress, how they have influenced the design process over the years, and whether or not they are necessary for clients. We discuss the practical aspects of offering a CMS: managing content, user permissions, and dealing with the demands and constraints that often come with these systems. Paul shares his experiences navigating these waters, working with both direct clients and agencies, and his thoughts on where the industry might be headed. If you've ever grappled with the decision of whether to integrate a CMS into your workflow or simply offer bespoke solutions to your clients, this episode will provide you insight and perspective on the evolving landscape of web design and development.