chore(starters): add gatsby-starter-i18n-bulma

[kalwalt]

Description

Proposed starter https://github.com/kalwalt/gatsby-starter-i18n-bulma to add to the starters list

Documentation

The main feature of this starter is the slug switcher for multilanguage. Basically with this system you can have any slug that you want. With i18n plugin you can not change the slug, with it instead let you have a slug in a language, example:

in English:

 /en/about/

in Italian:

/it/presentazione/

The starter is also based on Bulma, Netlify CMS and many more features...

Related Issues

See #14250

[kalwalt]

I don't understand what is to be changed followed this result https://github.com/gatsbyjs/gatsby/runs/490472157 i think i added the tags included in categories.yml but maybe i'am wrong...

I also upgraded gatsby-plugin-sharp gatsby-transformer-sharp gatsby-transformer-sharp to the latest, because the fails in CircleCi build-test

[laurieontech]

Thanks for the PR! It looks like "Media" and "Freelance" are the tags causing this to fail.

[kalwalt]

Thanks for the PR! It looks like "Media" and "Freelance" are the tags causing this to fail.

Thanks to you @laurieontech ! ok i will remove them. Can you tell me something more about the other errors? I upgraded some pkgs but i think it's needed also to fix other dependencies. It's not included yarn.lock or package-lock.json in the starter so maybe that is the problem...

[kalwalt]

i found that there is an issue with decompress #21791 the fix is on the way kevva/decompress#73 waiting for the fix.

[gillkyle]

Hey @kalwalt! Thanks for the starter and a detailed README with it 🎉

The validation tests failing due to the npm audit will fail for other starts like yours that use similar plugins. From what I understand they actually don't pose a real vulnerability because what's shipped to the browser won't have the vulnerability anyway so I'm going to merge this.

[gatsbot]

Holy buckets, @kalwalt — 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. We’ve got Gatsby t-shirts, stickers, hats, scrunchies, and much more. (You can also unlock even more free swag with 5 contributions — wink wink nudge nudge.) See gatsby.dev/swag for details.
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!

[kalwalt]

WOW! Thank you @gillkyle @laurieontech very happy for this!

The validation tests failing due to the npm audit will fail for other starts like yours that use similar plugins. From what I understand they actually don't pose a real vulnerability because what's shipped to the browser won't have the vulnerability anyway so I'm going to merge this.

yes, i saw the discussion will see when it will be solved...