Actually, it seems you pull in the desc from the repo, that's better, this can be closed, but might be good to add that as a comment the starters.md code snippet in the docs? https://www.gatsbyjs.org/docs/submit-to-starter-library/#steps

I didn't even know we read package.json description, but it does seems a bit inconsistent:

• on listing view we show package.json description ( https://www.gatsbyjs.org/starters?s=gatsby-starter-contentful-i18n&v=2 )
• but on detail view we show description from .yml file - "N/A" in this case ( https://www.gatsbyjs.org/starters/mccrodp/gatsby-starter-contentful-i18n/ )

Might be worth to look into consolidating those? Not sure if it was intentional or not.

/cc @amberleyromo

Nice find, @pieh. It also seems that the description pulled and displayed for my starter is not the current one. I updated it 4 days ago, so not sure how those are cached either.

I'm not sure either about caching here - I lack lot of context on how starter showcase works, but let's merge PR in meantime, so your starter have proper description ;)

Holy buckets, @mccrodp — we just merged your PR to Gatsby! 💪💜

Gatsby is built by awesome people like you. Let us say “thanks” in two ways:

1. We’d like to send you some Gatsby swag. As a token of our appreciation, you can go to the Gatsby Swag Store and log in with your GitHub account to get a coupon code good for one free piece of swag. (Currently we’ve got a couple t-shirts available, plus some socks that are really razzing our berries right now.)
2. We just invited you to join the Gatsby organization on GitHub. This will add you to our team of maintainers. Accept the invite by visiting https://github.com/orgs/gatsbyjs/invitation. By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.

If there’s anything we can do to help, please don’t hesitate to reach out to us: tweet at @gatsbyjs and we’ll come a-runnin’.

Thanks again!