Skip to content

Commit ac447c2

Browse files
committed
GITBOOK-360: change request with no subject merged in GitBook
1 parent 8f241c2 commit ac447c2

File tree

1 file changed

+0
-11
lines changed

1 file changed

+0
-11
lines changed

‎misc/testimonials.md‎

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,3 @@
11
# Testimonials
22

3-
{% @vaultrice-voting/vote-block votingId="voting-xyz" title="Sample Voting" description="Choose your preferred option" choices="[
4-
{
5-
"id": "option-a",
6-
"label": "Option A"
7-
},
8-
{
9-
"id": "option-b",
10-
"label": "Option B"
11-
}
12-
]" voteLabel="Vote" enableUserTracking="true" showPercentages="false" showTotalVotes="true" ttl="3600000" %}
13-
143
<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><p><strong>&#x3C;&#x3C;How we translated the Avocode website written in Next.js with the i18next package</strong></p><p><strong>...>></strong></p></td><td></td><td></td><td><a href="https://locize.com/customers.html#avocode">https://locize.com/customers.html#avocode</a></td><td><a href="../.gitbook/assets/avocode.jpg">avocode.jpg</a></td></tr><tr><td><p><strong>&#x3C;&#x3C;...</strong></p><p><strong>Using i18next as our international framework enables us to use the same technology around our whole software stack, regardless the actual backend or framework we use. locize is the icing on the cake – it made translation management unspeakably easier.</strong></p><p><strong>...></strong></p></td><td></td><td></td><td><a href="https://locize.com/customers.html#logiscool">https://locize.com/customers.html#logiscool</a></td><td><a href="../.gitbook/assets/logiscool.jpg">logiscool.jpg</a></td></tr><tr><td><p><strong>&#x3C;&#x3C;...</strong></p><p><strong>We have separated help pages for en, ja, zh, zh-TW. i18next automatically switched the link to appropriated lang help’s page</strong></p><p><strong>....>></strong></p></td><td></td><td></td><td><a href="https://locize.com/customers.html#worldshopping">https://locize.com/customers.html#worldshopping</a></td><td><a href="../.gitbook/assets/worldshopping.jpg">worldshopping.jpg</a></td></tr><tr><td><p><strong>&#x3C;&#x3C;Using locize and its tools (i18next) saves us a LOT of time by not thinking about the texts and focusing on development only.</strong></p><p><strong>...>></strong></p></td><td></td><td></td><td><a href="https://locize.com/customers.html#fideli">https://locize.com/customers.html#fideli</a></td><td><a href="../.gitbook/assets/fideli.jpg">fideli.jpg</a></td></tr><tr><td><p><strong>&#x3C;&#x3C;...</strong></p><p><strong>We used i18next with React and were translating JSON files by hand, which was really cumbersome.</strong></p><p><strong>...>></strong></p></td><td></td><td></td><td><a href="https://locize.com/customers.html#realadvisor">https://locize.com/customers.html#realadvisor</a></td><td><a href="../.gitbook/assets/realadvisor.jpg">realadvisor.jpg</a></td></tr><tr><td><p><strong>&#x3C;&#x3C;...</strong></p><p><strong>Switching to locize was pretty straightforward, thanks to i18next and the possiblity to import JSON files in the admin dashboard.</strong></p><p><strong>...>></strong></p></td><td></td><td></td><td><a href="https://locize.com/customers.html#photogram">https://locize.com/customers.html#photogram</a></td><td><a href="../.gitbook/assets/photogram.jpg">photogram.jpg</a></td></tr><tr><td><p><strong>&#x3C;&#x3C;...</strong></p><p><strong>Support was also very reactive and fixed a bug in under 1 hour after it was reported. I would recommend for use with i18next on a React.js platform.>></strong></p></td><td></td><td></td><td><a href="https://locize.com/customers.html#beelance">https://locize.com/customers.html#beelance</a></td><td><a href="../.gitbook/assets/beelance.jpg">beelance.jpg</a></td></tr><tr><td><p><strong>&#x3C;&#x3C;...</strong></p><p><strong>We use i18next as an internationalization framework. locize being perfectly integrated with the framework become a really good translation management tool for us.</strong></p><p><strong>...>></strong></p></td><td></td><td></td><td><a href="https://locize.com/customers.html#2captcha">https://locize.com/customers.html#2captcha</a></td><td><a href="../.gitbook/assets/2captcha.jpg">2captcha.jpg</a></td></tr><tr><td><p><strong>&#x3C;&#x3C;...</strong></p><p><strong>Using i18next in conjunction with react-i18next (there’s an Angular, Vue and even jQuery support, among others) will help you maintain expressive code that’s i18n ready.</strong></p><p><em><strong>...>></strong></em></p></td><td></td><td></td><td><a href="https://dutzi.party/utilizing-i18next/">https://dutzi.party/utilizing-i18next/</a></td><td><a href="../.gitbook/assets/dutzi.jpg">dutzi.jpg</a></td></tr></tbody></table>

0 commit comments

Comments
 (0)