What is the future of netlify-cms?

[bmackinney]

WIth @erezrokah and previously @erquhart having left Netlify, progress seems to have halted here. Does Netlify have a plan for moving forward? Who is reviewing pull requests?

edit: see https://github.com/netlify/netlify-cms/graphs/code-frequency

[erezrokah]

Thanks for opening the discussion @bmackinney, tagging @krider2010

[bmackinney]

No plan, no one is reviewing. It's time for a fork.

[talves]

Moving this here for reference: https://answers.netlify.com/t/is-this-project-dead/70988

@bmackinney thanks for asking the question.

[CamilleScholtz]

Considering there is no real answer, it might indeed be time for a fork. Problem is of course is that we need someone dedicated enough for this.

[leo-petrucci]

I really feel this. At its core Netlify CMS should've stayed simple for ease of maintenance:

• Create or update Markdown files
• Good editing experience
• Easy to customise editor

That's really all that was needed.

[CamilleScholtz]

Not to shill or anything (I don't have any connection to the project), but a new CMS called TinaCMS will soon support static sites made with Hugo and such: tinacms/tinacms#2215. Might be interesting for people that want to use something that is maintained.

[leo-petrucci]

Not to shill or anything (I don't have any connection to the project), but a new CMS called TinaCMS will soon support static sites made with Hugo and such: tinacms/tinacms#2215. Might be interesting for people that want to use something that is maintained.

I just checked this out, turns out if you want to use their editor in production you need to use their cloud solution. :/

[jimafisk]

Being a total shill for my own project, we've built an open source, git-backed CMS that does not require a cloud solution to run: https://github.com/plentico/plenti

Things to consider:

• It only supports a GitLab backed currently, although we'll add GitHub as soon as they support PCKE
• It's tightly integrated with our own Svelte-based SSG (it's all one repo), so it won't work with Hugo, Gatsby, etc.

I keep a video devlog if you want to see it in action without wasting time spinning things up, although that's pretty quick too :)

[jhvanderschee]

I have build something similar to what @jimafisk is saying, but it is closed-source and Hugo only. You can find it here:
https://cms.usecue.com.

[KaneFreeman]

As part of another project I started a fork to incorporate some changes I really wanted to see in the app. At first with the project I tried to use NetlifyCMS straight up but kept running into limiting factors for what I was trying to achieve.

• The markdown editor is very limiting (no table support 😢 )
• The editorial workflow was way more trouble then it was worth (I think I turned it off after just 15 minutes of having it on)
• Bundling into a TypeScript react had issues due to the published types not matching the underlying code
• Styling preview templates from your main app difficult due to the preview being in a frame (especially if you are using something like styled components).
• The dependencies of the app are getting rather out of date, making bundling them into a more modern app rather hard

All of this AND the severe lack of activity in this repo led me to start my own fork. I am planning on dedicating quite a lot of time to it as I go through the process of simplifying it (removing the editorial workflow for one) and modernizing it.

I would love to get input from anyone here on the direction I take. I am still working on some of the infrastructure pieces (which should be in place in the next week or so).

Repo: https://github.com/StaticJsCMS/static-cms
Roadmap: StaticJsCMS/static-cms#2
Discussion: StaticJsCMS/static-cms#4
NPM Package: https://www.npmjs.com/package/@staticcms/core
Docs: https://staticcms.org/

[martinjagodic]

Great news 😁 The project is not dead anymore! We are honoured to continue the path of Netlify CMS as Decap CMS.

Read more at Netlify blog or Decap blog

[jhvanderschee]

WOW that is really great news!!!!!

Some thoughts: https://www.usecue.com/blog/the-future-of-netlify-cms/

[craftzneko]

Was literally researching options to replace netlify CMS today and i see this news! Amazing 👍

[kyoshino]

Hi everyone 👋 The Decap news came as a surprise two weeks ago, but I thought my project was still worth sharing in this thread:

I have recently started rebuilding Netlify CMS from scratch and migrating my clients to the unofficial Svelte port to fix some UX and i18n issues. The resulting product basically materializes what Netlify CMS v3 would look like, such as a modern UI with dark mode, an all-new media library, stock photo integrations, custom collection icons, etc., while ensuring basic compatibility with Netlify CMS v2.

Check out Sveltia CMS today 👉 https://github.com/sveltia/sveltia-cms

It’s still early beta with no test coverage but open source. Hope some of you will like it!