I've had a website built in Gatsby for a while now, but I really did miss having it in .NET. Here's how and why I moved to a .NET static-site instead of Gatsby.
Working with Kentico Kontent and Gatsby has been a nice learning curve for me, as I pick up and build upon my front-end developer skillset. You can end up taking quite a lot for granted when you're working with .NET. Securing your calls to an API can be one of these things, as you add things like API keys to your .config files and make sure that you don't push those files into your git repo.
About this time last week, I'd just published a post about moving to Gatsby from .NET Core for my own personal site and was walking to a Gatsby meetup in central London.
There is no escaping the amount of traction that static site generators and JAMStack are getting these days. As a traditional .NET developer, you may feel that your skillset doesn’t contain the things you need to jump on this bandwagon and make the most of the benefits available. But is it really that difficult to get up and running with a new stack?