Update Next.js icon and data

[sisp]

Issue: closes #7742, closes #7626

Checklist

• I updated the JSON data in _data/simple-icons.json
• I optimized the icon with SVGO or SVGOMG
• The SVG viewbox is 0 0 24 24

Description

The new Next.js wordmark uses gradient transitions which cannot be converted to a monochromatic icon. We've discussed in #7742 that it might be better to use the full wordmark instead. I've also updated the guidelines link as suggested in #7626.

[LitoMore]

I'd prefer just N.

Next.js is using the logo on their main project. The full trademark looks not good on a badge.

See https://github.com/vercel/next.js/blob/canary/packages/next/README.md?plain=1#L22

[sisp]

But what do we do about the gradient transition?

[LitoMore]

Let's ask Next.js for help. Just let them know Simple Icons does not support gradient colors.

It would be good if they can design a specific version for Simple Icons.

[sisp]

I've started a discussion over at Next.js: vercel/next.js#41193

[adamrusted]

Hey @ijjk - is there currently a monochrome (including without the gradient) version of the NextJS N icon? If we're able to use it here - any chance you can share somewhere it's publicly available?

[adamrusted]

The SVG itself is a perfect match, if we go ahead with the full wordmark until Next update their icon format. Just a quick change to the JSON, seems they've updated URLs since this PR was put in. Once that's done, let's get this merged in!

[LitoMore]

I want to keep their icon visual at https://github.com/vercel/next.js.

BTW, the Next.js Conf will be back in October. They should revise the logo again.

[adamrusted]

I want to keep their icon visual at https://github.com/vercel/next.js.

Oh I totally agree, but in the absence of an official monochrome treatment for the 'new' icon - we should go with a safe monochrome treatment from the brand. Let's hold fire until Next Conf, and if there's no significant re-brand I'd look to merge this one in.

[PratyushJayachandran]

I want to keep their icon visual at https://github.com/vercel/next.js.

Oh I totally agree, but in the absence of an official monochrome treatment for the 'new' icon - we should go with a safe monochrome treatment from the brand. Let's hold fire until Next Conf, and if there's no significant re-brand I'd look to merge this one in.

So I was looking their Readme and saw them using Next.js icon hosted in simple-icons.
It is the same as their favicon on https://nextjs.org/
So why are we changing it to wordmark?

[adamrusted]

Still no official monochrome treatment from what I can see. We can either proceed with the wordmark, as that's the only monochrome treatment offered by the brand at this time - or we adapt their currently used icon (as I imagine we had to do with the old version too!)

[PeterShaggyNoble]

I vote to give the icon our own treatment. But, then, I'll always vote in favour of an icon over a wordmark!

[PeterShaggyNoble]

So, @simple-icons/maintainers, where have we landed on this?

[service-paradis]

They have a monochrome version of their favicon buried in their Github:
https://github.com/vercel/next.js/blob/6b3d145e7e7e88037f4e326cc63038814ab5fd76/examples/cms-prepr/public/favicon/safari-pinned-tab.svg?plain=1#L4

So, I think we're safe!

[adamrusted]

@service-paradis - that looks to be the old version of the icon, note the last commit was 2yrs ago.
The new one is a much chunkier font.

[service-paradis]

Hum... yeah, you're right...

[PeterShaggyNoble]

It's been well over a year since Lito started the discussion in their repo and there's been no response so I think it's time we make an executive decision. Consensus seems to be that we use the icon rather than the wordmark so could you update the PR accordingly, @sisp? The best option is probably just to use the same treatment as for our existing icon.

contributed

[PeterShaggyNoble]

I think the diagonal of the "N" should still touch the edge of the circle here, @adamrusted.