News

Let’s meet up at WordCamp Asia 2023!

Sawasdee!

We are geared up for Asia’s first-ever flagship WordCamp happening on 17-19 February, in Bangkok, Thailand. We have a bunch of rtCampers attending this time around. If you spot Rahul Bansal, Vivek Jain, Nitun Lanjewar, Prasad Nevase, Joel Lobo, Maitreyie Chavan, or Rahi Prajapati, know that they’re always up for a conversation 🤝

Those of you attending the event, do drop by our booth to converse around anything WordPress. Also, this is a great chance to explore work opportunities at rtCamp, as we’re actively hiring for multiple roles!

As a part of the exciting lineup, rtCampers Prasad Nevase and Rahi Prajapati will be speaking on the 18th. 

Prasad’s session on ‘Using WordPress.org APIs for community’ is lined up at 4:30 pm (9:30 am GMT) in Track 1. He elaborates on how we utilize the WordPess.org APIs to help you effortlessly compare across plugins with our WP Plugin Compare tool

Throwing light on the importance of ‘Getting your designer ready for Gutenberg’, Rahi is set to speak at 1:30 pm (6:30 am GMT) in Track 2. There’s an inevitable need for designers to be well-informed about Gutenberg constructs. The talk delivers on building a synergy between design and development for a smooth shift to the era of block editing.

If you want to follow along WCAsia remotely, check out the livestream schedule charted out in your local timezone. The official Twitter and YouTube handles are quite informative & fun to check out as well 👀 

We’re grateful to have contributed to the coming together of the community through WCAsia! And are thrilled to discover the possibilities this action-packed weekend holds 🙌 


Links: Accessibility at WordCamp Asia | WordCamp Asia Twitter

Discuss your project
with our experts

No obligation. Limited slots.

Contact Form Business Enquiry

"*" indicates required fields

Please attach any RFP, project specification, or document that you would like to share.
Drop files here or
Max. file size: 5 GB.
    This field is for validation purposes and should be left unchanged.