Skip to content

revisit docs.dappbooster.cc #207

Description

@pablofullana

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

  • Getting started shows installing @bootnodedev/canton-connect, canton-dappbooster and canton-theme from npm
  • The versions shown match what is published
  • "Use the kit in your dApp" and "Run this repo" are separate and clearly labelled
  • Any connect example imports the published packages, not workspace paths

Additional context

M1 deliverable: documentation. Pairs with #206 (llms.txt) and BootNodeDev/dappbooster-canton-landing#14 (landing). Packages went to npm in #204.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

enhancementNew feature or requestpriority: highMust be addressed in current sprint

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions