Different flavors of content management

1

WordPress

The most typical approach is having a CMS admin panel sit somewhere on the server; everyone with an account uses this. This is a very convenient approach, especially when working with a team. This way, many people can work on different articles simultaneously without worrying about potential conflicts or overwriting stuff. The only con is related to security - everyone can try to get inside, and if you forget to update our CMS or some user have a weak password, it can be someone outside of our team. WordPress, Drupal, CraftCMS, or Ghost are perfect examples of such CMSs.

#CMS #Blogging #Blogging Platform 764 social mentions

2

Webflow

Webflow, Storyblok, and ButterCMS are great examples of SaaS CMSs.

#Website Builder #CMS #Website Design 131 social mentions

3

Strapi

A headless one is responsible only for data management and providing an API for other applications to show this data. When talking about headless CMS, Strapi or Sanity comes to my mind first, but there are many more.

#CMS #Blogging #Blogging Platform 310 social mentions

4

Statamic

Local CMSs are the ones that are mostly file-based (like Statamic or Astro). This means that you can edit everything locally and deploy the data. This way, our CMS is more secure, but on the downside, you have to have a local server working, and you might experience more conflicts, especially when two people will work on the same article (although Git might save you from many of those). It also means that there is a higher learning curve. A remote CMS works somewhere on a server, and most users don't care how.

#CMS #Blogging #Blogging Platform 48 social mentions

5

Ghost

The most typical approach is having a CMS admin panel sit somewhere on the server; everyone with an account uses this. This is a very convenient approach, especially when working with a team. This way, many people can work on different articles simultaneously without worrying about potential conflicts or overwriting stuff. The only con is related to security - everyone can try to get inside, and if you forget to update our CMS or some user have a weak password, it can be someone outside of our team. WordPress, Drupal, CraftCMS, or Ghost are perfect examples of such CMSs.

#Blogging #CMS #Blogging Platform 173 social mentions

6

Front Matter

But, when your CMS is based on Markdown files, you can use whatever editor you want. For example, if you use Nuxt as your CMS, everyone can choose which editor they prefer. It can be Visual Studio Code, FrontMatter CMS, or maybe Nuxt Studio. Everyone can pick the app they like the most.

#CMS #Content Management System #Static Websites 11 social mentions

7

Craft CMS

The most typical approach is having a CMS admin panel sit somewhere on the server; everyone with an account uses this. This is a very convenient approach, especially when working with a team. This way, many people can work on different articles simultaneously without worrying about potential conflicts or overwriting stuff. The only con is related to security - everyone can try to get inside, and if you forget to update our CMS or some user have a weak password, it can be someone outside of our team. WordPress, Drupal, CraftCMS, or Ghost are perfect examples of such CMSs.

#CMS #Blogging Platform #Blogging 31 social mentions

8

Cloud Cannon

Solutions like CloudCanon or TinaCMS use this approach.

#CMS #Blogging #Social & Communications 23 social mentions

9

Butter CMS

Webflow, Storyblok, and ButterCMS are great examples of SaaS CMSs.

#CMS #Blogging #Blogging Platform 9 social mentions

10

Builder.io

Webflow and Builder.io are perfect examples here.

#Website Builder #Website Design #Web Development Tools 36 social mentions

11

Astro Build

Local CMSs are the ones that are mostly file-based (like Statamic or Astro). This means that you can edit everything locally and deploy the data. This way, our CMS is more secure, but on the downside, you have to have a local server working, and you might experience more conflicts, especially when two people will work on the same article (although Git might save you from many of those). It also means that there is a higher learning curve. A remote CMS works somewhere on a server, and most users don't care how.

#Website Builder #Blogging #Blogging Platform 177 social mentions