Hacker News Reader

Comment by robbiemitchell | Hacker News Reader

Love Netlify. Have to migrate soon because we need a visual CMS for marketing to edit the site more visually and "Netlify CMS" is not nearly as mature as Netlify itself, or competitors like CloudCannon.

Netlify: please make the CMS a first-class citizen so we can keep projects on you!

View on HN

(I work for netlify).

You are aware that any headless CMS works well with netlify, right? (even some less headless ones, but these are easy): Contentful, Sanity, Ghost, Forestry? Our CMS is an open source project that is community maintained these days, not managed by us :)

Thank you for the list! For anyone interested, apparently Forestry is going to eventually be sunset in favor of Tina, but seems to be built by the same team: https://twitter.com/forestryio/status/1386274017187975168

NetlifyCMS has worked well for me, but I think Tina is what i'm going to try next. It's a good time for headless CMS options, so many to choose from!

I love NetlifyCMS but it sounds like you may be interested in what we're doing at tina.io. Contact me if you'd like a quick demo scott[at]tina.io

Wow! Very nice, real-time preview is rad.

Link to save you a click https://tina.io/

Strongly agree. I created an awesome integration between Netlify and our no-code platform WeBase [1] to solve this exact problem.

I believe Netlify could grow even more if they embraced some form of "no-code" website editing in their offering or directly partnered with us.

But what do I know? I am just sitting here watching Webflow gobble up this market! :-)

Congrats to the Netlify guys on this raise! Maybe we should apply for their new investment program.

[1] https://www.webase.com

You can use WordPress with a full site editing enabled theme providing the visual builder, and host a static version on Netlify.

Check this out: https://lokl.dev/

I tried to publish a very simple static site with Netlify not that long ago (post COVID lockdowns). Just several (~4) plain text (unminified) JS, CSS, and HTML files. There was also a .git directory pointing to a non-GitHub remote, not that it should matter, since I wasn't trying to use Netlify for builds. I just wanted it to do a straightforward deployment on par with FTPing your work to a dumb host. Turns out, this did matter. The Netlify CLI was so thoroughly confused by the presence of this .git subdirectory that it failed hard. Not even a cryptic error or stack trace, the process just up and terminated. It took some poking around before I realized that what the trigger was.

The utter failure to handle what seemed to me to be a straightforward, "hello world" sort of use case did not inspire confidence.

Reply on news.ycombinator.com