erquhart

> College isn't just a place that teaches you how to do a job; it's also a safe, structured, and productive environment for people to continue growing up – and to fend off adulthood for a bit.

This is actually a problem.

> in developed countries, there is an era between ages 18 and 25 when we collectively agree to let people explore the world and figure out what role they want to have in it. He calls it "emerging adulthood". And college is an environment built for emerging adults – a place where kids can leave their family environment and finally have a chance to independently shape their futures.

This is a wholly inaccurate description of college.

The CMS is specifically made to work with Git, because so many developers are already using it for the rest of their site development. That said, it's not impossible to write a non-git backend, but it's heavily bent that way at the moment.

Shouldn't have said "systematic", didn't mean to insinuate a collaborative effort. Silently down voting is what I'm pointing out, as it tends to be non constructive, I don't think I'll ever get used to that.

That said, my comment was ultimately pointless and I regret making it, agreed.

Asset storage integrations are supported, but it’s very early. That’s one area where we expect to strengthen after 1.0 drops in December.

That said, you don’t need a direct integration to work with a service - you could upload files to a service and enter the url into the cms as a stopgap.

Yes, the backend system is actually pluggable, so anyone can write one to fit their use case.

Yep, the source of a widely useful CMS will always be non trivial - but you have to build your site inside of a traditional CMS, where it lives on a server. Netlify CMS is a page on your site that creates and edits markdown and data files. The difference is real :)