Skip to content

docs: developer onboarding pass for all entry-point READMEs - #1466

Open
marc0olo wants to merge 2 commits into
masterfrom
docs/onboarding-entrypoint-readmes
Open

docs: developer onboarding pass for all entry-point READMEs#1466
marc0olo wants to merge 2 commits into
masterfrom
docs/onboarding-entrypoint-readmes

Conversation

@marc0olo

Copy link
Copy Markdown
Member

Every category directory now has a real entry point for newcomers. Before this PR: motoko/README.md was three lines with a dead security URL, hosting/README.md listed 3 of 6 examples via absolute GitHub URLs, and rust/, native-apps/, wasm/ had no README at all.

Root README

Category entry points

motoko/ and hosting/ rewritten; rust/, native-apps/, wasm/ created. Consistent shape: what the directory is → start-here path → categorized index (every example, one-line description, relative links) → security-best-practices footer. Categories: getting started / full-stack apps / tokens & payments / chain fusion & signing / HTTPS outcalls / inter-canister patterns / system features / compute & AI / vetKeys.

vetkeys indexes

  • motoko/vetkeys/README.md created (there was none).
  • rust/vetkeys/README.md rewritten: it previously linked only to the upstream dfinity/vetkeys repo (one under a name that doesn't match the local directory), steering readers away from the code next to it.

Link conventions

  • Internet Identity: docs guide (docs.internetcomputer.org/guides/authentication/internet-identity) in integration contexts; id.ai kept only for live-instance references (ic-pos mainnet section, unity deep-link endpoint). Applied to root, ic-pos, unity_ii_deeplink, and the new entry points.
  • All external links verified against the current docs site (several old paths only survive via redirects); all relative links checked to resolve.

🤖 Generated with Claude Code

marc0olo and others added 2 commits July 30, 2026 15:20
Every category directory now has a proper entry point focused on getting
a newcomer from zero to a running example:

- Root README: contribution invitation removed (repo is not soliciting
  external PRs while examples are restructured for the developer docs),
  'New here?' path rewritten with language-labeled links (hello_world →
  who_am_i), wasm/ listed alongside the other categories.
- motoko/ and hosting/ READMEs rewritten; rust/, native-apps/, and wasm/
  READMEs created: each opens with a start-here path, then a categorized
  index of every example with a one-line description and relative links,
  and closes with the canonical security-best-practices link.
- vetkeys indexes: motoko/vetkeys/README.md created; rust/vetkeys/README.md
  rewritten to link the local examples instead of the upstream vetkeys
  repository (which it pointed at exclusively, under partly wrong names).
- Link conventions applied throughout: Internet Identity mentions link the
  developer docs guide in integration contexts (id.ai stays only for
  live-instance references, e.g. ic-pos mainnet notes); all external links
  verified against the current docs site; all relative links checked.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… canister

The hosting examples run on the @dfinity/static-site recipe
(certified-assets canister), which replaces the legacy asset canister
going forward. Name both, state the direction, and mark photo-storage as
the deliberate legacy exception (AssetManager uploads).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Improves developer onboarding by adding and standardizing entry-point READMEs across the repository’s top-level example categories, ensuring newcomers have consistent “start here” guidance and complete indexes with verified links.

Changes:

  • Updated the root README.md “New here?” path and expanded category directory listing (including wasm/).
  • Added new entry-point READMEs for previously undocumented categories (rust/, native-apps/, wasm/) and rewrote existing category READMEs (motoko/, hosting/) into a consistent structure.
  • Added/rewrote vetKeys index READMEs so the repo’s local vetKeys examples are discoverable and cross-linked between Motoko and Rust.

Reviewed changes

Copilot reviewed 10 out of 10 changed files in this pull request and generated 1 comment.

Show a summary per file
File Description
README.md Refines the newcomer path and updates top-level category navigation (adds wasm/).
hosting/README.md Replaces outdated/partial index with a complete, structured hosting category entry point.
motoko/README.md Expands Motoko category entry point with a guided start path and full categorized index.
motoko/ic-pos/README.md Updates Internet Identity link to the current docs guide.
motoko/vetkeys/README.md Adds a Motoko vetKeys index with cross-links and categorized example list.
native-apps/README.md Creates a native-apps entry point with a short index and consistent security footer.
native-apps/unity_ii_deeplink/README.md Updates Internet Identity link to the current docs guide.
rust/README.md Creates a Rust category entry point with start-here guidance and categorized index.
rust/vetkeys/README.md Rewrites vetKeys index to point to local examples (and Motoko counterparts) instead of upstream-only links.
wasm/README.md Creates a wasm category entry point describing low-level canister examples and indexing counter/.
Comments suppressed due to low confidence (1)

hosting/README.md:15

  • This parenthetical says photo-storage runs on the legacy asset canister, but hosting/photo-storage/icp.yaml uses the @dfinity/static-site recipe. The description here should match the repo’s actual configuration.
- [`photo-storage`](photo-storage/) — store and manage photos programmatically with `AssetManager` from `@icp-sdk/canisters/assets` (runs on the legacy asset canister).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread hosting/README.md
@marc0olo
marc0olo marked this pull request as ready for review July 30, 2026 13:52
@marc0olo
marc0olo requested review from a team as code owners July 30, 2026 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants