How dfinity/icp-hello-world-motoko works
Main Components
a. Developer Environment
• IDE (VS Code, Gitpod, Codespaces with DevContainer)
• DFX CLI & Local ICP Sandbox (dfx start / dfx start --background)
• Build / Deploy Scripts (package.json scripts, scripts/canister_urls.py)
b. Backend Canister
• Motoko code (src/backend/main.mo)
• Integration Tests (src/backend/tests/integration_tests.py)
c. Frontend Canister
• Static assets & client code (src/frontend/index.html, index.js, main.css)
• Vite dev server (npm run dev, vite.config.js)
d. User / Browser
• Interacts with frontend via HTTP
• Frontend calls backend via Internet Computer Agent
e. External / Cloud
• Internet Computer Network (when deployed remotely)
Relationships & Data Flows
a. Developer → DFX CLI
• Triggers dfx start, dfx deploy, dfx build, dfx canister create
• Runs integration tests (Python script invokes HTTP calls to canister endpoints)
b. DFX Local Sandbox → Canisters
• Hosts both frontend and backend canisters locally
• Exposes canister URLs (also retrieved via scripts/canister_urls.py)
c. Browser → Frontend Canister
• Requests assets either from local Vite server (dev mode) or frontend canister
d. Frontend → Backend
• Uses agent/browser HTTP requests to call Motoko backend methods
e. Frontend Hot-Reload (Vite)
• Developer edits frontend → Vite rebuilds → Browser reloads
Architectural Patterns & Design Principles
• Full-stack separation: frontend canister vs backend canister
• Micro-canister architecture: each canister is an independent unit
• Local sandbox for rapid iteration, plus optional remote deployment
• Testability: integration tests decoupled via HTTP/agent layer
• DevContainer / Gitpod for reproducible environment
Technologies, Frameworks & Libraries
• Motoko & DFX SDK for backend canister development
• Vite + vanilla JS + CSS for frontend canister & dev server
• Python for integration tests and canister URL retrieval
• Docker / DevContainer definitions for consistent local environment