ESP32-S3 Bench Guide
ESP32‑S3 N16R8 벤치 가이드: 실시간 핀아웃, 강의, 시뮬레이터 및 벤치 로그
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기메이커가 쓴 소개는 위의 한 줄이 전부입니다. 더 자세한 내용은 저장소 README에서 읽을 수 있습니다. 저장소 README ↗
README 전체를 불러오는 중입니다.
README 전문 보기 ↗Skills-to-Work Platform: train, prove, connect, work.
Talentral gives training organisations one system to run cohort-based skills programmes, turns each learner's work into verified evidence of skill, and connects that verified talent to employers in Nigeria, across Africa and in the GCC. The flagship pilot is the Kirkira Innovation Hub iDICE Centre of Excellence in Katsina.
Name clearance. "Talentral" replaces the earlier name, which is registered with CAC by another party. It is subject to a CAC name search and a trademark search (classes 9, 35, 41, 42) before incorporation. See section A1.5 of the plan.
The repository holds the plan the MVP will be built from and the brand identity. Application code starts with Sprint 0 (plan section C22.1).
| Path | Contents |
|---|---|
docs/master-plan.md | The master plan in Markdown: the version to read and review on GitHub |
docs/Talentral_Master_Plan_v3.1.docx | The same plan as a Word document for sharing with partners |
docs/assets/ | Figures used by both versions |
docs/master-plan-source/ | The generator: one source that produces the .docx, the Markdown and the figures |
brand/ | Logo set (SVG, PNG, favicon), the PDF brand guide, design tokens and their generator |
| Part | Covers |
|---|---|
| A. Strategic Concept | Brand and company structure, customers, product suites, readiness model, Passport, GCC corridor, business model, go-to-market, governance, risks |
| B. MVP Definition | Release phasing, scope matrix, roles, journeys, epics with acceptance criteria, non-functional requirements, validation gates |
| C. Technical Implementation | Architecture decisions, system design, tenancy and RLS, data model, offline sync, credentials, matching, AI, APIs, security, UI foundations, CI/CD, sprint plan, budget |
| D. Action Plan | First 90 days, pilot journey, recommendation, naming registry, assumptions, glossary |
The mark is a person with open arms forming the T of Talentral, with the dot as the head. Its gradient runs from violet (learning) through blue (proof) to teal (work). Start with brand/README.md or the PDF guide.
Never edit docs/master-plan.md or the .docx by hand. Edit the files in docs/master-plan-source/ and rebuild:
cd docs/master-plan-source
npm install
npx playwright install chromium # once, to render the figures
npm run fonts # optional: downloads the Inter font for the figures
npm run build # figures, then .docx and Markdown
| File | Role |
|---|---|
brand.js | The brand and company name. Change it here and rebuild to rename everything, including the logo set |
meta.js | Document version and date |
front.js, partA.js to partD.js | Document content |
h.js | Layout helpers: each one writes the Word element and its Markdown twin |
diagrams.js | Renders the figures from HTML to PNG |
build.js | Assembles the Word document, pre-fills its Contents page and writes the Markdown |
preview.js | Renders the built .docx in Chromium for visual checks (node preview.js <section>) |
The brand assets rebuild from brand/source (see brand/README.md). Rebuild the brand first when the name changes, because the documents embed the logo.
Requirements: Node 22, pnpm 10 and PostgreSQL 15 or later (Supabase in production).
pnpm install
cp .env.example apps/web/.env.local # then adjust DATABASE_URL and PLATFORM_ADMIN_EMAILS
DATABASE_URL=... pnpm db:migrate # applies packages/db/migrations
DATABASE_URL=... [email protected] pnpm db:seed # add --demo for a sample hub
pnpm dev # http://localhost:3000
Sign in at /sign-in with a platform admin email (with MAIL_DRIVER=console the link is printed in the terminal), open /platform, create a hub and invite its owner. The owner completes the hub profile, creates a programme and opens applications. Hub pages are at /<hub> locally and <hub>.talentral.ng in production.
| Command | What it checks |
|---|---|
pnpm typecheck | TypeScript in every package |
pnpm test | Domain unit tests and the Row-Level Security suite (needs DATABASE_URL_TEST; the database is reset) |
pnpm --filter @talentral/web e2e | The full journey in a browser against a production build (needs E2E_DATABASE_URL) |
The code is organised as apps/web (Next.js), packages/db (migrations, RLS, data access) and packages/domain (pure logic). Decisions that refine the plan are recorded in docs/adr/.