Translation Toolkit
A personal translation bottleneck became a WordPress plugin.
- My role
- Idea, plugin development & personal workflow
- Delivery context
- Recently released
- Tools
- WordPress · WPML · Elementor · ACF · MyMemory · Chrome On-device
The need
My previous team received around 15–25 bilingual website projects a month. Preparing both language versions took time, especially on larger websites. After moving to freelance work, I needed a practical way to handle translations without a separate content team.
My contribution
I originated and built Translation Toolkit for my own work, then released it as a WordPress plugin. It works within the WPML workflow to automate translation of supported website content and help review and save translations.
Tools & decisions
WPML provides the multilingual website foundation. MyMemory and Chrome On-device are the translation engines currently supported. The goal was to offer a free-provider route alongside WPML rather than rely only on its paid automatic translation credits. WPML is required; provider availability and translation quality vary.
Scope & current outcome
The workflow covers supported posts, pages, Elementor content, taxonomies, strings, and ACF fields. Each content type needs appropriate handling within the existing multilingual structure. The plugin is newly released, so there is not enough data to claim measured time savings or adoption. The team’s monthly project volume describes the original problem, not plugin usage.
Let’s make your next website work.
Have a design, a business idea, or a website that needs help? Let’s talk.