erquhart

8 ms·

1.
by erquhart 2y ago
> 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. > i
2.
by erquhart 7y ago
Couple of clarifications: - Netlify is multi-cloud: https://www.netlify.com/products/edge/ - Content from a headless CMS like Contentful is generally retrieved at build time, not rendered in the browser
3.
by erquhart 9y ago
There's a tool called staticman - it doesn't integrate with Netlify CMS (yet), but it's a great git-based comments solution: https://staticman.net/
4.
by erquhart 9y ago
Yep! Hit the docs website and click "Get started": https://www.netlifycms.org/
5.
by erquhart 9y ago
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 th
6.
by erquhart 9y ago
Preface: Netlify is a platform that enables static development, while Netlify CMS is an open source project created by Netlify. In a broad sense there's nothing that can't work with the CMS - you can integrate a Mailchimp sign up
7.
by erquhart 9y ago
No documentation for this yet, but here's the PR to add the file system backend: https://github.com/netlify/netlify-cms/pull/786 We have a lively community on Spectrum if you have questions: https:&#x2F
8.
by erquhart 9y ago
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 tha
9.
by erquhart 9y ago
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 se
10.
by erquhart 9y ago
Yes, the backend system is actually pluggable, so anyone can write one to fit their use case.
11.
by erquhart 9y ago
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.
12.
by erquhart 9y ago
Odd that this and other comments in favor of the article are being systematically down voted.
13.
by erquhart 9y ago
I definitely weighed that out, and I appreciate you mentioning it. I settled on this title because it's accurate for the implementor, and because folks are having a hard time understanding the benefit compared to a large solution like
14.
by erquhart 9y ago
It's meant to be implemented by a developer, but it doesn't take much skill, and can be hosted for free on a number of services. I was a champion of Netlify well before I became an employee, so I still shamelessly plug them as the
15.
by erquhart 9y ago
Cost isn't the big issue, there are plenty of ways to do it for free. I'm curious why you think this is against GitHub's TOS? We're creating commits and pull requests via their API, which is exactly why the API exists, p
16.
by erquhart 9y ago
Yep, we're managing Git content through their API, which is exactly the kind of thing the API exists for. There are working PR's for open for Bitbucket and GitLab backends too, those will be out soon.
17.
by erquhart 9y ago
It's actually great for highly complex, high traffic setups as well - Smashing Magazine was a conglomerate site using Wordpress, Kirby, Rails, and Shopify, and are now entirely static (10x faster literally) and using Netlify CMS for co
18.
by erquhart 9y ago
Post author here: As others said, it's a CMS for static site generators. Traditional CMS's are opinionated server side applications that live outside of the site developer's workflow, and are subject to maintenance and a hi
19.
by erquhart 9y ago
Post author here: There's definitely no shortage of options - the CMS exists to fill a very specific trifecta that we believe are critical for modern static development. It is: 1. Git based, which is how devs are working increasingly 2