IPFS is not a blockchain
Understand what a CID identifies, how pinning keeps content available, and which editorial features IPFS does not provide.
JOURNAL / TAG / 4 ARTICLES
Decentralized Storage
A focused reading path through the publishing stack.
This reading path brings together articles on the different responsibilities of content addressing, retained availability, and retrieval. Use the collection to follow the same idea across introductory explanations, operating decisions, and practical publishing examples. The articles are grouped by subject rather than by a product recommendation. Begin with the topic guide for the main definitions, then compare the related workflows below. As you read, identify what is being stored, what is being verified, and who remains responsible for corrections and recovery. Those questions make the technical vocabulary useful to a real publication.
The related topic guide
Know the limits of blockchain CMS
A failure-first review of recurring costs, correction problems, public metadata, gateway dependencies, and realistic recovery planning.
Decentralize the publishing stack
Follow a content revision from private draft to stored payload, on-chain record, rebuildable index, and reader-facing page.
Arweave vs IPFS for publishing
Choose storage around your retention policy, correction workflow, delivery needs, and operating budget—not a promise of effortless permanence.