2. Why decentralized

In the last article I explained the CMS and how it works. But I haven't answered the main question: why does this product exist.

There are several very good CMS already. I love Contentful - it is a great and powerful product that has even more sample clients and years of the development behind. A very mature solution for a lot of companies. There is also Hygraph, that would work better if you need more data-oriented publishing. So why I am building another product in this crowded space?

Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety.

There's a reason a quote from Benjamin Franklin is included here. With any other CMS, what you create is owned by the CMS (the same applies to blogs). Your content is typically stored on a server cloud database in a proprietary format, meaning you don't actually own your articles. It is all provided as a service to you. The issue isn't necessarily that every service has a cost. The problem is that every service is just a phone call away from being suspended. Some of you may have heard of the "Tornadogate," where a generic and useful service was shut down by the US Treasury for allegedly sending money to North Korea. To me, this is akin to banning email because it is sometimes used for scams. While I understand that this is not a straightforward issue, it highlights the dangers of relying on centralized services.

I'm not suggesting that the government will shut down your website or blog tomorrow. Rather, I am advocating for using technology to truly own the content you are publishing. With Blockenberg, you can publish using your own credentials on a globally distributed storage network, all at a fraction of the cost compared to using a traditional CMS (which I am currently covering for you). The data (articles, pictures and everything else) stay yours and the client application (like the blog you are reading) is accessing this data completely independently.

I'll explain the technical details and the data flow in the next article. Stay tuned.