So little update on this. I did more research on how the CMS works and while I don’t think it’s worth re-creating the editorial workflow logic, the very basics of it are actually incredibly simple. So I’ll see how far I can actually get this proof of concept to go in the next couple of weeks
@bmatthews Have you considered moving off of Netlify and hosting those sites on V3rcel? Have a similar setup but we only pay for the Pro plan which just 20$ a month.
Just adding my piece here as well, if not for Netlify CMS, I - and the company I work for - would not be a Netlify customer right now (and most likely won’t be anymore if we end up switching to another CMS). It would be a shame to see a project with such potential go to waste…
Either way, a clear answer on Netlify’s decision would be very much appreciated at this point and allow us - the community - to make plans for the future (whether it be a fork, a new project, or just moving on to another inferior existing product).
Just adding my viewpoint here. I would love to see this project blossoming again. if not for Netlify CMS, I would not be a Netlify customer (likely won’t be anymore if we end up switching to another CMS).
I always viewed Netlify as a pioneer in Jamstack. But the sunsetting of this project is somehow eroding that belief.
I can only agree with the previous speakers. The future of Netlify CMS is very important to me, as I want to develop website projects in the future exclusively gitbased without the complexity of server-side hosting or a database.
Where do we go from here with this project? We are all waiting for feedback from Netlify. Is it possible that the project will simply be discontinued and numerous projects will face rebuilding? I would feel that way and in that case I offer my help to work together on a further development.
I have built a complex, mulitlanguage page builder that allows you to create a page using Nuxt/Vue virtually entirely through Netlify. There are some things that are still missing in Netlify and I am happy to invest ideas and manpower. I just can’t take over the management of the project, unfortunately, I don’t have the time for that.
I’d even rather Netlify would come forward and create a new version from the current beta anyway. That would be a sign for a right direction.
Not really a fork and more of a spiritual successor. NetlifyCMS is great but it’s a huge codebase and I think part of the issue it got abandoned is that there’s too much there for an unpaid team to manage?
Either way, I’ll post here once I’m over the initial discovery part and I have something concrete to show
In the meantime Static CMS looks fantastic, probably going to switch to that!
Hi folks, thanks so much for all of your thoughtful commentary here! I have passed all of your feedback on to the Product team.
What I can share is that you can absolutely count on us to not remove the CMS from github or change the license to prevent any sort of usage. You can continue to fork the CMS to make any changes that you need.
I just finished adding Netlify CMS to several of my repos and I was having an issue and I came across this thread and now I am quite sad. I really love Netlify and Netlify CMS. I really hope that Netlify CMS comes back into active developer. As an amateur I was drawn away from WordPress and to JAMSTACK’s speed and stability but I’ve found mostly heartache.