Primary documentation is the best place to inspect the specific behavior behind a publishing design. This reading list complements the topic guides with sources about content addressing, storage retention, web delivery, CMS integration, and provenance. The links are references, not partner endorsements or a list of services offered by BlockchainCMS.com.
Blockchain and off-chain storage
Ethereum: decentralized storage explains why large content payloads are usually kept outside Ethereum itself. Read it alongside the blockchain CMS overview when deciding which responsibility a ledger should actually handle.
Ethereum: blockchain data storage strategies distinguishes storage mechanisms and their different access and availability properties. Do not turn historical example prices into a permanent cost estimate for your publication.
IPFS identity, retention, and privacy
IPFS: content identifiers describes the relationship between content, representation, and CIDs. It is useful when designing reproducible releases or explaining why a CID is not a plain file checksum.
IPFS: persistence and pinning explains how content is retained and why a reference does not guarantee permanent availability. Use it to assign an operational owner to your publication's storage plan.
IPFS: privacy and encryption distinguishes encrypted transport from content confidentiality and discusses public network metadata. Review those boundaries before publishing sensitive material or describing an address as private.
Websites and naming
IPFS: custom domains and DNSLink separates signaling a CID from serving a site directly at an HTTPS domain. It supports the domain discussion in our static-site deployment walkthrough.
IPFS: multi-page websites introduces directory-based website publishing. Test nested pages and assets against the actual gateway URL model, not only a local homepage preview.
Arweave and archival intent
Arweave's project overview describes the network's permanent-information-storage objective. Compare that objective with your own retention and correction policy before choosing an archival destination. Our storage comparison focuses on the surrounding publishing decisions rather than provider rankings.
WordPress integration
WordPress: REST API handbook explains structured content access and separate application interfaces. It is a useful reference when keeping an established editor while changing public delivery.
WordPress: plugin hooks describes actions and filters. Read the relevant implementation documentation before building an integration, and test how a publishing extension handles drafts, retries, and failures.
Timestamping and provenance
OpenTimestamps explains timestamp-proof creation and verification. Preserve the original material, proof, and instructions together rather than relying only on a status shown in a third-party interface.
C2PA: Content Credentials explainer distinguishes provenance evidence from a determination that content is true and explains that Content Credentials do not require a blockchain. Compare the evidence model with the specific question your readers need to answer.