WordPress is powered by a global community of developers, designers, translators, educators, organisers, writers, testers, moderators, accessibility specialists, and many other contributors.
Every Make WordPress team is doing valuable work. These teams are supported by volunteers and sponsored contributors who share their time, knowledge, and experience to improve WordPress for millions of users.
This article is not intended to criticise any contributor team, team representative, moderator, or individual volunteer.
It is a constructive discussion about how WordPress contributor teams can improve communication, contributor management, transparency, and efficiency. It also explores how responsible use of artificial intelligence could help teams complete repetitive work faster while keeping important decisions in human hands.
From my personal point of view, the Support Team deserves particular attention because it communicates directly with WordPress users, plugin developers, theme developers, agencies, freelancers, hosting providers, and new contributors.
For many people, the official support forums are their first direct interaction with the wider WordPress community.
That first experience matters.
A positive experience can encourage someone to continue using WordPress, recommend it to others, contribute to the project, or become an active member of the community.
A negative experience, especially one involving unclear moderation or an unexplained account restriction, can cause someone to leave the community completely.
Every WordPress Contributor Team Is Doing Important Work
The WordPress project includes many contributor teams, each responsible for a different part of the ecosystem.
The current Make WordPress contributor teams include:
- Core
- Design
- Mobile
- Accessibility
- Polyglots
- Support
- Documentation
- Themes
- Plugins
- Community
- Meta
- Training
- Test
- WordPress TV
- Marketing
- WP-CLI
- Hosting
- Tide
- Openverse
- Photos
- Core Performance
- Playground
- Core AI
- Core Program
Each team contributes in a different way.
Some teams develop the WordPress software. Some improve accessibility, performance, design, and mobile experiences. Others review plugins and themes, organise events, create learning resources, translate WordPress, test new features, maintain WordPress.org platforms, or help users through the support forums.
All of these teams are doing meaningful work.
Improvement does not mean that a team is failing. It means the community is continuing to learn, grow, and look for better ways to support contributors and users.
Why the Support Team Deserves Special Attention
The Support Team is one of the most visible WordPress contributor teams because it interacts directly with users.
Support contributors help people:
- Troubleshoot WordPress problems
- Understand WordPress features
- Resolve plugin and theme conflicts
- Find relevant documentation
- Identify possible bugs
- Report technical issues
- Improve website security
- Learn safe WordPress practices
- Understand forum guidelines
The team also handles difficult responsibilities, including:
- Spam
- Fake reviews
- Commercial promotion
- Personal attacks
- Harassment
- Unsafe code
- Requests for private website access
- Duplicate accounts
- Privacy concerns
- Repeated guideline violations
- Attempts to manipulate ratings
- Security-related discussions
This work is not easy.
Support contributors and moderators often manage frustrated users, incomplete information, technical misunderstandings, language barriers, commercial disputes, and emotional discussions.
Their work should be respected.
At the same time, because the Support Team manages users and contributors directly, its communication and moderation processes need to be especially clear, fair, consistent, and understandable.
My Main Concern: Restrictions Without Clear Communication
One area I believe could be improved is communication when a user or contributor is warned, moderated, restricted, or blocked.
In serious cases, moderators may need to act immediately.
This may be necessary when someone is involved in:
- Harassment
- Threats
- Fraud
- Credential theft
- Repeated spam
- Privacy violations
- Multiple-account abuse
- Attempts to bypass an existing restriction
- Deliberate disruption of the community
Immediate action is understandable in situations where users or the community may be at risk.
However, for less serious or correctable issues, contributors should normally receive a clear explanation.
A useful moderation notification should explain:
- What action was taken
- What activity caused the concern
- Which forum guideline applies
- Whether the restriction is temporary or permanent
- What the contributor needs to change
- Whether a previous warning was issued
- Whether the decision can be reviewed
- How can the contributor return to positive participation
Without clear communication, the affected contributor may not understand what happened.
Even when the moderation decision is correct, a lack of explanation can make the process feel unfair, confusing, or discouraging.
Clear communication would reduce repeated mistakes, public complaints, unnecessary arguments, and misunderstandings between contributors and moderators.
Allow Genuine Contributors to Improve
Not every guideline violation should immediately result in a permanent restriction.
There is an important difference between:
- A first-time mistake
- A misunderstanding of forum rules
- An accidental promotional link
- An emotional response during a difficult discussion
- Repeated commercial promotion
- Deliberate spam
- Harassment
- Threats
- Fraud
- Attempts to avoid previous moderation
These situations should not always receive the same response.
A genuine contributor may accidentally include a company link, ask someone to contact them privately, share untested code, or misunderstand a support forum guideline.
If the issue is not severe and the contributor has a positive contribution history, a warning and clear guidance may be more constructive than immediate removal.
This does not mean regular contributors should receive special privileges.
Everyone should follow the same community guidelines.
However, moderation decisions can still consider:
- The seriousness of the issue
- Whether harm was caused
- Whether the action was deliberate
- The contributor’s previous behaviour
- Their contribution history
- Whether they received earlier guidance
- Whether they accepted responsibility
- Whether they corrected the issue
- Whether they are willing to follow the guidelines
A fair system should protect the community while also allowing well-intentioned people to learn from mistakes.
A Clearer Warning and Moderation Process
A more structured process could make moderation easier to understand.
Educational Notice
For a small or likely accidental issue, the contributor could receive a respectful explanation.
For example:
Your recent reply included a link to a commercial service. Promotional replies are not permitted in the support forums. You are welcome to continue contributing, but please keep future replies focused on public and non-promotional solutions.
This approach explains the problem without immediately discouraging the contributor.
Formal Warning
If the same behaviour continues, the contributor could receive a formal warning.
The warning should clearly explain:
- Which behaviour continued
- Which guideline applies
- What must change
- What may happen if the issue continues
Temporary Post Moderation
The contributor’s future replies could be held for review for a limited period.
They should be told:
- Why is this happening
- How long will it continue
- What behaviour is expected
- How normal participation can be restored
Temporary Suspension
Repeated or more serious behaviour may result in a temporary suspension.
The notification should explain:
- The reason
- The duration
- The conditions for returning
- How to request clarification
Permanent Restriction
Permanent blocking may be appropriate for severe or repeated behaviour involving harassment, threats, fraud, credential theft, repeated spam, serious privacy violations, multiple-account abuse, or continued violations after previous warnings.
This kind of structured process would not weaken moderation.
It would make moderation clearer, more consistent, and easier to justify.
Warnings Can Make Moderation Stronger
Giving someone a warning does not mean ignoring the rules.
A warning creates a clear record and allows the contributor to change.
It can make moderation stronger because:
- Expectations become clear
- The contributor understands what must stop
- Future decisions are easier to explain
- Minor issues may be resolved quickly
- Genuine contributors may remain active
- Repeat offenders become easier to identify
- Moderators can show that a fair process was followed
A good moderation process should be firm when necessary, but educational whenever possible.
A Private Review Process
Important moderation decisions should have a simple private review process.
The review should not become a public argument or place individual moderators under pressure.
A contributor requesting a review could provide:
- Their WordPress.org username
- Links to the relevant topics
- Their understanding of the issue
- Any missing context
- Confirmation that they reviewed the guideline
- The steps they will take to avoid repeating the problem
Where practical, another experienced moderator could review the case.
Possible outcomes could include:
- The original decision remains unchanged
- The restriction is shortened
- The account is moved to temporary moderation
- A warning replaces a permanent restriction
- More information is requested
- The decision is corrected
A review process does not remove moderator authority.
It improves confidence in the moderation system.
Contribution History Should Provide Context
A contributor’s history should not make them exempt from the rules.
However, it may provide useful context.
Consider two examples.
The first user creates a new account, repeatedly posts promotional messages, ignores guidance, and uses multiple accounts.
The second contributor has helped users for several years, has no prior warnings, and has made one incorrect or promotional reply.
The same guideline may apply to both users, but the most suitable response may differ.
The first case may require stronger action.
The second case may be resolved through guidance and a warning.
Considering contribution history does not mean creating a privileged group. It means choosing a proportionate response based on context, behaviour, and risk.
Better Notifications on WordPress.org
Some communication problems may be caused by limitations in the WordPress.org platform rather than by individual moderators.
The Meta Team could help the Support Team by improving account and moderation notifications.
A contributor dashboard could display:
- Current account status
- Posts being held for review
- Removed or edited replies
- Warning information
- Relevant forum guidelines
- Restriction duration
- Required actions
- Review request status
- Previous moderation notices
Email notifications could also be sent when significant account actions occur.
A contributor should not discover that their account has been restricted only after repeatedly trying to publish a reply.
Clear and Respectful Moderation Messages
Moderation messages should be direct, specific, and respectful.
Vague messages such as “Your behaviour was inappropriate” do not always help someone understand what needs to change.
A clearer message would be:
Several of your recent replies included links to your paid service. The support forums cannot be used to generate commercial leads. Please stop adding promotional links. You may continue contributing by providing public, non-promotional troubleshooting guidance.
This kind of message explains:
- What happened
- Why it is a problem
- What must stop
- How the person can continue contributing
Clear communication helps both the contributor and the moderator.
A Second Review Before Permanent Blocking
Except in urgent or obvious abuse cases, permanent restrictions could be reviewed by at least two experienced moderators.
This could reduce the risk of:
- Incomplete context
- Personal bias
- Cultural misunderstanding
- Emotional decisions
- Inconsistent enforcement
- Conflicts of interest
An immediate temporary restriction could still be applied when necessary.
The second review would simply help determine whether permanent removal is the most appropriate long-term action.
Disagreement Should Not Automatically Be Treated as Misconduct
Contributors should be able to respectfully disagree with a moderator or community process.
They should be able to:
- Ask for clarification
- Request a guideline reference
- Explain missing context
- Suggest a different interpretation
- Request a second review
- Propose improvements to the process
Disagreement should not automatically be treated as disrespect.
At the same time, disagreement must not become harassment, threats, repeated disruption, personal attacks, or attempts to bypass restrictions.
A healthy community should allow respectful questions while responding firmly to abusive behaviour.
Improve Support Contributor Onboarding
The Support Team welcomes contributors with different levels of experience.
However, new contributors may not fully understand forum expectations.
They may accidentally:
- Promote their business
- Add unnecessary links
- Ask users to contact them privately
- Request administrator access
- Post duplicate replies
- Share untested code
- Give unsafe advice
- Reply outside their expertise
- Use AI-generated answers without checking them
- Criticise another plugin or developer unfairly
A short onboarding process could prevent many of these problems.
It could include:
- Reading the support forum guidelines
- Reviewing examples of helpful replies
- Understanding promotional-content restrictions
- Learning what information should remain private
- Learning how to report unsafe content
- Reviewing examples of moderated replies
- Receiving feedback on the first few contributions
This does not need to become a large new training programme.
A short, practical onboarding checklist could already make a meaningful difference.
Support Contributors Need Mentorship
New support contributors may hesitate to ask questions publicly.
A lightweight mentorship process could help them understand:
- How to write useful replies
- How to avoid promotional language
- When to escalate an issue
- How to handle frustrated users
- How to share code safely
- When not to reply
- How to report a security issue
- How moderation works
Experienced support contributors could review a few early replies and provide private guidance.
This would improve reply quality and reduce future moderation issues.
Recognise Positive Support Contributions
Contributor management should not focus only on mistakes.
The Support Team should also recognise people who consistently provide helpful, safe, accurate, and respectful assistance.
Recognition could be given to contributors who:
- Answer questions patiently
- Welcome new users
- Reproduce difficult issues
- Report unsafe advice
- Improve documentation
- Help without self-promotion
- Mentor other contributors
- Participate regularly
- Share accurate technical solutions
Recognition could include contributor badges, appreciation posts, contributor spotlights, public thank-you messages, or opportunities to mentor others.
When positive work is recognised, contributors are more likely to remain active.
Protect Moderators as Well as Contributors
Any improvement process must also protect moderators.
Moderators may experience:
- Personal attacks
- Threats
- Repeated complaints
- Public accusations
- Private contact attempts
- Pressure from companies
- Attempts to expose their identity
- Burnout from difficult cases
Transparency does not mean publishing private moderator information or requiring moderators to defend every decision publicly.
A better system should support:
- Private moderation
- Team-based decisions
- Internal escalation
- Anonymous moderator communication where appropriate
- Strong anti-harassment protections
- Time away from difficult cases
- Shared responsibility
Contributor fairness and moderator safety should not be treated as opposing goals.
Both are necessary for a healthy community.
Avoid Publicly Shaming Contributors
When someone makes a correctable mistake, the detailed disciplinary discussion should normally happen privately.
Public shaming can:
- Escalate conflict
- Create defensive reactions
- Damage reputations
- Discourage future participation
- Encourage others to join the argument
- Turn a small issue into a major dispute
A public topic may still need to be edited, closed, or removed.
However, communication with the contributor should remain respectful and focused on improving behaviour.
Responsible Use of AI in Support Forums
Artificial intelligence can help contributors work faster, but it also creates new risks.
An AI-generated answer may include:
- Incorrect WordPress functions
- Invented hooks or filters
- Unsafe code
- Incorrect database queries
- Generic responses
- Misunderstanding of the original question
- Confident but unverified advice
- Security or privacy problems
Support contributors should remain responsible for every answer they publish, even when AI helped create it.
AI-assisted replies should be:
- Checked carefully
- Edited for the specific question
- Tested where possible
- Reviewed for security and privacy
- Corrected quickly if inaccurate
AI should support human knowledge, not replace judgement or responsibility.
How AI Can Help WordPress Contributor Teams Work Faster
AI should not replace contributors.
It can be used as an assistant to reduce repetitive work, organise information, discover patterns, and make useful resources easier to find.
Support Team
AI could help:
- Categorise support topics
- Identify duplicate questions
- Recommend relevant handbook pages
- Highlight potentially unsafe replies
- Summarise long support threads
- Prepare draft responses for human review
- Detect repeated spam patterns
AI should not automatically block users or make final moderation decisions.
Documentation Team
AI could help identify:
- Outdated pages
- Broken links
- Duplicated content
- Missing examples
- Documentation that no longer matches the latest WordPress version
- Common support questions that need better documentation
Human contributors should review and approve all updates.
Training Team
The Training Team is already doing valuable work through Learn WordPress, learning pathways, courses, tutorials, workshops, and contributor resources.
AI could assist with:
- Content discovery
- Draft summaries
- Quiz suggestions
- Transcripts
- Subtitles
- Translation support
- Identifying learning materials that need updates
- Organising feedback from learners
As a Training Team Representative, I believe the focus should remain on supporting existing contributors and improving current workflows rather than creating unnecessary additional systems.
AI can help contributors work more efficiently, but accuracy, accessibility, educational quality, and human review must remain central.
Polyglots Team
AI could help:
- Suggest initial translations
- Identify untranslated strings
- Highlight inconsistent terminology
- Find similar approved translations
- Detect possible spelling or formatting issues
Locale editors should continue making final translation decisions.
Core and Test Teams
AI could assist with:
- Ticket categorisation
- Bug reproduction steps
- Test-case generation
- Code review suggestions
- Finding related historical tickets
- Summarising long technical discussions
Final technical decisions should remain with experienced contributors.
Plugins and Themes Teams
AI could help:
- Improve initial automated checks
- Group common submission problems
- Generate clearer explanations
- Detect repeated code patterns
- Suggest relevant handbook guidance
- Reduce repetitive review work
AI should not automatically reject a plugin or theme without human review.
Community Team
AI could assist with:
- Event summaries
- Organiser documentation
- Accessibility checklists
- Meeting notes
- Scheduling assistance
- Analysis of anonymous community feedback
Sensitive contributor, organiser, or community decisions should always remain human-led.
Meta Team
AI-powered search could make handbooks, meeting notes, contributor documentation, and historical discussions easier to find.
This could help contributors discover answers without repeatedly asking the same questions.
Accessibility Team
AI could help identify possible accessibility problems, but automated suggestions should never replace testing by accessibility specialists and people who use assistive technologies.
WordPress TV and Photos Teams
AI could help with:
- Video transcripts
- Caption suggestions
- Content categorisation
- Tagging
- Duplicate detection
- Search improvements
- Basic quality checks
Final review decisions should remain with contributors.
Collaboration Between Support, Documentation, and Training
Support, Documentation, and Training naturally complement one another.
Support contributors see the questions users ask repeatedly.
The Documentation Team can improve written guidance for those recurring issues.
The Training Team can create structured learning resources when a topic requires a deeper explanation.
A practical workflow could be:
- The Support Team identifies a frequently reported problem.
- The Documentation Team checks whether existing guidance is missing or outdated.
- The Training Team determines whether the topic needs a tutorial, lesson, course, or learning resource.
- Support contributors share the improved resource with users.
AI could help identify repeated topics and organise the information, while contributors decide what content should be created or updated.
This would improve collaboration without adding unnecessary complexity.
Better Use of AI Across All Teams
The purpose of AI should be to help teams work faster and more consistently.
It could reduce repetitive tasks such as:
- Summarising meetings
- Organising feedback
- Finding duplicate issues
- Suggesting documentation
- Categorising tickets
- Identifying outdated content
- Preparing first drafts
- Creating transcripts
- Improving search
- Highlighting possible risks
However, AI should not make final decisions about:
- Blocking contributors
- Removing community members
- Approving or rejecting plugins
- Selecting team leadership
- Resolving sensitive disputes
- Publishing unverified technical guidance
- Making accessibility decisions without human review
AI should assist the community, not control it.
Improvement Does Not Mean Failure
All WordPress contributor teams are doing meaningful work.
Many contributors are volunteers or sponsored contributors managing multiple responsibilities.
They should be supported, not blamed.
Suggesting improvements does not mean that a team is failing.
It means the project is continuing to evolve.
As WordPress grows, contributor teams need better communication, clearer workflows, improved tools, stronger recognition, and responsible use of new technology.
The goal should be to make contribution:
- Easier
- Faster
- More transparent
- More welcoming
- More sustainable
- More consistent
Final Thoughts
Every Make WordPress team contributes something important to the project.
The Core Team develops WordPress.
The Design Team improves the user experience.
The Accessibility Team helps make WordPress usable by everyone.
The Polyglots Team makes WordPress available in many languages.
The Documentation and Training teams help people learn.
The Plugins and Themes teams support the extension ecosystem.
The Community Team connects people through events and local communities.
The Meta Team maintains the platforms used by contributors.
The Test and Performance teams improve quality and reliability.
The newer Playground and Core AI teams explore future possibilities.
However, the Support Team has a particularly important responsibility because it directly represents WordPress to users and new contributors.
From my point of view, the most useful improvements would include:
- Clear moderation notifications
- Specific explanations of relevant guidelines
- Warnings for correctable first-time mistakes
- Opportunities for genuine contributors to improve
- Temporary restrictions before permanent action where appropriate
- Consideration of contribution history
- A private review process
- A second review before permanent restrictions
- Better WordPress.org notifications
- Recognition of positive contributions
- Strong protection for moderators
- Clear guidance for AI-assisted support replies
- Better collaboration with Documentation, Meta, Test, and Training
Rules are necessary to protect the WordPress support forums.
Without moderation, the forums could quickly become filled with spam, promotion, unsafe advice, and personal conflict.
However, strong moderation should not only remove harmful behaviour.
It should also help genuine contributors understand expectations, correct mistakes, and continue contributing positively.
AI can help WordPress teams reduce repetitive work, discover useful information, update resources faster, and improve collaboration.
But human contributors should always remain responsible for important decisions.
WordPress does not need AI to replace its community.
It needs AI to help its community work more effectively, fairly, and efficiently.
