Blockchain CMS.
Content with
a record.

A blockchain CMS is a content-management approach that uses a blockchain for selected integrity records, permissions, provenance, or publication history. Large content payloads usually remain off-chain. It still needs an editor, storage, and reader-facing delivery.

It distributes selected responsibilities across authoring, storage, publication authority, indexes, and delivery. The important questions are who can update the content, who retains it, and how another operator can reconstruct the accepted history.

Neither. IPFS is a content-addressed peer-to-peer system for organizing and transferring data. A CMS can use it for public files, but must add editing, approval, version management, and an explicit retention arrangement.

Small content can be stored on some chains, but putting an entire dynamic website on a general-purpose blockchain is usually impractical. Typical designs keep files elsewhere and record selected hashes, pointers, permissions, or metadata on-chain.

A traditional CMS centers on editing, organizing, and delivering content. A blockchain-related layer can add independently checkable publication records or shared authority. A hybrid can preserve WordPress or a headless editor while adding a narrow integrity feature.

Costs, key management, corrections, privacy, retained availability, and gateway dependencies all need attention. Immutability does not verify truth, guarantee file availability, or remove every point where access can be disrupted.