ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
A focused, adaptive way to learn world geography through flags, locations, outlines, and land-border neighbours.
Translation pending
EducationTypeScript · JavaScriptGitHub @BenWassaOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
Atlas is a mobile-first geography-learning PWA across Flags, Locations, Outlines and Neighbours.
Atlas teaches world geography through direct retrieval, geographic context and deliberately scarce mastery/completion. The production navigation is Spatial Atlas: after choosing a learning domain, the learner uses a persistent interactive Earth to select a continent or region, then deliberately starts Play or Learn for that scope.
Spatial Atlas is the accepted product direction, not a preview. The conventional launcher is retained only as the equivalent fallback when WebGL cannot start.Read the full README ↗Atlas is a mobile-first geography-learning PWA across Flags, Locations, Outlines and Neighbours.
Atlas teaches world geography through direct retrieval, geographic context and deliberately scarce mastery/completion. The production navigation is Spatial Atlas: after choosing a learning domain, the learner uses a persistent interactive Earth to select a continent or region, then deliberately starts Play or Learn for that scope.
Spatial Atlas is the accepted product direction, not a preview. The conventional launcher is retained only as the equivalent fallback when WebGL cannot start.
Current production coverage:
The learner-facing product language is modern British English (en-GB). User-facing copy uses Neighbours and Play. Stable compatibility identifiers remain unchanged where migration would add risk: the route is /neighbors, Play remains internal test, and existing flag-atlas:* storage/cache namespaces remain.
Read these in order before changing product behaviour:
PRODUCT.md — current product contract.DESIGN.md and .impeccable/design.json — current visual/interaction system.docs/architecture/spatial-atlas.md — production Spatial Atlas architecture.docs/architecture/routing.md — typed URL/history contract.docs/index.md — documentation map.docs/open/index.md — genuinely open work and sequencing.docs/history.md — historical issue lineage and supersession map.Closed GitHub issues and docs/closed/ records are intentionally retained as decision/evidence history. Old feature, spike and agent branches are not project history and should be deleted once their useful work is merged, superseded or captured.
Requires Node 22.12+.
npm install
npm run dev
The Vite development server uses an isolated development progress sandbox and does not write learner production state.
Build and verify:
npm run build
npm test
npm test is the primary repository gate: strict checking, React/component coverage, production Vite/PWA build and the complete invariant verifier chain. Browser matrices run separately where required by an issue.
The deployable static application is written to dist/.
src/data curriculum + generated canonical geography
src/domain pure learning/evidence/scoring/achievement rules
src/infrastructure persistence + asset/cloud adapters
src/routing typed routes + hash-router transport
src/state application/session orchestration
src/react production React shell and domain activities
src/spatial production Spatial Atlas presentation
src/ui framework-independent map/UI adapters
src/main.tsx browser entry
src/sw.ts Workbox service-worker policy
The spatial layer interprets authoritative routes; it does not own a second navigation state machine. Geography taps and equivalent DOM controls dispatch the same application actions. Domain-native activities retain their own primary learning surfaces rather than being forced into 3D.
Accepted main is built and deployed to GitHub Pages, the primary production host, and to Firebase Hosting as the secondary live target. Preserve the existing local-first progress/cloud-sync contracts and PWA/offline behaviour when changing unrelated product areas.