locize documentation
Help CenterBlogSign inlocize.com
Search…
⌃K
Links
Introduction
Using locize
What's inside?
The different views
Checks/Issues
Using locize as a translator
Integration
Getting started
Instrumenting your code
API
Webhook
Slack
Microsoft Teams
GitHub Repository Dispatch Event
CLI
GitHub Action
I18n Formats
File Formats
Guides / Tips & Tricks
Find unused translations
How to search
Going to production
Keeping track of new translations
Working with translators
Migrating an i18next project
Migrating from ...
More
InContext Editor
Migrating from the old InContext editor
Figma Plugin
Versioning
Namespaces
Notifications
Multi-Tenant
Caching
Backend Fallback
Latency Optimization – Tips for Optimal Performance
2-factor authentication
Convince Your Boss Letter
General questions
Powered By GitBook

InContext Editor

Context matters

Often doing correct translations needs more information by providing more context information. The best context is always the place where the content is shown - your website.
So we decided to bring the locize project closer to your website / application with our InContext view:
Make sure you add the locizify or the locize script to your website, then enter the url.
Find more details on this page.
Previous
Migrating from Transifex to locize
Next
Migrating from the old InContext editor
Last modified 8mo ago
Copy link