WordPress Day for AI

Organizing a WordPress Day for AI

A WordPress Day for AI is a local WordPress community event focused on the practical, ethical, and technical intersections between WordPress and artificial intelligence.

These events help attendees understand how AI is changing WordPress workflows, content creation, site management, development, accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), business operations, and contributions to the WordPress project.

A WordPress Day for AI can be organized as a half-day event with talks and networking, or as a full-day event with multiple tracks, workshops, demos, and contributor activities.

Overview

Artificial intelligence is becoming part of how many people build, manage, and publish with WordPress. A WordPress Day for AI gives local communities a space to explore these changes together in a practical, responsible, and community-focused way.

The event should help attendees:

Learn how AI can support real WordPress workflows.
Understand current and emerging AI-related WordPress tools.
Discuss the risks, limitations, and responsibilities of using AI.
Connect with other WordPress users, developers, agencies, creators, and business owners.
Discover ways to contribute to AI-related work in the WordPress project.

A WordPress Day for AI should not be a vendor sales event or a general artificial intelligence conference with little connection to WordPress. The focus should remain on WordPress, open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL., practical learning, and community discussion.

Goals of this event

The goals of a WordPress Day for AI may include:

Introducing attendees to practical AI use cases in WordPress.
Helping site owners, agencies, freelancers, and developers evaluate AI tools responsibly.
Showing examples of AI-assisted WordPress workflows.
Discussing privacy, security, accessibility, copyright, licensing, and quality concerns.
Encouraging human review and transparency when AI tools are used.
Creating space for questions, feedback, and community discussion.
Connecting attendees with the WordPress AI Team and other Make WordPress contribution opportunities.
Supporting local community growth around an emerging topic.

Who this event is for

A WordPress Day for AI can serve a mixed audience, including:

WordPress users who are curious about AI.
Site builders and site administrators.
Content creators, editors, and marketers.
Freelancers and agencies.
Business owners and entrepreneurs.
PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. and theme developers.
WordPress contributors.
Students and educators.
Designers, accessibility specialists, and user experience professionals.

If the event has a broad audience, consider separating beginner-friendly and technical content into different sessions or tracks.

Recommended format

A WordPress Day for AI can work well as either a half-day or full-day event.

Half-day format

A half-day format is a good option for communities organizing this event type for the first time.

A typical half-day event may include:

3-4 talks
A coffee break
Networking time
A short panel or open discussion
Optional demos

This format works well for an audience of around 50-100 people.

Full-day format

A full-day format allows more room for different audiences and deeper learning.

A full-day event may include:

Opening session
Two content tracks
Talks
Workshops
Demos
Panel discussion
Contributor or feedback session
Networking

For larger events, consider two tracks.

AI for WordPress users and businesses

This track can focus on practical, non-technical uses of AI, such as:

Content planning and editing
Customer experience
Workflow automation
Productivity
Site management
Marketing and operations
Evaluating AI tools for client work
Responsible AI policies for agencies and teams

AI for WordPress developers and builders

This track can focus on technical topics, such as:

AI-assisted development workflows
AI APIs and integrations
WordPress AI projects
MCP and AI agents
Automation
Plugin development
Testing and debugging
Local AI tools
Security and permission models

Example schedules

Example half-day schedule

09:00 – Registration and welcome

09:15 – Opening remarks: Why AI matters for WordPress

09:30 – Talk 1: Practical AI workflows for WordPress users

10:15 – Talk 2: AI, content, and editorial quality

11:00 – Coffee break and networking

11:45 – Talk 3: AI for agencies, freelancers, or business owners

12:30 – Talk 4: WordPress, AI, and the open web

13:15 – Panel or open discussion: risks, opportunities, and questions

13:45 – Closing and next steps

14:00 – Event ends

Example full-day schedule

09:00 – Registration and networking

09:30 – Welcome and Code of ConductCode of Conduct “A code of conduct is a set of rules outlining the norms, rules, and responsibilities or proper practices of an individual party.” – Wikipedia reminder

09:45 – Opening session: WordPress and AI in practice

10:30 – Break

10:45 – Track A: AI for business workflows

10:45 – Track B: AI for WordPress development

11:30 – Track A: Content, productivity, and customer experience

11:30 – Track B: AI-assisted development, APIs, and automation

12:15 – Lunch

13:15 – Workshop: Testing AI tools safely with WordPress

14:30 – Break

14:45 – Panel: Privacy, security, accessibility, licensing, and trust

15:45 – Contributor session, feedback session, or open discussion

16:45 – Community announcements and next steps

17:00 – Networking

18:00 – Event ends

Organizer team

A WordPress Day for AI should have a clear organizing team. Suggested roles include:

Lead organizer: Coordinates the event and keeps planning on track.
Program lead: Defines the event theme, reviews speaker applications, and builds the schedule.
Speaker wranglerWrangler Someone, usually a person part of event organizing team, who looks after certain things like budget or sponsors.: Communicates with speakers and helps them prepare.
Sponsor lead: Coordinates sponsorships according to WordPress event guidelines.
Venue and logistics lead: Manages venue, food, accessibility, Wi-Fi, signage, and day-of logistics.
Communications lead: Handles website updates, attendee emails, social media, and local promotion.
Volunteer coordinator: Recruits and supports volunteers.
Accessibility lead: Reviews venue, communication, and event accessibility needs.
Technical/demo lead: Helps speakers and workshop facilitators prepare safe, reliable demos.
Contributor or discussion lead: If the event includes contributor activities, prepares tasks and helps attendees get started.

For events with technical workshops or contributor sessions, make sure there are enough experienced facilitators to support attendees.

Planning timeline

12-16 weeks before the event

Confirm the event purpose, audience, and format.
Form the organizing team.
Choose whether the event will be half-day or full-day.
Identify possible venues.
Draft a budget.
Decide whether the event will have one track or multiple tracks.
Contact the Community Team if approval or support is needed.
Begin outreach to potential speakers, facilitators, and sponsors.

8-12 weeks before the event

Confirm venue and date.
Launch the event website or event listing.
Publish the call for speakers, if applicable.
Publish the call for sponsors, if applicable.
Begin promotion through local WordPress channels.
Draft the schedule structure.
Identify accessibility needs and venue requirements.
Plan any workshops or demos.

4-8 weeks before the event

Confirm speakers and sessions.
Review sessions for balance, relevance, and community alignment.
Confirm sponsors.
Open attendee registration.
Publish the schedule, or at least a preliminary schedule with confirmed speakers and sessions. (Publishing the schedule as early as possible can help generate excitement and encourage registrations).
Recruit volunteers.
Prepare signage, badges, and attendee communication.
Review demo requirements with speakers.
Create a backup plan for internet or APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. issues.

1-4 weeks before the event

Send speaker and attendee information.
Confirm food, coffee, accessibility, and venue arrangements.
Test AV and internet access.
Confirm volunteer assignments.
Prepare Code of Conduct reminders.
Prepare feedback forms.
Prepare links to WordPress AI resources and contribution opportunities.

After the event

Thank attendees, speakers, volunteers, sponsors, and the venue.
Share slides, recordings, photos, and resources if available.
Send a feedback survey.
Publish a recap.
Submit recordings to WordPress.tv if applicable.
Invite attendees to join the local WordPress meetupMeetup Meetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook. and Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.
Review what worked and what should improve next time.

Venue and logistics

A WordPress Day for AI may include talks, live demos, workshops, and networking. Choose a venue that supports the format.

Consider:

Reliable Wi-Fi.
AV equipment for presentations and demos.
Enough power outlets for workshops.
Accessible entrance, seating, restrooms, and stage area.
Space for registration.
Space for coffee breaks and networking.
Quiet areas for conversation or support.
Livestreaming or recording needs.
Clear signage.
Food and beverage options.
Public transport and parking.

Because AI demos may depend on external services, organizers should plan for unreliable internet or API failures. Encourage speakers to prepare screenshots, recordings, local environments, or fallback demos.

Content and speaker guidance

A WordPress Day for AI should focus on useful, practical, and responsible AI topics connected to WordPress.

Good session topics include:

Practical AI workflows in WordPress.
AI-assisted content creation and editing.
AI and accessibility.
AI and SEO workflows.
AI for agencies and freelancers.
AI and customer support.
AI-assisted development.
WordPress AI projects and contribution opportunities.
MCP, APIs, automation, and AI agents.
Privacy, security, and data handling.
Copyright, licensing, and attribution.
Evaluating AI tools critically.
Building human review into AI-assisted workflows.

Avoid sessions that:

Are primarily sales pitches.
Promote one commercial product without broader educational value.
Present AI output as always accurate or trustworthy.
Encourage attendees to enter private, client, confidential, or sensitive data into AI tools.
Ignore copyright, licensing, privacy, accessibility, or security concerns.
Require attendees to create paid accounts with third-party AI services.
Are not clearly connected to WordPress.

Speakers should be encouraged to explain:

What problem their AI workflow solves.
What WordPress tools or processes are involved.
What data is being shared with AI systems.
What human review is required.
What risks or limitations attendees should understand.
How attendees can try the workflow safely after the event.

Responsible AI and demo safety

AI-related sessions should be practical and transparent. Organizers should remind speakers and facilitators that:

AI can assist, but humans remain responsible for the final result.
AI-generated content, code, or recommendations should be reviewed before use.
Speakers should disclose meaningful AI assistance where relevant.
Attendees should not be asked to share private, client, personal, or confidential information with AI tools.
Demos should use test content, demo sites, or sample data.
Production websites should not be used for risky live demos.
Speakers should have a fallback plan if an AI service, API key, or internet connection fails.
Read-only demos are safer than demos that modify content, settings, users, or code.
If an AI tool makes changes to a site, the speaker should explain permissions, review steps, and rollback options.

For contribution-related content, organizers may link to the AI Guidelines:
https://make.wordpress.org/ai/handbook/ai-guidelines/

For talks about the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. AI projects, organizers may share the Guide to talking at WordPress meetupsMeetup Meetup groups are locally-organized groups that get together for face-to-face events on a regular basis (commonly once a month). Learn more about Meetups in our Meetup Organizer Handbook. and WordCamps about the Core AI projects:
https://make.wordpress.org/ai/handbook/resources-and-links/guide-to-talking-at-wordpress-meetups-and-wordcamps-about-the-core-ai-projects/

Budget considerations

Budgets will vary depending on the event format, location, attendee count, venue costs, food, AV needs, and other factors. Organizers are encouraged to keep the event as lean and practical as possible, since each additional budget item may require more planning, fundraising, and administration.

Common costs may include:

Venue rental.
Coffee, snacks, or lunch.
Accessibility services.
Recording or livestreaming.
Signage and printing.
Badges or lanyards.
Contributor or workshop materials.

A half-day event may be easier to organize with a smaller budget, especially if the venue is donated and only coffee or light refreshments are provided.

A full-day event with multiple tracks may require a larger budget for venue, food, AV, and volunteer support.

Inclusion, safety, and accessibility

All WordPress community events must follow the WordPress event Code of Conduct.

Organizers should:

Link to the Code of Conduct on the event website.
Mention the Code of Conduct during opening remarks.
Identify who attendees can contact if they need help.
Choose an accessible venue.
Ask attendees about accessibility needs during registration.
Provide clear directions and venue information.
Avoid jargon where possible.
Include beginner-friendly explanations.
Make space for attendees who are skeptical, cautious, or new to AI.
Encourage respectful discussion of risks and concerns.
Avoid treating AI adoption as mandatory or inevitable for every user.

AI can be a sensitive topic. Some attendees may be concerned about privacy, labor, copyright, environmental impact, accessibility, or misinformation. A good WordPress Day for AI should create room for thoughtful discussion, not only enthusiasm.

Promotion

Promotion should clearly explain who the event is for and what attendees will learn.

Possible promotional channels include:

Local WordPress meetup group.
Local WordPress community website.
WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They’re one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. or WordPress Events site.
Make WordPress Slack.
Local tech, business, university, and open-source communities.
Social media.
Sponsor and speaker networks.
Local newsletters.

Promotional copy should emphasize:

WordPress relevance.
Practical learning.
Responsible AI use.
Community discussion.
Networking.
Whether the event is beginner-friendly, technical, or both.
Whether attendees need to bring a laptop.
Whether any AI accounts or tools are required.

If workshops use specific tools, tell attendees in advance and provide free or open alternatives where possible.

Day-of checklist

Before attendees arrive

Confirm venue access.
Test Wi-Fi and AV.
Check microphones, projector, and recording setup.
Prepare registration area.
Display signage.
Brief volunteers.
Confirm speaker arrival times.
Confirm food and coffee timing.
Prepare Code of Conduct contact information.
Prepare backup demos or offline materials.

During the event

Welcome attendees.
Mention the Code of Conduct.
Explain the event schedule.
Thank sponsors, volunteers, speakers, and the venue.
Remind speakers of time limits.
Encourage questions and discussion.
Make announcements about local WordPress community activities.
Share links to relevant WordPress AI resources.
Collect feedback.

After the event

Thank everyone involved.
Share resources and recordings.
Send a feedback form.
Publish a recap.
Invite attendees to future local WordPress events.
Invite interested attendees to join Make WordPress Slack and the relevant contributor channels.

After the event

Post-event follow-up helps turn a one-day event into lasting community activity.

Consider sharing:

Slides.
Recordings.
Photos.
Demo links.
Resource lists.
Speaker contact links.
Contributor links.
A recap post.
Feedback survey results or key takeaways.

If sessions were recorded, submit suitable recordings to WordPress.tv.

Invite attendees to continue the conversation through:

The local WordPress meetup.
Future AI-focused meetups.
Make WordPress Slack.
The Make WordPress AI blog.
The WordPress AI Handbook.
Relevant GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ repositories and contribution channels.