What is internationalization?!? Internationalization is the designing of a product in such a way that it will meet the needs of users in many countries or can be easily adapted to do so. Internationa
Efficient localization need not to be expensive, disorganized, and time-consuming for development and localization teams. We designed locize with this core ideas in mind, and a popular software review
So you want people from all around the world to use and understand your software... ...but how to achieve that? Which format should I use?Think about the workflow of exporting strings of the soft
Very often, when you're engrossed in the everyday work, you do not realize how easily your localization process could be improved. For this reason, it is important to me to show you the following
slides Why we choose serverless? When we started with locize we did not know how fast it would scale… serverless means we didn’t need to make that choice. The serverless architecture scales with our
We use the unpkg CDNIn the past we deployed the locizify script to our own CDN space. While this was ok migrating over to https://unpkg.com allows us to provide you an improved usage. In the past your
Learn from our experience we made during using the locize service on our own new webapplication. In an early stage of drafting out our plan to completely rewrite our locize webclient we decided to us
Past timesIn the past most organizations that have to write some software planned, developed and released their product in one-year or even multiple-year cycles. =>Typical waterfall process. Every
When we started work on locize.com our localization as a service platform we basically had in mind to solve the translation process for developers using our i18n framework i18next.com. Translation M
After relaunching our website with new templates for our documentation, post pages and adding a new landing page, we decided to have at least the landing page translated. As we use hexo to generate ou
No Servers?We believe that the best DevOps is NoOps. Nothing against DevOps or DevOps people. On the contrary, but we think we could do differently! Instead of spending time on setting up virtual mach
Back in 2011All started back in 2011 when we were in search for a internationalization library that meets our demand - allowing to run both on serverside node.js and on our clientside singlepage appli