Recently, we've received many requests from our users to simplify the update of translations on production, and now we have an answer. Say Hi to Tolgee Content Delivery, a fast and reliable way to keep your translations independent of your code! Also introducing Webhooks for more automation options.
After a little over 2 years, we decided to freshen up the Tolgee brand, including our logo, website and platform's user interface. We value your suggestions and want to provide the best experience for our users. So, we rolled up our sleeves and gave Tolgee a little refresh to not feel so old-school.
Before I started to work on Tolgee I was used to working with Jira. But I didn't like it much, so I chose YouTrack for project monitoring that time. Now it seems better to move the project management to GitHub, since it's more transparent for developers. Also, there is a kanban board feature on GitHub, so we can move the issues as we were used to in YouTrack, but it's also visible to everyone.
In Q4 of 2021, we planned to finish features like translation memory, automated/machine translating, glossaries or paywall for Tolgee cloud. However, we spent a lot of time on upgrading a website and improving JS integrations. Sadly, we haven't finished any of the features, we wanted to finish before the end of the year. So we have to reflect it in our roadmap. We decided to reschedule everything and target more on the segment of developers than translators. Ladies and gentlemen, we are introducing improved roadmap! 🎉
The i18next library is one of the most popular choices for formatting translations in React applications. We decided, that we want to improve the experience by offering an easy integration with Tolgee. Localization is now uniquely accessible as your translations can be managed through opensource platform, without wasting precious Dev time.
When I started to develop Tolgee for my master thesis about 2 years ago, one of my goals was to provide a localization tool also for developers who would like to use it locally on their machine.
Things were different those days. Tolgee was named Polygloat and the tool was intended to be simplest as possible. So I wanted to keep the tool small, and I didn't want to make users to run separate database server for it. But I also wanted to run the app in cloud, where Postgres is considered "more production ready" choice.
After three weeks of hard work, we finally created, documented and released an integration for Svelte.
I learned a lot about Svelte while creating it, and I have to say, that I love Svelte!
Get started on Tolgee for Svelte!