Please make it clear this is not a Vercel product 🙏

[leerob]

Hey! We are continuously seeing folks who think this an official Vercel product, and getting very confused.

Could you make it more clear on the website that this is not created by Vercel? Thank you!

https://twitter.com/nwbotha/status/1445436159610531848

[unix]

This is already noted on the current documentation. But since some people still misunderstand it, I will add a bolded note to the readme and documentation next.

[leerob]

Thank you @unix, we appreciate it. And we're fans of the work you're doing as well ❤️

[unix]

I've added a few new statements to make sure everyone can understand that this is just a community product that: #637 . If you think additional hints need to be added or statements need to be adjusted, you can reply again.

[DennisSmolek]

Hey guys, just to add to this, one potential vector of confusion (as it was for me)

Is the Vercel Design Guide and more specifically the Playground: https://vercel.com/design/playground

You do a quick google and you're here: https://geist-ui.dev/en-us

Which as a design language across all the stuff they do you just assume it's "Another Vercel Thing"

The powered by etc.

The multiple call outs even linking here might seem redundant but its working!👍

[unix]

@DennisSmolek You make a very good point, that's what I'm trying to avoid. But I had to do this in order to apply for Vercel sponsorship (GitHub Org deploy), and on reflection, it does seem misleading.

[unix]

I'll talk about this in full:

1. The old free team version Geist was using expired the other day, so I found this link and thought it would be a good idea to apply for a free sponsorship.

2. 719 was then created to complete the site's sponsorship requirements and a request email was sent.

Email content:

Hi t[here](https://vercel.com/support/articles/can-vercel-sponsor-my-open-source-project),

Thank you for getting in touch, you can read more about our sponsorship [here](https://vercel.com/support/articles/can-vercel-sponsor-my-open-source-project). 

If you meet the criteria outlined here then please:

Create a new team in your account, this will start the 14 days trial for our Pro plan,
Share the link to your public Git repo with us,
Add the Vercel banner (attached to this reply) to your site footer and your Git's README,
Add a link back to https://vercel.com/?utm_source=[team-slug]&utm_campaign=oss, replacing [team-slug] with the slug of your team.
The Product Advocacy team will review your sponsorship application once you have completed the steps above.

Samuel Ko
▲ Senior Customer Success Engineer at [Vercel](https://vercel.com/)

--------------- Original Message ---------------
From: [[unix.bio@gmail.com](mailto:unix.bio@gmail.com)]
Sent: 2/5/2022, 8:50 AM
To: [unix.bio@gmail.com](mailto:unix.bio@gmail.com)
Subject: request Vercel's sponsorship for a website

-----------------------------------
Area: Sponsorship
Name: Witt
Team: geist-ui
Previous Page: Not Specified
-----------------------------------
Hi, I am the author of Geist, an open-source component library inspired by the Vercel design, which has a certain number of users and has been maintained for 2 years. I would like to request an Org account for the maintenance of the documentation site and other affiliated open source projects.

- GitHub: https://github.com/geist-org/geist-ui
- Site: https://geist-ui.dev/
- Current Vercel's account: https://vercel.com/geist-ui (Legacy plan)

I would be happy to indicate the sponsorship from Vercel on the website and README, but before @leerob mentioned that I need to mark the site as not related to Vercel in [README.md](https://readme.md/) (https://github.com/geist-org/geist-ui/issues/635), so does adding a banner or logo have an impact (maybe not, I'm not sure), or should I do something about it.
Thank you for reading and I look forward to your reply!

[unix]

@DennisSmolek Although I explained the situation in email, the truth is that there are still viewers like you who will misunderstand, so next I will cancel the sponsorship request and migrate the documentation site to cloudflare, and remove the changes of #719

[DennisSmolek]

I don't think you need to do all that..

I just wanted to share how I jumped to same conclusion and how I got there.

(IMO): leave out the disclaimer for the time being, and perhaps reach out to the Vercel team and Request they put clear language on that page.

No matter where you deploy the source of confusion is from Vercel.

as it just says "Geist Components" and is on a core Vercel url/project it's unclear the relationship and if it's another tool they built, (and they build a lot)

They can add "Vercel Components are Themed React Components from the Geist-UI Library | https://geist-ui.dev

(visible URL link intentional)

-

A little bit "Friendlier" disclaimer might be: "Although We are proud Vercel used our work, we are not affiliated.."

And just link back here...

[DennisSmolek]

OH WAIT

I have it backwards..

You built it OFF Vercels Design System..

Honestly I didn't go deep enough and just jumped to the components..

I'm not sure the 'right' solution sorry...

perhaps move the origination/inspiration from the guide page to the home page with a subtle color highlight?

[unix]

@DennisSmolek

It doesn't matter. I actually added the statement in the documentation site and in the readme, but it always causes misunderstandings. So I'm going to adjust the direction of Geist, you can learn more here: #722

I think Geist can be a good design system, but it shouldn't be a parody of styling, this is a way to make fundamental changes. (In fact, many components are already undergoing such changes)