Make WordPress

The Learn WordPress Learning Pathways help people build their WordPress skills, whether they are getting started as users, developing websites, or exploring web design.

As WordPress continues to evolve, it’s important to make sure our learning materials remain accurate, relevant, and useful for learners. We’d like to invite experienced WordPress users, contributors, developers, designers, educators, and community members to help us review the existing Learning Pathways and identify opportunities for improvement.

What Are We Reviewing?

We’re looking for feedback on the three existing Learning Pathways:

• User: https://learn.wordpress.org/learning-pathway/user/
• Developer: https://learn.wordpress.org/learning-pathway/developer/
• Designer: https://learn.wordpress.org/learning-pathway/designer/

We want to understand which lessons continue to work well, which may need updating, and whether there are gaps in the learning experience.

What Should You Look For?

As you explore the pathways, consider sharing feedback about the following:

• Outdated instructions: Are any steps, screenshots, or explanations no longer accurate?
• WordPress and software versions: Do lessons refer to older versions of WordPress, plugins, themes, or other tools where the content may need updating?
• Tools and workflows: Have the recommended tools, interfaces, or workflows changed?
• Missing information: Are there important concepts or skills that learners need but the lessons don’t currently cover?
• Learning experience: Is the content easy to follow, well structured, and appropriate for its intended audience?
• Opportunities for improvement: Could a lesson benefit from a clearer explanation, a practical exercise, a video, a better example, or a different teaching approach?

You don’t need to review an entire pathway. Feedback on even one lesson can be valuable.

How to Share Your Feedback

When submitting a suggestion, please include as much of the following information as possible:

1. Learning Pathway: User, Developer, or Designer.
2. Lesson title and URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org: Which lesson are you referring to?
3. What needs attention: Describe the outdated information, issue, or missing content.
4. Suggested improvement: What would you change, and why?
5. Supporting references: If available, share relevant documentation, current examples, or other resources that can help verify your suggestion.

Please be as specific as possible. For example, rather than saying that a lesson looks outdated, point out the particular instruction, interface, software version, or workflow that may need to be checked.

What Happens Next?

Our goal is to make this a collaborative and practical review process.

We’ll collect the feedback, group similar suggestions, and prepare a draft of the proposed improvements. Relevant Subject Matter Experts (SMEs) will then be invited to review the recommendations, verify their technical accuracy, and help determine which changes should be prioritized.

Not every suggestion will necessarily require a change. Some lessons may still be accurate and useful, while others may benefit from revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision., additional examples, or updated resources.

Once the recommendations have been reviewed, we can work toward implementing the approved changes and establishing a process for keeping the Learning Pathways relevant over time.

Join Us in Improving Learn WordPress

If you have experience with WordPress, teaching, web development, design, or creating learning resources, we’d love to hear from you.

Your perspective can help us identify issues that might otherwise go unnoticed and make the learning experience better for people discovering and working with WordPress.

Which lessons do you think need attention, and what improvements would you suggest?

Let’s work together to make Learn WordPress an even more useful resource for the community.

This week’s meeting will be held on Tuesday, October 13th, 2026, at 07:00 UTC. The meeting will be held on 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/, in the #training channel. Anyone is welcome to contribute to the meeting by commenting in Slack threads during the meeting and throughout the following days. Meeting notes will be published by the following Tuesday to incorporate these asynchronous conversations as well.

This week’s meeting will be hosted by @devmuhib.

1. Intro/Welcome

• Welcome to all the new teammates who joined the Training Team this week!
• Icebreaker – Who will be joining tomorrow’s Office Hours meeting on Zoom?

2. Contributor Updates

• What have you been working on, and how has it been going?
• Anything you’ve accomplished since the last meeting?
• Do you have any blockers?
• Can other contributors or Training Team members help you in some way?

3. Open Discussions

• If you have topics you’d like discussed in the meeting, please leave them as a comment on this post.
  • Have you heard the exciting announcement about a NEW FLAGSHIP 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.?
    • Just like WordCamp Europe, WordCamp US, and WordCamp Asia, the newest flagship event is WordCamp India 2027!
    • Which city will get the opportunity to host this prestigious event? Share your guesses in the comments!

4. News

1. Meeting Note Takers
   • 27th October: @jenish1234
   • 3rd November: @andrewssanya
   • 10th November: @gohelkunjan
   • 17th November: @harshjadav003
   • 24th November: @upekar99
2. Looking for feedback
   • We are proposing a community-driven review of the Learn WordPress Learning Pathways (User, Developer, and Designer) to identify outdated content and gather improvement suggestions from experienced WordPress users and contributors. Check out this post for details.
   • Looking for feedback on the Spanish translation for “Open Source Principle 0: With many eyes, all bugs are shallow” #3714 and Spanish translation for “What is a plugin?” #3711
   • Team Homepage: @clk87 has shared A block-based prototype for the Training Team homepage to make team pages more engaging and newcomer-friendly. Feedback is welcome via GitHub Issue #3674.
   • Office Hours: The next Office Hours will be held on a weekday, avoiding Monday and Friday. The proposed dates are October 27, 28, or 29, 2026; you will be informed when the date is set and confirmed.
   • Text-to-Speech: The team discussed exploring text-to-speech/read-aloud functionality for course lessons. @softglazee has created prototypes, and the team is encouraged to provide feedback before implementation discussions with MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Team.
   • Training Team Handbook: The handbook is currently being updated, and team members are encouraged to share suggestions, improvements, and ideas in GitHub Issue #3447.
   • Intermediate 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. Developer Course: @mebo has revived the Learning Pathway course and started working on modules and lessons. Team members are invited to review the new content and share feedback, including the “Rendering plugin data” lesson.
3. Looking for volunteers
   • Content Review Volunteers: Volunteers are needed to review and identify content that should be updated or consolidated. Two groups are needed: one for the handbook and one for courses.
   • Lesson Thumbnails: Work has started on creating thumbnails for lessons that need them. Team members are welcome to contribute to the remaining thumbnails through GitHub Issue #3428.
   • Issue Cleanup: The team discussed organising the many open issues into smaller categories and reviewing them systematically.
     • Review Workflow: The proposed process is to review issues one by one, identify outdated or irrelevant items, suggest next steps, and add comments before closing or updating issues.
       • Good First Issues: Contributors can start with issues labeled Good First Issue, especially those related to content feedback, and follow the handbook guide for validating feedback.
       • Issue Categories: The team discussed starting with a specific categoryCategory The ‘category’ taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging., with Bug issues suggested as a priority. Other options include Needs Translation Reviewer, Unlabeled, Awaiting Triage, and Content Feedback.
       • Next Steps: Team members are encouraged to suggest which category should be reviewed first, after which the issues can be divided among contributors.
     • Goal: Work together to clean up and keep the repository organised.
4. Updates from last week’s Triage Squad session
   • No triage squad meetings last week
5. Other announcements and news
   • Office Hours Recap: The September 26, 2026 Office Hours session was successfully hosted, moderated by @vasantrajput, and the recap post has been published. Thanks to @rfluethi for preparing the draft.
   • Monthly Update: The Training Team’s September 2026 monthly update has been published.
   • Community & Slack: The team shared the guide on how to bring your community to Make WordPress Slack.

5. Come and Contribute

• Content ready for review
  • See Guidelines for reviewing content when reviewing content.
    • We have 9 issues ready for review
• Feedback awaiting validation
  • See Validating and Applying Content Feedback for step-by-step guidance on validating feedback.
    • We have 36 issues that require validation
• Topics awaiting vetting
  • See Vetting Topic Ideas for step-by-step guidance on vetting topic ideas.
    • We have 2 issues that require vetting
• Validated feedback awaiting fix
  • Contributors, see Validating and Applying Content Feedback for step-by-step guidance on applying feedback that has been validated.
    • We have 27 issues awaiting a fix

6. Contribution Acknowledgement

• Badges awarded:
  • No badges awarded this week

7. Project updates

• A new version of the 50-hour course, WordPress Credits: Intro to Contribution, has been launched. It is integrated with the new Education Platform, where mentors can track student progress through student report cards.

8. Upcoming Online Workshops

• No workshop scheduled

The Training Team Office Hours session will take place on October 28, 2026, at 15:00 UTC (meeting details).

This Office Hours session has been scheduled on a weekday as a trial. The day and time were finalized through proposals and discussions in the #training channel.

Everyone is welcome to participate by joining the Zoom meeting during the session or by sharing their feedback and suggestions in the following days.

• Date: 28 October, 2026
• Time: 15:00 UTC (local time)
• Platform: Zoom (Zoom Meeting link in 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/ #training channel.)
• Issue: #3730
• Moderator: Sumit Singh (@sumitsingh)
• Note-taker: SAndrew (@andrewssanya)

Meeting Agenda (60 minutes)

15:00–15:05 – Welcome & Onboarding (5 min)

• Post Slack opening tag: <office hour meeting>
• Moderator welcomes participants
• Reminder of the WordPress Community Code of Conduct
• 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) check: any needs we should be aware of?
• Note the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ usernames of everyone present (the note-taker will need them)

15:05–15:10 – Brief Introductions (5 min)

• Each participant briefly introduces themselves: name, location, role in the WordPress ecosystem
• For repeat participants, keep it short; prioritise new faces

15:10–15:20 – Topic Presentation (10 min)

• Topic: WordPress Learn 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/ Issue Triage and Cleanup
  • The WordPress Learn repository currently has many open issues. Rather than reviewing everything at once, we propose dividing issues into smaller categories and reviewing one categoryCategory The ‘category’ taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. during each session.
  • The goal is to make it easier for contributors, including newcomers, to participate while keeping the repository organised and up to date.
  • Suggested workflow:
    1. Select one issue category or label.
    2. Review issues one by one.
    3. Identify outdated, duplicate, or irrelevant issues.
    4. Suggest fixes or next steps.
    5. Add comments before closing or updating issues.
    6. Assign follow-up actions where needed.

15:20–15:40 – Open Discussion (20 min)

• Discussion questions:
  1. Status of the Training Handbook inventory: https://github.com/rfluethi/wpt-office-hours/issues/7
  2. TT-Admins meeting and Triage: clear separation vs. merge: https://github.com/rfluethi/wpt-office-hours/issues/16

15:40–15:50 – Review of Open Action Items (10 min)

• Ask responsible persons for a brief status update on open items from the previous meeting
• If something is blocked or delayed, document it; this is a checkpoint, not a re-discussion

15:50–15:55 – Definition of Next Steps (5 min)

• Summarise the decisions made today
• Confirm each action item: task description, responsible person, and target date

15:55–15:00 – Date, Moderator and Note-Taker for the Next Meeting (5 min)

• Confirm the next meeting date, moderator, note-taker, and backup note-taker with the group
• If the date cannot be set: name one person who sets it and confirms the roles by a deadline
• Thank all participants
• Post Slack closing tag: </office hour meeting>

---

You can see all meetings scheduled on this meeting calendar. If you are new to the Training Team, then come walk through our onboarding program to get to know the team and how we work. And if you have questions, feel free to reach out in the #training Slack channel at any time.

#agenda, #learn-wordpress, #training-team

This meeting followed the meeting agenda in GitHub and P2 Post.
You can see conversations from the meeting in this Slack Log. (If you don’t have a 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/ account, you can set one up.)

Introductions and Welcome

There were 20 attendees: @softglaze, @alkesh7, @rjekic, @sumitsingh, @sumitjavia, @mosescursor, @rfluethi, @makanikaran (async), @gohelkunjan (async), @andrewssanya (async), @lidarroy (async), @nitspatel (async), @vasantrajput (async), @dilip2615 (async), @mohkatz (async), @pravin1996 (async), @sonaliprajapati (async), @harshjadav003 (async), @jenish1234 (async), @ursha (async)

Newcomers: @kulsumsiddique, @quentinldd, @polg87, @meahadi, @rafamarin

Meeting hosted by: @sumitsingh
Note Taker: @softglaze
Note Reviewer: @vasantrajput

Welcome! Please post in the #training channel or reach out to a team member to help you with contributing. Resources to check out our onboarding program and our Guide Program.

News

Meeting Note Takers

Here is our current note taker roster:

• 20th October: @softglaze
• 27th October: @jenish1234
• 3rd November: @andrewssanya
• 10th November: @gohelkunjan
• 17th November: @harshjadav003
• 24th November: @upekar99

It’s recommended to publish meeting notes before the next weekly meeting, so it stays clear which meeting a recap refers to. Note takers who need help with a recap post can DM @vasantrajput, who will guide them and review and publish the post.

Looking for feedback

• Spanish translations: Feedback and reviewers are welcome on #3714 (“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. Principle 0: With many eyes, all bugs are shallow”) and #3711 (“What is a 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.?”).
• Team Homepage: @clk87 has shared a block-based prototype for the Training Team homepage to make team pages more engaging and newcomer-friendly. Feedback is welcome via GitHub Issue #3674.
• Office Hours: The next Office Hours will be held on a weekday, avoiding Monday and Friday. The proposed dates are October 27, 28, or 29, 2026.
  • @sumitsingh asked whether the date could be finalised during the meeting. No date was agreed in the meeting.
  • In the thread afterwards, the team settled on Wednesday, October 28, 2026, at 15:00 UTC on Zoom, moderated by @sumitsingh. The topic will be shared beforehand. @vasantrajput suggested publishing the agenda post on the Training blog two to three days ahead to bring in more contributors.
• Text-to-Speech: The team discussed exploring text-to-speech/read-aloud functionality for course lessons. @softglaze has created prototypes, and the team is encouraged to provide feedback before implementation discussions with the MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Team.
  • @softglaze noted that the prototypes are linked in #3649, and that feedback from @rjekic points toward the free, built-in browser voice, which needs no paid service and no hosted audio files.
  • Two questions were raised for the team: what should be in place before the proposal goes to the Meta Team, and who to contact there. These are still open, and replies are welcome on the issue.
• Training Team Handbook: The handbook is being updated; suggestions are welcome in GitHub Issue #3447.
• Intermediate Plugin Developer Course: @mebo has revived the Learning Pathway course and started working on modules and lessons. Team members are invited to review the new content, including the “Rendering plugin data” lesson.

Looking for volunteers

• Content Review Volunteers: Volunteers are needed to review and identify content that should be updated or consolidated, in two groups: one for the handbook and one for courses.
  • @softglaze volunteered for the handbook group.
• Office Hours Note Taker: A note taker is needed for the October 28 Office Hours session (15:00 UTC, Zoom). Please reply in the #training channel if you can help. Previous recaps for reference: September 26.
• Lesson Thumbnails: Work has started on creating thumbnails for lessons that need them. Contributions to the remaining thumbnails are welcome through GitHub Issue #3428.
• Issue Cleanup: The team is organising the many open issues into smaller categories and reviewing them systematically. The proposed process is to review issues one by one, identify outdated or irrelevant items, suggest next steps, and comment before closing or updating. Contributors can start with Good First Issues, especially those related to content feedback, following the handbook guide for validating feedback.
  • Bug issues were suggested as the first priority. Other options are Needs Translation Reviewer, Unlabeled, Awaiting Triage and Content Feedback. No categoryCategory The ‘category’ taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. was chosen during the meeting; team members are encouraged to suggest which one to review first, after which the issues will be divided among contributors.
  • On Needs Translation Reviewer, @softglaze shared that 24 of these issues are Urdu lesson translations. The translations are complete, 20 lessons have been reviewed, and two more volunteers have offered to review the remaining 4.
  • @sumitsingh confirmed that once the review is done, author access will be provided so the lessons can be published. Whether to remove the label from already reviewed issues is still open.

Update for last week’s triage squad

No triage squad meetings last week.

Other news

• Office Hours Recap: The September 26, 2026 Office Hours session was hosted and moderated by @vasantrajput, and the recap post has been published. Thanks to @rfluethi for preparing the draft.
• Monthly Update: The Training Team’s September 2026 monthly update has been published.
• Community & Slack: The team shared the guide on how to bring your community to Make WordPress Slack.

Come and Contribute

This week’s contribution focus area

1. Content ready for review: 9 issues. See Guidelines for reviewing content.
2. Feedback awaiting validation: 36 issues. See Validating and Applying Content Feedback.
3. Topics awaiting vetting: 2 issues. See Vetting Topic Ideas.
4. Validated feedback awaiting fix: 27 issues.

Contribution Acknowledgement

Badges Awarded

• No badges awarded this week.

Give Props

• @softglaze, @mosescursor and @andrewssanya gave props to @sumitsingh for hosting the meeting.

Project updates

• A new version of the 50-hour course, WordPress Credits: Intro to Contribution, has been launched. It is integrated with the new Education Platform, where mentors can track student progress through student report cards.

Upcoming Online Workshops

• No online workshop is scheduled for this week.

Contributor Updates

• @softglaze:
  • Text-to-Speech #3649: replied on the issue; the prototypes are ready for feedback.
  • Urdu course: translations are complete and 20 of 24 lessons have been reviewed (thanks to @sanayasir). The last 4 are being shared between @had1a and @pomypk.
  • Leading the WordPress 7.2 Test Scrub on Thursday 22 October at 15:00 UTC in #core-test. Everyone is welcome.

Open Discussions

• No topics were raised during the meeting. Async discussion is welcome in the meeting thread.

The meeting closed with Dussehra wishes from @sumitsingh. Thanks to everyone who participated in the sync and async, and to those who will contribute in future sessions.

---

You can see all meetings scheduled on this meeting calendar. If you are new to the Training Team, then come walk through our onboarding program to get to know the team and how we work. And if you have questions, feel free to reach out in the #training Slack channel at any time.

#meeting-recap, #training, #training-team

Your journey with WordPress doesn’t end with the workshop—it starts here!

We’re excited to welcome all the students participating in WordPress Campus Connect at Presidency University, Dhaka! This workshop is an opportunity to explore WordPress, learn new skills, connect with the community, and discover new possibilities in web development, design, and the open-source ecosystem.

But learning is only one part of the experience. We also want you to stay connected with the people you meet and become part of the wider WordPress community.

To help us build that connection, we have two small requests for every participant.

1. Share Your Workshop Experience in the Comments 💬

Did you participate in our WordPress Campus Connect workshop? Let us know in the comments!

Please introduce yourself briefly and share that you attended the event. You can also tell us what you learned, which session you enjoyed most, or what you’re excited to explore next.

Here’s a sample comment you can follow:

Hi, I’m [Your Name], a student at [Your University]. I participated in WordPress Campus Connect at Presidency University and look forward to learning more about WordPress and connecting with the community!

A few tips for writing your comment:

• Use your real name so other participants can recognize you.
• Mention your university, department, or area of study.
• Share one thing you learned or found interesting during the workshop.
• Tell us what you want to learn or build with WordPress.
• Keep it friendly, authentic, and simple. You don’t need to write a long paragraph!

Feel free to write in your own style. The sample is just a guide.

2. Introduce Yourself in the WordPress Campus Connect 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/ Community 💬

The workshop is just the beginning. We want you to stay connected, ask questions, share your progress, learn from others, and discover opportunities within the WordPress community.

That’s why we encourage every participant to join our WordPress Campus Connect Slack community and post a short introduction.

If you’re new to Slack, don’t worry! It’s a communication platform where community members can connect, exchange ideas, ask for help, and collaborate on projects.

Here’s a sample Slack introduction:

Hi everyone! 👋 I’m [Your Name] from [Your University], and I’m excited to be part of the WordPress Campus Connect community. Looking forward to learning and connecting with you all!

Tips for a great Slack introduction

• Be yourself: You don’t need to be an expert or an experienced developer to introduce yourself.
• Share your interests: Whether you enjoy coding, design, writing, marketing, or simply exploring technology, there’s a place for you.
• Mention your goals: Tell the community what you want to learn, create, or contribute.
• Ask questions: If you’re a beginner, let people know what you’re curious about.

If you don’t have experience with WordPress yet, that’s completely fine. Curiosity and a willingness to learn are great places to start.

3. Claim Your Free Domain & Hosting from WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/!

As a WordPress Campus Connect workshop participant, you can claim a free domain and hosting through the WordPress.com Education offer. You’ll use this website to build your workshop project or portfolio.

How to Claim Your Website

1. Visit WordPress.com and create a free account.
2. Visit the Education Offer Page to start setting up your website.
3. Choose your preferred domain name and complete the registration.

⚠️ Important Instructions

• Only .blog or .art domains are available for free under this offer.
• The domain will be free for one year.
• Choose your domain name carefully, as it will represent your project or portfolio website.
• Save your website address (URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org) after registration. You’ll need it when submitting your project or portfolio.
• Do not create multiple accounts or attempt to register multiple domains, as this may result in your account being blocked.
• If you encounter any issues, avoid repeated attempts. Contact the WordPress.com Support Team and follow their instructions.

Example domain: cozysummerbloom.blog

🚀 Once you’ve claimed your website, you’ll be ready to start building! During the workshop, we’ll use WordPress to create our own websites.

4. Contribute to Bengali WordPress Translations

Want to contribute to WordPress beyond building websites? Help make WordPress plugins more accessible to Bengali-speaking users by translating a few strings into Bengali!

You can start with these two popular plugins:

• 🛒 WooCommerce: https://translate.wordpress.org/projects/wp-plugins/woocommerce/stable/bn/default/?filters%5Bstatus%5D=untranslated
• 🔍 Rank Math SEO: https://translate.wordpress.org/projects/wp-plugins/seo-by-rank-math/stable/bn/default/?filters%5Bstatus%5D=untranslated

How to get started:

1. Open either translation link.
2. Log in with your WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ account.
3. Choose an untranslated string and suggest a Bengali translation.
4. Submit your translation for review.

A few tips:

• Use clear, natural Bengali that people can easily understand.
• Read the original text carefully and understand its context before translating.
• Keep technical terms in English when that makes the meaning clearer.
• Review your translation for spelling and accuracy.

You don’t need to translate hundreds of strings. Start with just a few and make a meaningful contribution! Your suggestions may need approval from the translation reviewers before they become available to users.

Let’s make WordPress more accessible to Bengali-speaking users, one translation at a time! 🇧🇩💙

5. Why Does This Matter? 🌍

WordPress is more than a platform for building websites. It’s part of a global open-source community where people learn together, share knowledge, collaborate, and contribute in different ways.

By sharing your experience and introducing yourself, you’re taking your first steps toward building meaningful connections beyond your university campus.

You never know where a conversation might lead—a new skill, a collaboration, a personal project, a mentorship opportunity, or even your future career.

Let’s Keep the Connection Going!

Here’s what we’d love every participant to do:

✅ Comment on this post and share that you participated in WordPress Campus Connect at Presidency University, Dhaka.

✅ Join the WordPress Campus Connect Slack community using the invitation shared by the organizers.

✅ Post your introduction in Slack so other community members can get to know you.

✅ Engage with others by welcoming fellow students, asking questions, and sharing what you learn.

Whether you’re taking your first steps into technology or already building websites, you belong here.

Thank you for being part of WordPress Campus Connect Dhaka. Let’s keep learning, building, and growing together!

Welcome to the community. Let’s build something amazing! 💙