It feels that way re: management/leadership crisis. Suddenly such a useful product has zero maintainers? Just odd. There are some kinks in it and definitely some tech debt by the looks of the code, but I’d hardly call it something worth stopping all development on. As you said, there are real customers using it at this point. It has great value.
At the very least, Netlify could monetize it with a subscription model. I’d pay $10/mo if that’s what it took.
Hi @SamO thank you for the update and raising this discussion with product. Any updates you can share so far? NetlifyCMS is truly loved by clients because of its simplicity and live previews. Best from Amsterdam
so forestry.io is getting sunset so that’s out. I set one of my clients up on Netlify CMS for their Jekyll site. I wanted to check if this CMS would suffer a similar fate under the erratic sways of JAMstack development and here we are
@Roneo.org that’s an excellent question. I’m shopping for a CMS for my Jekyll builds I did for a bunch of non-profits. I built a site with Netlify CMS after forestry announced their end of life but I really want to be sure I’m setting people for success.
We have also already promised, also in this thread (here: Is this project dead? - #50 by hrishikesh) that we intend to keep the auxiliary services to allow you to continue to use our CMS (or others) on our service running for the foreseeable future.
While Netlify is still considering the future of the codebase, and someone above my pay grade will come announce our future intentions someday in this thread (once they are decided), I think you can read between those lines that your best bet today would likely be to use the fork. This of course will come with the expectations of support that come with a package maintained by a third party with whom you have no financial relationship, so you have to decide if that works well for your business or not.
My two cents: the fork is a fantastic and commendable effort, but it’s a complete rewrite, removes a huge number of features, will never even attempt be kept in sync with the original, and most important of all - is made by a solo developer without many other OSS projects that I’m aware of, with no financial backing, for a church website. It would be a big risk for most teams to rely on it for a production use case.
If all of that is fine for your use case, then go ahead. But the Netlify team shouldn’t point to it on their repo. It’s not a like for like replacement and an official mention would give the wrong impression that it’s safe for production use.
Sorry to be late to reply but I’m happy to lay out the main pain points for you and others. I realize that the answer to the thread topic “is it dead?” has been answered Yes so I’m no longer looking for support, just sharing for the sake of it.
As @mfan noted, the way Netlify now requires GitHub contributor seats led to unforeseen monthly costs
We also had to solve one MAJOR technical lack of NetlifyCMS: graphql type generation. We rolled our own custom script that parses the YAML and generates typings that Gatsby can use for its graph. Without this, you can still use the CMS but in a large project with a complex schema you’ll need to automate it at some point. Whoever is writing that Static CMS hopefully has realized this and addressed it for Gatsby.
On the bright side all the CMS ever did to our codebase was add a bunch of static markdown files and static assets. So simply discontinuing use of it in the future won’t break the code, it will just eliminate the CMS admin frontend. But that’s preferable to something like Contentful where the entire codebase ends up wrapped around their specific data format. Porting to another CMS in the future is still feasible.
Sorry to see this project put on ice, we really liked it!
Successfully switched my Gatsby project from Netlify CMS to Static CMS. Had to write some custom email templates due to the lack of routing. But other than that, it’s working super smoothly.
The steps I took were:
Granted by default if someone tries to reset the password or if you send someone an invite, the URL doesn’t contain /admin/ so they won’t be automatically redirected to admin. So I had to roll my own using a custom email template. Granted that’s a pro-level feature, but to me, it was worth it.
You can use the static folder in Gatsby to write your templates.
Otherwise you can just tell whomever to manually just add the /admin/ to the URL.
StaticCMS is, as far as I can tell, identical to Netlify CMS. My yml file and identity worked fine.
Working on a YouTube video documenting the process.