inlang ecosystem compatible badge for marketing

[samuelstroschein]

Idea

We can use the inlang ecosystem compatible badge for marketing individual products https://inlang.com/g/7777asdy/guide-nilsjacobsen-ecosystemCompatible on external sites like the Figma store, @opral/inlang-ide-extension marketplace.

pros

• increases the value of the presented product [if the viewer knows what the inlang ecosystem is]
• increases inlang's brand awareness as ecosystem
• backlinks ;)

cons

• yet another things that needs to be maintained and communicated

[samuelstroschein]

@felixhaeberle @martin-lysk do you (as app providers) see value in placing the badge into the figma and vscode readme's?

@NilsJacobsen close this if you think it is not worth it.

[NilsJacobsen]

I actually like it. It could also be used for projects. If they are inlang ecosystem compatible, they can give contributors the signal that they can just plugin fink to translate ...

[martin-lysk]

I like the badge and i would totally use it - as soon as the process feels good.

We are close but not there yet: Imagine you can become a contributor to one of your loved open source projects with just a click of a button and fix a translation in your language.

Two nice things here:

1. you get this rewarding feeling of becoming a contributor in a project you like
2. you connect this feeling with fink/inlang/opral

I would park this for now focus on the process that the badge will start off.

[felixhaeberle]

👍 what @martin-lysk said

[samuelstroschein]

conclusion seems to be "too early". @NilsJacobsen close this for now?

[NilsJacobsen]

For parrot yes but i can already see a simple badge for ide extension & i18n-action. Just discovered that we will have the same branding problem with the action.

[samuelstroschein]

Just discovered that we will have the same branding problem with the action.

You mean if we name the action "inlang github action"? Yes, we shouldn't name any product anymore "inlang X". Maybe with the exception of the inlang cli.

[NiklasBuchfink]

Supabase added a GitHub badge for fans today: https://twitter.com/supabase/status/1752794390815223973

This might also be interesting for our products and inlang fans. This could indicate to contributors or teams that this repo works with our ecosystem, it's a free backlink and it's free advocacy.

[NilsJacobsen]

Let's go

inlang ecosystem compatible

[![badge](https://cdn.jsdelivr.net/gh/opral/monorepo@main/inlang/assets/md-badges/inlang.png)](https://inlang.com)

fink

[![badge](https://cdn.jsdelivr.net/gh/opral/monorepo@main/inlang/assets/md-badges/fink.png)](https://fink.inlang.com)

i18n supercharged

[![badge](https://cdn.jsdelivr.net/gh/opral/monorepo@main/inlang/assets/md-badges/fink.png)](https://inlang.com/m/r7kp499g)

[felixhaeberle]

@nilsjacobsen can't they be higher res, e.g. svg and not png? they seem oldish and pixel-y.

or is this a limitation by github/jadelivr? 🙄

[NilsJacobsen]

If I make them high res, they get bigger. I can try to make them a jpg but I don't see a huge improvement 😬

[samuelstroschein]

@NilsJacobsen smart move to use jsdelivr to automatically have a good cdn!

[NilsJacobsen]

@felixhaeberle we can try svgs. I put it on the list.

[felixhaeberle]

If I make them high res, they get bigger. I can try to make them a jpg but I don't see a huge improvement 😬

@NilsJacobsen can't you set a default size on the svg? this should render them in the correct size. or is github weird?

[NilsJacobsen]

Here are the svgs 🚀

[NilsJacobsen]

Where we can use this badges:

• [ ] For our own compatible products
• [ ] Fans can add it
• [ ] Projects that use fink can shortcut on the readme's top
• [ ] Projects that use i18n supercharged can shortcut to the marketplace
• [ ] We can eventually add stack-specific badge to generate backlinks to the category pages

[felixhaeberle]

@NilsJacobsen thank you for the svgs 🙏🔥

[samuelstroschein]

@NilsJacobsen why a badge for fink? we already have a badge?

[NilsJacobsen]

Because it was no effort. Maybe you can put it in the first line of the repo readme that is better then loosing conversion with the badge deep down in the docs.

[samuelstroschein]

@NilsJacobsen confusing. now fink has mutliple badges. which one should a user choose?

suggestion: remove the fink badge and avoid the communication problem

[NilsJacobsen]

@NiklasBuchfink if we don't see a benefit I can delete the image.

Follow up question: Where do we want to show the badges? On the badge page or is it a entirely different product and this is more like a marketing asset reachable from the footer ...

[samuelstroschein]

Where do we want to show the badges?

In our inlang.com docs "publish on marketplace".

I further vote to remove the ide extension badge. What value does the ide extension badge have? If we don't have the ide extension badge (& fink), we don't need to think about where to place which

[NilsJacobsen]

I just thought that this can be a backlinking channel. The compatible badge can only be used by partner projects so we don't use it as a fan badge. But I agree let's start with the first badge and see if we need the others.

[NilsJacobsen]

Added it to the docs -> https://inlang.com/documentation/publish-to-marketplace#inlang-ecosystem-compatible-badge

We can now use the badge. Should we add it to every compatible package or just apps?

[samuelstroschein]

@NilsJacobsen just apps that are published on external marketplaces. don't go wild :)

[NilsJacobsen]

@opral/inlang-sherlock @NiklasBuchfink can you add the badge on the external landingpages. So we can close this?

[NiklasBuchfink]

@NilsJacobsen Done ✅ https://github.com/marketplace/actions/ninja-i18n

[NilsJacobsen]

I close this as it is mainly done