EDIT: Feel free to downvote but please answer. TFA does not answer it.
We do it for our company website. Markdown makes it easy to have a pull-request-based workflow for reviews. It’s neat and uses the tools we as developers are used to. Another advantage is that the end result is static pages. We can literally host them anywhere, though we’re currently using netlify for convenience. They don’t need security patches either.
Does that make it superior to hosted WordPress? For our needs: yes. For other people’s needs? Don’t know.
WordPress is good, but some see it as overkill.
Might as well be a Facebook page.
Why is the youth so adverse to owning their own data?
I don't see any vendor lock in evident in any of this. Plenty of flexibility to both move your git code to your own self hosted git, and quite easy to host it on your own webserver on DO or wherever instead of Netlify.
I think the appeal is that you have complete control over your site/blog and should you choose to somehow monetise the content, e.g., adding singups and subscriptions to premium content or even ads, you can have complete control. With a combination like this you start at 0$/m for ever (or at least until Netlify stops offering free services) and take it from there. I probably won't do this for a travel-blog but its nice to have the choice and to be honest I wanted to try out a combination of the tech mentioned above and see how far I can take it for 0$.
I still have an old blog on Wordpress (http://pyscience.wordpress.com) and its done very well but I never liked the fact that Wordpress just sticks ads wherever it wants to unless I get the premium subscription.
For the many many static sites that I throw out with either Jekyll or just plain HTML/CSS/JS, I know that once I drop them to something like S3 + CloudFront fronted by Cloudflare, it will very very unlikely go down.
They all have their time, places and circumstances.
It's good to want to know why some people want to do X, but try to ask it in a way that doesn't make a negative assumption about the people taking a certain approach.
I feel like there is a LOT in this comment that is reading much more into a question that very likely are not even there, to take the position of scolding someone just because their inquiry was delivered in brevity.
It's hard to give good advice in a tone that isn't paternalistic, and I should get better at doing that. Sometimes you just want to ask a genuine question without somebody questioning your phrasing.
What prompted me to give out advice is "Feel free to downvote but please answer". I don't believe the comment deserves a downvote, but I assume (and it may be, as you put it, reading too much into it) that some downvotes come from people who are tired of seeing the attitude I describe in my reply (https://news.ycombinator.com/item?id=7650799#7651343).
It's a case of greedy matching /why would you do/.
And then I learned that there is a niche (compared to 30% WP) of technical people that have their content in GitHub anyway and profit from simple deployment through netlify. It just fits their workflow. I had the typical business user (another blog post said everyone!) in mind and I don't see them to be able to handle git so it sounded very far fetched which was reflected in the tone.
This is free (domain aside), doesn't require managing upgrades and presumably has some redundancy.
SEO experts and social media marketers will tell you that nothing beats Wordpress, but that's not true I've seen plenty of static sites that are much more engaging, work faster and rank higher when they post good content often.