Products
Personal products
Intl multilingual studio
I developed a studio for editing source text and translations side by side. Work on the app is paused, while its editor remains in use as a separate package.
- Period
- 2026.05
- Organization
- Firstage
- Role
- Design and implementation (solo)
- Key features
- Source text and translations can be compared and edited paragraph by paragraph. ROUND also uses the editor for multilingual event guides.
- Work and results
- ROUND reuses IntlEditor as is to edit event guides in several languages
- The editor lives on as a package in the editors family
- Documents, language versions, and paragraph pairings are defined in a format separate from the interface
- Tech stack
- Next.js
- React
- Lexical
- TypeScript
Context
Firstage serves Korean, English, and Japanese, and its content has to be managed in several languages as well. In May 2026 I started an internal studio meant to handle importing source text, translating, reviewing, and publishing in one place.
Decisions and implementation
- I built the editor as the intl package of the editors family (IntlEditor) rather than inside the app. It places the source and the translation side by side for review, and documents, per-language variants, and block mappings are defined in a React-free model.
- The app handles only the studio frame, creating a document on first input, auto-save, and the language switcher.
Current state
Because the editor lives in its own package, ROUND, a sports event service in the same monorepo, uses IntlEditor as is to edit event guides in several languages. I paused the studio app itself in May 2026, before connecting translation to it.