[rjzzleep]

I still don't fully grasp it. What's the advantage here? Besides the fact that Netlify provides a CDN when you decide to use them(which granted can be very helpful to some people).

I see the appeal against Wordpress. Wordpress is hell to integrate, slow and a security nightmare. But I don't see the advantage compared to, say Kirby.

There's a post somewhere down below saying smashingmagazine moved to netlify from a Rails, Shopify, Kirby mix[1]. "move would need to include solutions for a decoupled CMS, comments engine, eCommerce platform, and member login."

What Netlify provides, reminds me of what parse used to provide. Except that it adds a CMS and targets Web applications with identity[2] etc. They sell a client facing website platform. Good for them. But that's not what the post is about. So yeah, I do find it misleading.

[1]: https://www.netlify.com/blog/2017/11/21/smashing-magazine-is...

[2]: https://www.netlify.com/docs/identity/

[bobfunk]

Netlify CMS is a self-standing open-source project. We maintain it and are puring a lot of resources into it, because we think it's really important there's a good open-source solution on the market for projects built with static site generators.

However, the CMS itself is not tied to our deployment and automation platform. It can also be setup to work for GitHub pages or self-hosted setups.

The basic idea is that's its an editor friendly content management UI for persisted data stored in a GitHub repository. What you do with that data is up to you.

[detaro]

> The basic idea is that's its an editor friendly content management UI for persisted data stored in a GitHub repository.

Since it was discussed in a different subthread: If you would describe it like that, why isn't something straightforward like that the blog post title?

[ridruejo]

What you guys are doing is awesome. I don’t understand all the nitpicking going on in this post. Keep doing what you are doing