Rebrand from Netlify CMS to Decap (#6710)

* rename Netlify CMS to Decap CMS * replace netlify-cms with decap-cms * replace Slack with Discord * hide updates section because it's outdated * remove Twitter links * update community page - remove priority issues link - remove netlify forum link - update stackoverflow tag * replace netlifycms.org domain with decapcms.org * change logo and favicon * update color schemes * add blog post about decap and remove old entries * update redirects * add maintained by to footer * remove services from readme * add moving to discord post * add og image
mrsnakeoil · Mar 6, 2023 · 68b41b7 · 68b41b7
1 parent d8d85a0
commit 68b41b7
Show file tree

Hide file tree

Showing 97 changed files with 480 additions and 1,249 deletions.
diff --git a/README.md b/README.md
@@ -1,6 +1,6 @@
-# Netlify CMS Website & Docs
+# Decap CMS Website & Docs
 
-This directory builds netlifycms.org. If you'd like to propose changes to the site or docs, you'll find the source files in here.
+This directory builds decapcms.org. If you'd like to propose changes to the site or docs, you'll find the source files in here.
 
 ## Local development
 

diff --git a/content/blog/deploy-preview-links.md b/content/blog/deploy-preview-links.md
diff --git a/content/blog/implementing-a-jekyll-cms-in-3-days.md b/content/blog/implementing-a-jekyll-cms-in-3-days.md
diff --git a/content/blog/introducing-decap.md b/content/blog/introducing-decap.md
@@ -0,0 +1,22 @@
+---
+title: Introducing Decap CMS
+description: >-
+  Decap CMS is a rebranded version of Netlify CMS, offering a simple, easy-to-use, open source, git-based CMS.
+date: 2023-02-23T10:30:00.000Z
+author: Martin Jagodic
+twitter_image: /img/preview-link-published.png
+canonical_url: https://techhub.p-m.si/insights/introducing-decap-cms
+---
+We are proud to introduce Decap CMS, the rebranded version of Netlify CMS. We took this step because we didn't like that this awesome project was slowly dying, and we wanted to ensure that it would continue to be supported and improved.
+
+We love Netlify CMS for multiple reasons. Its ease of configuration and how simple it is for editors to use. Additionally it ships with lots of features and is highly customisable. It is also an integral part of the great Jamstack and open source community.
+
+As the new maintainers of Decap CMS, our plan is to continue on the premise of a simple, easy-to-use, open source, git-based CMS. We are excited about the potential for this type of product and we strive that it remains a viable option for developers and editors alike.
+
+First we plan to solve deprecation issues, then we will evaluate what are the next chapters for Decap. In the mean time, we will appreciate any contributions in form of pull requests, issues and discussions on GitHub.
+
+We understand that there may be some growing pains as we transition to being the maintainers of this project, but please bear with us as we try to bring this project from the dead. We are excited to continue developing and improving Decap CMS with your help!
+
+We would like to thank Netlify for entrusting us with the Netlify CMS project. We are excited and grateful for this opportunity.
+
+Team of maintainers at [PM](https://techhub.p-m.si/)
diff --git a/content/blog/moving-to-discord.md b/content/blog/moving-to-discord.md
@@ -0,0 +1,20 @@
+---
+title: Moving to Discord
+description: >-
+  We are migrating our community chat from Slack to Discord
+date: 2023-03-01T10:30:00.000Z
+author: Martin Jagodic
+twitter_image: /img/preview-link-published.png
+---
+During the transition period, we will be active on both services, and Slack will remain open until it dies off. This decision was based on the fact that when we took over, the most requested feature on Slack was to migrate to Discord, and we were already considering it ourselves.
+
+Here is the [Discord invite link](https://discord.gg/KZRDXmTm9v).
+
+Slack is not ideal because messages disappear and invite links expire after 30 days. Additionally, it is a walled garden, where you need a separate account for each workspace. This is good for companies but bad for communities.
+
+Discord is a great alternative because messages stay forever, and the invite link does not expire. It is open to everyone and is therefore more accessible. A lot of open source communities rely on it, so it will be a familiar service for many.
+
+This solves community chat problem, but the problem of a public forum still remains. We are considering using Discourse because it is a great platform, and Netlify Answers' CMS subforum is already on Discourse. Hopefully this means that we could transfer all that knowledge to the new instance.
+
+If you have any suggestions on how to structure the Discord server, tell us on Discord 💬
+
diff --git a/...lify-cms-2-0-launches-with-bitbucket-support-and-a-new-monorepo-architecture.md b/...lify-cms-2-0-launches-with-bitbucket-support-and-a-new-monorepo-architecture.md
diff --git a/content/blog/netlify-cms-2-1-0-adds-external-media-support-with-uploadcare.md b/content/blog/netlify-cms-2-1-0-adds-external-media-support-with-uploadcare.md
diff --git a/content/blog/netlify-cms-2-4-0.md b/content/blog/netlify-cms-2-4-0.md