Platform Guides

Supported Platforms

Setup snippets for every platform Pronto supports. The six site-builder platforms are unique to Pronto — you won't find WordPress, Webflow, Shopify, Squarespace, Framer, or Wix support anywhere else.

WordPress

now supported

Pronto scans your theme and plugin PHP files for translatable strings wrapped in WordPress i18n functions (__(), _e(), _n(), esc_html__(), etc.) and generates/updates your .pot and .po files.

Initialize

$ pronto init --framework wordpress --locales-dir ./languages

pronto.config.json

{ "framework": "wordpress", "localesDir": "./languages", "textDomain": "my-theme", "sourceLocale": "en", "targetLocales": ["es_ES", "ja"] }

Pronto writes .po files compatible with Loco Translate and standard WordPress plugins. No extra plugins needed on the WordPress side.

Webflow

now supported

Pronto connects to your Webflow site via the Webflow Data API. It extracts all static text from CMS collections and page content, translates only what changed, and pushes updates back.

Initialize

$ pronto init --framework webflow --webflow-token $WEBFLOW_TOKEN

pronto.config.json

{ "framework": "webflow", "siteId": "your-site-id", "sourceLocale": "en", "targetLocales": ["es", "ja"] }

Requires a Webflow API token with CMS read/write permissions. Content staging is supported — Pronto can push to a staging locale before publishing.

Shopify

now supported

Pronto works with Shopify's Translate & Adapt app and the Translations API. It scans your theme's locale JSON files and syncs product / collection metafields to target languages.

Initialize

$ pronto init --framework shopify --shop my-store.myshopify.com

pronto.config.json

{ "framework": "shopify", "shop": "my-store.myshopify.com", "localesDir": "./locales", "sourceLocale": "en", "targetLocales": ["es", "ja"] }

Squarespace

now supported

Pronto integrates with Squarespace's Developer Platform. Export your site strings, translate with Pronto, and import the updated locale files back via the Squarespace CLI.

Initialize

$ pronto init --framework squarespace

pronto.config.json

{ "framework": "squarespace", "localesDir": "./static/locales", "sourceLocale": "en", "targetLocales": ["es", "ja"] }

Framer

now supported

Pronto syncs with Framer Sites via the Framer Localization API. It reads your source locale, translates changed strings, and commits updated locale files back to your Framer project.

Initialize

$ pronto init --framework framer --framer-token $FRAMER_TOKEN

pronto.config.json

{ "framework": "framer", "projectId": "your-project-id", "sourceLocale": "en", "targetLocales": ["es", "ja"] }

Wix

now supported

Pronto integrates with Wix Multilingual via the Wix Studio API. It reads page content, CMS collections, and app texts, then pushes translated content to each target locale.

Initialize

$ pronto init --framework wix --wix-api-key $WIX_API_KEY

pronto.config.json

{ "framework": "wix", "siteId": "your-site-id", "sourceLocale": "en", "targetLocales": ["es", "ja"] }

React / Next.js

Pronto works with any react-i18next, next-intl, or i18next setup. It scans your source files for t() calls and updates your locale JSON files.

Initialize

$ pronto init --framework nextjs

pronto.config.json

{ "framework": "nextjs", "localesDir": "./public/locales", "sourceLocale": "en", "targetLocales": ["es", "ja"] }

Vue / Nuxt

Works with vue-i18n. Pronto scans for $t() calls in .vue files and updates your messages JSON files.

Initialize

$ pronto init --framework vue

pronto.config.json

{ "framework": "vue", "localesDir": "./src/locales", "sourceLocale": "en", "targetLocales": ["es", "ja"] }

Flutter

Works with Flutter's arb-based localization. Pronto scans .arb files and generates updated arb files for each target locale.

Initialize

$ pronto init --framework flutter

pronto.config.json

{ "framework": "flutter", "localesDir": "./lib/l10n", "sourceLocale": "en", "targetLocales": ["es", "ja"] }