WordPress Sydney

Most WordPress sites do not fall apart because of one dramatic failure. They slowly drift out of shape through normal use, ordinary edits, unclear permissions, and well-meaning changes made by people trying to get their work done.

That is the awkward reality of building websites for real organisations. The launch version may be clean, tested, and carefully structured, but six months later the site has met editors, managers, contractors, plugin updates, urgent content changes, and someone who “just needed to quickly fix the homepage”.

This session looks at the common places WordPress sites get damaged after handover, including content editing, user permissions, plugin decisions, SEO changes, forms, layout control, and content governance.

The bigger question is not how to stop clients touching their own websites. It is about building WordPress systems with enough guardrails so that normal human behaviour does not quietly turn into technical debt, broken layouts, lost leads, or avoidable support problems.

Note: this is a rescheduled event.

You'll walk away with:
✅ A clearer way to spot the predictable break points in client-managed WordPress sites
✅ A practical mental model for deciding where clients need freedom, and where they need guardrails
✅ Better judgement around permissions, editing access, plugin decisions, and post-handover risk
✅ A simple way to think about WordPress sites as ongoing systems, not finished launch artefacts

🎯 Who's It For?
In-person event

WordPress enthusiasts, freelancers, digital managers, and site owners who already work with WordPress and want to move beyond surface-level tutorials.
This session assumes basic WordPress familiarity. It’s not designed for complete beginners.

Format

• In-person Event
• Arrive 6:30 for pre-networking
• Talk starts at 6:45.

The most expensive bug in a WordPress project often isn't hidden in the code — it's hidden in communication. When business requirements, SEO strategies, UX decisions, and developer specifications are scattered across emails, Slack conversations, Google Docs, and meeting notes, projects slow down, scope creeps in, and teams waste time rebuilding features that could have been avoided.

That challenge becomes even more common as projects grow. Developers spend valuable time searching for information, clients receive inconsistent answers, and important decisions become difficult to track because no single source contains the full picture.

In this practical session, Georgia Tan, Co-Founder of Switch Key Digital, demonstrates how to build a centralised "Project Brain" using Google's NotebookLM. By bringing together client goals, UX wireframes, SEO documentation, and project requirements into a single AI-powered knowledge base, teams can quickly find answers, stay aligned, and make better decisions throughout the entire project lifecycle.

You'll walk away with:
✅ A practical framework for building a centralised AI-powered project knowledge base using NotebookLM
✅ Faster ways to find answers across project documentation without digging through emails and chat history
✅ Techniques for turning SEO audits and business requirements into clear technical specifications for developers
✅ Better strategies for keeping clients, strategists, and development teams aligned while reducing scope creep

🎯 Who's It For?
WordPress developers, digital agencies, project managers, SEO specialists, and anyone involved in planning or delivering WordPress projects who wants to improve collaboration and documentation.
This session is ideal for teams managing multiple stakeholders, client requirements, and technical documentation.

Format

• In-person Event
• Arrive 6:30 for pre-networking
• Talk starts at 6:45.