8000 web3-storage/docs at dev · bolajahmad/web3-storage · GitHub
[go: up one dir, main page]

Skip to content

Latest commit

 

History

History
 
 

docs

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 

README.md

Documentation

docs/
├── getting-started/   — quickstart
├── design/            — canonical system design (review-gated)
├── site/              — architecture diagrams and dApp guide, derived from design/
└── drafts/            — unratified / WIP notes (need triage)
  • design/ — the source of truth; changes require design-owner review (see .github/CODEOWNERS).
  • drafts/ — unratified / WIP notes; treat as provisional. Each needs triage: promote to design/, fold into an existing doc, or drop.

API reference

There is no hand-written API reference. The rustdoc on the pallets is the reference, and because that text ships in the runtime metadata, every client surface shows the same words:

  • Rust — cargo doc --workspace --no-deps --open, or hover over the storage-subxt bindings in your IDE.
  • TypeScript — hover over the PAPI descriptors generated from packages/papi; the JSDoc is the pallet rustdoc.
  • Browser — polkadot.js Apps → Developer → Extrinsics shows the doc for each call, error, and event.

Every public pallet item must carry a doc comment; the missing_docs CI gate that enforces this lands with #403.

Getting started

  • Quick Start — three-terminal setup (chain → provider → demo).
  • CLAUDE.md (repo root) — agent/contributor rules and the source-of-truth map.
  • Contributing - setup, PR process, and /cmd bot usage (/cmd fmt, /cmd bench).

Design

The canonical system design. Changes require review (see .github/CODEOWNERS).

  • Scalable Web3 Storage — architecture, economic model, comparisons with Filecoin/IPFS/Arweave, rebuttals to common review concerns.
  • Implementation Details — pallet extrinsics, provider HTTP API, MMR layout, challenge mechanism, replica sync.

Site

site/ — architecture and workflow diagrams for web3-storage developers, and a guide for dApp developers. Every page is derived from design/; when design/ changes, update the site in the same PR (/generate-docs skill, checked in CI by scripts/check-docs-site.sh).

Drafts

Unratified / WIP notes. These need triage (#308) — each should be reviewed and either promoted into design/ (design-of-record), folded into an existing doc, or dropped.

Clients

  • Storage Client SDK — Layer-0 Rust client.
  • File System Client — Layer-1 drives, directories, and files.
  • S3 Interface — Layer-1 S3-compatible Rust client.
  • TypeScript SDK — @web3-storage/sdk at packages/sdk (./fs, ./s3, ./revive subpaths).

External

License

See the repository root README.

0