-
Notifications
You must be signed in to change notification settings - Fork 22
Switch from NetlifyCMS to StaticCMS #61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey I just put together a POC for working with StaticCMS based off of the work you did here. Please let me know if you are interested in collaborating or if I can publish |
I'm super keen on moving forward with static cms... keen to hear where this is heading! |
What about decap cms? Seems like the project might be revived |
Agreed decap has the backing and support needed for an open source project
…On Mon, 13 Mar 2023, 4:02 am onionhammer, ***@***.***> wrote:
What about decap cms?
—
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARTWGA65FMFMOOBO4HC5P63W3YFSPANCNFSM6AAAAAAT6EOJEM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
They haven't pushed a single commit other than rebranding ones. We can talk when they're going to publish a new release |
@Marocco2 I dont think you shouldn't pursue astro support for StaticJSCms, but why not just have two astro plugins? |
I didn't say that it shouldn't be considered at all. We must see what they're gonna do with NetlifyCMS repo before jumping up to the hype train. |
I vote close this thread as netlify CMS is transitioning to decap |
Hi!
Today StaticCMS has released its 1.0.0 version of the successor of NetlifyCMS, which it has been abandoned.
https://github.com/StaticJsCMS/static-cms/releases/tag/v1.0.0
It may be good switching ASAP to get better features and security in the future
The text was updated successfully, but these errors were encountered: