Closed ptman closed 1 year ago
Although Netlify CMS is currently unmaintained, I'm not convinced Static CMS is the right choice to use at this time either:
This comment on the Netlify forums summarizes the situation well:
I want to note - anyone considering using the staticccms fork should read this comment and the thread surrounding it: Create NetlifyCMS to StaticCMS Migration Guide · Issue #46 · StaticJsCMS/static-cms · GitHub 25
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.
I am not looking at supporting Static CMS at this time.
Netlify CMS has new maintainers and is being rebranded to Decap CMS.
We hope the project will continue to prosper. This repo will update to match in #2.
https://github.com/staticjscms
Static CMS is a fork of Netlify CMS focusing on the core product over adding massive, scope expanding, new features.