Make docs neutral and clean from "ads" about react-i18next-gitbook HOT 7 CLOSED

Can understand this request - but you might also understand that we do no other advertising for locize.

We did i18next 10 years and asked for nothing. Nowadays i18next is one of most used i18n lib in javascript / even most downloads for react i18n nowadays.

A lot of large companies use it but getting sponsorship out of those is close to impossible - so if you need financial support you're basically doomed in OSS -> either the project is crazy popular or you will burn out doing it for free (and believe me - there are not only nice people using your work).

I can understand advertising our own product can look unfair or unrelated -> but without it chances would be we would have to close i18next down

from react-i18next-gitbook.

Yeah, that same OSS sad story. I can relate.

But what about advertising the plugin in unrelated places? Does it earn the team some money as well, or just more public? It's really confusing because, for a newcomer, you're not sure if it's unrelated and unclear, of if it's really a different topic.

Also, I think my main concern here is that the docs feel biased as a documentation source. You're not to be blamed by ads, but these do not look like ads. It seems like you're really trying to push people into the service, instead of suggesting them to know it and hire because they got interested in the product. Making it clear it's an ad (with a separate section, a box, a small disclaimer) for a related service goes a long way in that sense, instead of intermixing real documentation with advertised services.

Lastly, maybe having a list of other services that integrate with i18next (with commission?) could help with the "unfair look" of having a related company behind the library. I can help bootstrap that page, if you want.

from react-i18next-gitbook.

I mean........... Even code samples have Locize ads. For a newcomer to the i18n field, it may seem like the only way to do it is using Locize and this foreign territory is dominated by JSON files and Locize. This paints a completely wrong picture, which goes beyond fairness or relatedness... There are so many ""organic"" mentions spread across the multiple docs that it seems like a ubiquitous tool instead of being actually a library sponsorship.

This is not a fair game - not with the rivals, but with the developers that are reading the docs.

from react-i18next-gitbook.

fair...really got to calm down a little if the topic is about being fair to rivals -> have a look at i18nexus.com -> do you feel it fair that built on top of i18next (even promoting itself with i18next) and neither being a member nor contributing to i18next (not sponsoring, nothing)...so please stop about talking fair. Or do you think it's fair to compete with companies having huge ad budgets

Yes the advertising for our locize is getting into your face -> but honestly I nowadays prefer 1 user going and trying locize because of the visual force than an other 100 users using in and not even think about the hard work and considering buying us a coffee.

from react-i18next-gitbook.

I was really talking about being fair with the developers who are reading the docs. Open source is terrible at those moments and I can't argue with you (never tried, actually, and if it seemed so, sorry!)

That said, you can still advertise the project in many different places and methods, but again, it's about fairness with the developer reading the docs: ads shouldn't be confusing, nor steer you away from your current objectives. Many sections in the docs are actually just ads, and could be boxed and noted as such (otherwise, the reader follows along with the topic and then stops to realize it's not "the next step"). Worse than that, some other parts also feel like documentation but are actually pointing to an unrelated service (to the topic being discussed in the page, like suggesting an inspector tool among extractors, instead of being a separate section in the plugins page).

This is my last cent on discussing the way the docs are read by newcomers. I guess, if you disagree, your point will be that you want to also be unfair using camouflaged ads and repetition, as to tip the scale back to your side and out of i18nexus - while I think there could be a middle-ground, I also understand, since their behavior is borderline disgusting now that I got the comparison.

from react-i18next-gitbook.

Btw, I was looking into how Locize actually works (since I got moved away by the ad policy) and found a couple of small mistakes :)
We're currently using a free service, but will probably move into a paid tier in the future - which is very expensive, so I'm maintaining a list of backup services. I'll add Locize to it!

from react-i18next-gitbook.

Btw, I was looking into how Locize actually works (since I got moved away by the ad policy) and found a couple of small mistakes :)
We're currently using a free service, but will probably move into a paid tier in the future - which is very expensive, so I'm maintaining a list of backup services. I'll add Locize to it!

thank you for your help, just fixed those typos...

from react-i18next-gitbook.