Neutrope Translate Ease

TranslateEase helps WordPress site owners create and manage English translations without turning the whole site into a complex multilingual system. It is designed for small sites that want to translate a limited number of Japanese pages or posts into English, review the translation, and publish only when ready. Main features

• Create paired English translations for pages and posts.
• Manage original and English content from a dedicated Content Translations screen.
• Search original and English content by title or slug, and start translating from post and page lists.
• Edit translations in a side-by-side Translation Workspace.
• Use manual translation without any external API key.
• Optionally create English draft translations with DeepL API.
• Keep automatic translation output as draft until reviewed.
• Show a JP / EN language switcher on paired published content.
• Output hreflang alternates for paired published content.
• Preserve Gutenberg block structure during automatic translation.
• Preserve list structure and shortcode-only blocks such as form embeds.

DeepL API and external service use TranslateEase can be used without DeepL by manually editing English translations. If you choose DeepL as the translation provider and enter a DeepL API key, TranslateEase sends the selected source title, content, and excerpt to the DeepL API only when an authorized administrator clicks an automatic translation action in the WordPress admin area. TranslateEase does not send visitor data to DeepL. Automatic translation is not triggered by front-end visitors. DeepL API service information:

• Service: DeepL API
• API endpoint used for Free keys: https://api-free.deepl.com/v2/translate
• API endpoint used for Pro keys: https://api.deepl.com/v2/translate
• DeepL Privacy Policy: https://www.deepl.com/privacy
• DeepL Terms: https://www.deepl.com/pro-license

You are responsible for your own DeepL account, API key, and usage limits.

0.8.2

• Renamed the public plugin listing to Neutrope Translate Ease for WordPress.org review.
• Updated the plugin slug, text domain, and package root to neutrope-translate-ease.
• Replaced inline script output with WordPress enqueue and inline script APIs.
• Re-audited nonce and permission checks for admin actions.

0.8.1

• Updated WordPress.org submission metadata.
• Updated Tested up to value.
• Adjusted the public plugin title to align the intended translate-ease slug and text domain.

0.8.0

• Add title and slug search to the Content Translations screen.
• Show the post type name and slug for each item on the Content Translations screen.
• Add Create, Continue, and Edit English version row actions to post and page lists for original content.
• Add a workspace note reminding editors that form field shortcodes are managed by the form plugin.

0.7.1

• Prepare WordPress.org packaging and address Plugin Check findings.
• Update request handling in the Translation Workspace.
• Prefix uninstall variables.
• Update Tested up to header.

0.7.0

• Preserve shortcode-only Gutenberg blocks during DeepL translation to protect form embeds and similar shortcodes.

0.6.1

• Preserve list wrapper tags during DeepL translation so list items remain inside ul and ol elements.

0.6.0

• Protect Gutenberg block comments during DeepL translation so block structure is preserved.
• Translate content text segments while keeping wp:block markers unchanged.

0.5.1

• Decode DeepL HTML entities before saving translated title, content, and excerpt so the workspace stays readable.

0.5.0

• Add a safer workspace automatic translation handler with draft-only output.
• Return DeepL API errors to the workspace as admin notices instead of stopping on an error page.
• Add workspace guidance explaining that original title, content, and excerpt are sent to DeepL when auto-translation is used.

0.4.2

• Add contextual guidance, front-end links, and input placeholders to the Translation Workspace.

0.4.1

• Avoid front-end slug conflicts while English post translations are still drafts.

0.4.0

• Add a side-by-side Translation Workspace for posts and pages.
• Route Content Translations actions to the workspace.
• Support manual English draft editing, draft save, publish, and DeepL full auto-translate from the workspace.

0.3.8

• Add no-cost/manual setup guidance and switcher style previews.

0.3.7

• Add provider setup links to the automatic translation wizard.

0.3.6

• Add a beginner-friendly automatic translation setup wizard for DeepL.

0.3.5

• Add one-click create-and-translate actions to the Content Translations dashboard.

0.3.4

• Localize split metabox labels for Japanese admin users.

0.3.3

• Localize Content Translations and post editor metabox labels for Japanese admin users.

0.3.2

• Localize Settings body text and field labels for Japanese admin users.

0.3.1

• Localize remaining Settings section headings for Japanese admin users.

0.3.0

• Add live DeepL translation for titles, content, and excerpts.
• Apply the selected translation publishing mode after automatic translation.
• Keep Google provider reserved for a later version.

0.2.4

• Add a Content Translations dashboard for pages and posts.
• Show original content and English status side by side.
• Replace the old page-only translation menu label with a content-focused view.

0.2.3

• Hide translation entries from normal post and page lists by default.
• Add show and hide translation list links.
• Replace unavailable automatic translation actions with guidance when no provider is configured.

0.2.2

• Add translation publishing mode setting.

0.2.1

• Copy source content into English drafts.

0.2.0

• Add standard post support.

0.1.0

• Initial MVP skeleton.