Contributing to WordPress without knowing “how to code”
summary
Panel argues that non-coders drive WordPress via concrete tasks: translations, testing, documentation, admin work and bug-scrubs, plus meetup and contributor-day organizing. Examples include a tri-lingual site built with Full Site Editor for a WorldCamp that succeeds in practice, weekly Japanese translation sprints (weekly translation sessions Fridays 22:00 JST), and a long-running polyglot network across 800 local Meetup groups. Practical routes: Make.WordPress.org, Slack channels, Learn.WordPress.org, and funding/mentorship options including a proposed 5% time pledge for sustained contributors.
AI-written summary · about
chapters (14)
- 0:00Introduction and panel setup
- 1:11Panelist introductions
- 3:27Why contribute to WordPress
- 9:13Challenges and skills in contributing
- 15:03Overcoming intimidation for non-coders
- 21:20Non-coding contribution opportunities
- 26:45Advice for new contributors
- 27:50Supporting contributors financially
- 30:41Audience Q&A begins
- 31:03Collecting improvement ideas
- 33:11Biggest wishes for WordPress
- 36:03Keeping contributors engaged
- 39:58Barriers to continuous contribution
- 40:40Simplifying onboarding process
