Web3 industry insiders are very much aware of their rights about the data and content they generate for likes of Apple, Google, Facebook, Amazon, etc. DAO's having web content management systems (CMS) need to ready themselves for this emerging decentralized world. Using Decentralised Technologies like IPFS, Blockchain along with existing CMS technologies, one can (try to) craft a new architecture called 'decentralized CMS' (DCMS).
The diagram below depicts the architectural evolution journey ...
Decentralized CMS: De-centralization does not mean a lack of control. It only means that no single entity controls the content. The decentralized world allows and enables a plethora of partners, users, enterprises to collaborate where control and trust are decentralized. The need for a decentralized CMS is our takeaway.
Why Ghost on IPFS
My intention is to create an online magazine and source of content that is not hosted on a traditional service provider like AWS. Let's try to provide a proof of concept to have a censorship-resistant source of content.
- Gatsby: A React-based open-source framework for creating websites and apps. Gatsby is a static site generator that generates HTML during a build process. Gatsby loads JSON from GraphQL and merges that data with page templates. The pages are then deployed to a web server. In this case, the site is built and deployed to IPFS. Removing the need for server-side rending and delivering pre-compiled static sources removes a layer of dependence and eliminates the need for a back end server or service.
- IPFS: The InterPlanetary File System (IPFS) is a peer-to-peer network for storing and sharing data in a distributed network. IPFS uses content addressing and a unique hash to identify and access the content. I am using Fleek to build and deploy the site. With IPFS I am able to remove any dependence on third-party providers. Fleek is a very convenient way to build and deploy but not required to publish content.
- Markdown: Markdown is a markup language for creating formatted text using a plain-text editor. Instead of using a CMS (content management system) like Ghost, let's try to use Markdown. The motive was to remove any dependence on services I have no control over but I would still love to explore options like WordPress or Ghost as a headless CMS. With markdown, my content is maintained with the source code and statically built during deployment.
What is the best place to start to explore this challenge? We started with creating and publish flaring fast blogs with this Jamify blogging system. Powered by the React framework Next.js and content fed by headless Ghost, you'll get a production-ready hybrid static & server-rendered website that you can easily distribute globally. At the same time, we hope content creators can continue to work with the Ghost authoring system they are used to, and not deal with a markdown context if possible ...
The first goal is to add the capability to log in with cryptocurrency wallets such as MetaMask for Ethereum. Adds a button to a login screen that will let users securely log in with their crypto wallet.
A widget library for React for creating and viewing token-protected content.
@unstoppableweb and @IPFS - anyone have any good guides on how to migrate from web2 to web3 without losing your mind?
The biggest thing about NFTs I've found is that it's pretty versatile in how you want to use it so if you want to sell blogposts it's essentially like posting it onto a website-like medium and getting readership based on it as well as charging a fee. I guess you could use it similarly to how NYT has subscription fees to read articles and the more people resell it, you get a portion of royalties that are based on how much the percentage you dictated in the original NFT is. Maybe a collection of short stories or multiple chapters? So maybe single one-off blogs or multiple blogs sold as a collection? Idk but the possibilities are limitless.