Category: Lightning talk

The topic highlights the failure aspects of business at project, operation , product decisions and not part of a single department.

The viewers will have a insight about how fixing the structural cracks help reducing churn rates and why business goals should be aligned across departments

WordPress sites sit on years of blog content that gets read once and never seen again. Meanwhile, short-form video is where most discovery actually happens now. The topic will describe a chain of AI agents that read a blog post, decide whether it’s worth turning into video, write a script, generate narration and visuals, and publish the short video.

In B2B commerce and procurement, the biggest flaw in modern customer experience (CX) is operational friction. When an enterprise buyer reaches out about catalog availability, volume pricing, or order status, they aren’t looking for a passive conversation, a help article, or a support ticket. They are trying to complete a transaction. Most conversational tools fail because they act as information dead-ends rather than systems designed to actually solve the buyer’s problem.

WordPress is no longer limited to traditional themes, templates, and plugins. Today, it can sit at the centre of modern digital platforms powering structured content, APIs, headless experiences, custom frontends, and increasingly, AI-assisted workflows.

In this session, I’ll share how we can rethink WordPress for the modern web: using it as a flexible content platform, integrating it with modern frontend frameworks, designing better editorial experiences, and making architectural choices that scale beyond a conventional website.

We’ll also explore where AI fits into this evolution, from assisting developers with code and debugging to improving content workflows, search, automation, and new user experiences.

Rather than asking whether AI will replace WordPress or traditional development, the session looks at a more useful question: how can WordPress, open-source technologies, modern web architecture, and AI work together to build better digital experiences?

The session is intended for developers, agencies, and technology leaders who want to understand how WordPress can continue to evolve without losing the openness and flexibility that made it successful.

• Structuring content so machines can better understand its meaning and context
• Using schema, entities, headings and internal linking more strategically
• Applying AI without turning the editorial process into generic AI-generated content

We’ve spent years talking about what WordPress does. But what if we talked about who WordPress is?

This session takes a playful detour into the brand behind the software — exploring what people associate with WordPress, how they would describe it as a person, what personality it seems to have, and the strange little contradictions that emerge when you start asking those questions.

It’s part research, part experiment, and part “why have we never thought about WordPress this way before?”

Come with an open mind. Leave with a completely different mental picture of WordPress.

At our company, agentic development is no longer just an experiment. For a few of our projects, we have shifted a large part of the development workflow to cloud-based AI agents that can work continuously.

In this talk, I’ll first give you a look at what that workflow actually looks like, including the tools we use, how agents fit into our development process, and how we make sure the code they produce still meets our quality standards.

But once you see the amount of AI involved, an obvious question comes up: how do we sustain the cost of running agents at this scale?

That is where the real topic of the talk begins.

I’ll share how we built an in-house system that optimizes our AI usage by deterministically routing different requests to the most appropriate models, instead of sending everything to the most powerful and expensive model available. I’ll also show how this approach has significantly reduced our AI usage and cost, backed by the analytics we collected along the way.

The goal of this talk is to share a practical approach to making large-scale agentic development economically sustainable, without simply compromising on the quality of the models you use.

The way people discover information online is changing rapidly. Search is moving beyond traditional keyword-based results toward AI-powered experiences that understand context, intent, and relationships between information. For WordPress publishers, this shift creates an opportunity to rethink how content is planned, structured, published, and optimized.

Drawing on 10+ years of experience in content, SEO, digital marketing, and WordPress, I’ll share practical insights, proven strategies, and actionable content hacks for making WordPress content more discoverable across both traditional search and emerging AI-driven search experiences. The session will explore search intent, topical authority, content architecture, internal linking, structured data, content optimization, and responsible AI-assisted publishing workflows. Attendees will leave with a practical framework they can apply to create more useful, connected, and discoverable content that delivers value beyond rankings.

AI and humans have more in common than we think: both need clear guardrails to consistently produce the right outcomes.

AI doesn’t always follow the exact same pattern every time, and that’s where guardrails become essential. When designed thoughtfully, they can help us harness AI while creating seamless editorial experiences that stay aligned with your brand guidelines, much like the systems and processes we use to guide human teams.

Join me as I explore how to build AI-powered editorial experiences that follow your brand guidelines with minimal deviation, while making AI practical and reliable useful for WordPress teams.

AI in WordPress talks usually stop at “look what Copilot/Cursor can do for your code.” This one goes further. Over the last two years, I’ve watched AI change how a WordPress engineering team actually runs — first as a developer using AI-assisted coding, then overseeing a QA team using AI for test generation and bug triage, and now as an Engineering Director using it for planning, process improvement, and code review.

In 15 minutes, I’ll share what genuinely changed (and what didn’t) at each of those levels — where the productivity gains are real, where they’re overstated, and what it means for how you staff and structure a WordPress team going forward. You’ll leave with three concrete things to evaluate before you scale AI adoption in your own team or agency, not another tool demo.