User story / Problem statement
docs.dappbooster.cc still documents how to clone and run this monorepo (pnpm i, dev-stack, LocalNet, DAR deploy). It never shows how to install the kit from npm and use it in your own dApp, even though the three libraries now ship on npm (@bootnodedev/canton-connect, canton-dappbooster, canton-theme).
Expected outcome
A developer landing on docs.dappbooster.cc sees how to add the kit to their own project — install the packages from npm and connect a wallet — not only how to run this repo. The contributor setup stays, but it is no longer the first thing you read.
Acceptance criteria
Additional context
M1 deliverable: documentation. Pairs with #206 (llms.txt) and BootNodeDev/dappbooster-canton-landing#14 (landing). Packages went to npm in #204.
User story / Problem statement
docs.dappbooster.cc still documents how to clone and run this monorepo (
pnpm i, dev-stack, LocalNet, DAR deploy). It never shows how to install the kit from npm and use it in your own dApp, even though the three libraries now ship on npm (@bootnodedev/canton-connect,canton-dappbooster,canton-theme).Expected outcome
A developer landing on docs.dappbooster.cc sees how to add the kit to their own project — install the packages from npm and connect a wallet — not only how to run this repo. The contributor setup stays, but it is no longer the first thing you read.
Acceptance criteria
@bootnodedev/canton-connect,canton-dappboosterandcanton-themefrom npmAdditional context
M1 deliverable: documentation. Pairs with #206 (llms.txt) and BootNodeDev/dappbooster-canton-landing#14 (landing). Packages went to npm in #204.