ESP32-S3 Bench Guide
ESP32-S3 N16R8 bench guide: live pinout, lessons, simulators and the bench log.
翻译准备中
尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证制作者的介绍仅有上面的一句话。 更多详情请阅读仓库 README。 仓库 README ↗
正在加载完整 README。
查看完整 README ↗A MkDocs site (Material theme) that gathers all .md files
from two locations and publishes them as one searchable website:
| Section in site | Source folder |
|---|---|
GENAI-AGENTICAI | Set via the GENAI_SOURCE_ROOT environment variable (defaults to ~/GENAI-AGENTICAI) |
Personal-SourceCode | C:\Dev\SoureceCode\Personal |
The source files are not edited. sync_docs.py copies them into docs/ and
builds an auto-generated landing page (docs/index.md) with links to every document.
You write these pages by hand — they live in content/ and are copied verbatim
into docs/ on every sync (never overwritten by the auto-sync):
content/
Technologies/ Snowflake, AWS, Databricks
GenAI-Topics/ Prompt Engineering, RAG, LangChain, LangGraph,
MCP, Bedrock, AgentCore, Graph DB
To add content to an area, just edit or add .md files in the matching folder,
e.g. content/Technologies/snowflake/warehouses.md, then run
python sync_docs.py. New pages appear in the nav automatically. Set a nav icon
on a page with YAML front matter at the top:
---
icon: material/snowflake
---
Course modules are auto-linked into the matching GenAI topic (e.g. MODULE5-RAG shows up as a "Related course module" callout on the RAG page).
sync_docs.py copies the openable files from each extracted module into
docs/Course-Modules/files/<module>/ and links them on the module page:
nbconvert) and
open as rendered pages. A few notebooks with incompatible metadata may fail
to convert — they're still listed, just without a link.Because these files are copied in, the built site/ is large (~470 MB). That's
expected. use_directory_urls: false is set so the file links resolve cleanly.
Packages are already installed. If you ever need to reinstall (note the corporate SSL trusted-host flags):
python -m pip install --trusted-host pypi.org --trusted-host files.pythonhosted.org -r requirements.txt
Build the full static site (fast — heavy module files are copied separately and
incrementally, so mkdocs build only renders the markdown in a few seconds):
python sync_docs.py # prep docs/ from sources + authored content
python -m mkdocs build --clean # render markdown pages (fast; excludes big files)
python finalize_site.py # incrementally copy module PDFs/notebooks into site/
Or as a one-liner:
python sync_docs.py; python -m mkdocs build --clean; python finalize_site.py
For live editing, python -m mkdocs serve (http://127.0.0.1:8000) builds
in-memory instantly — best for iterating on content/CSS.
Why the 3 steps? The course-module files (PDFs, rendered notebooks, diagrams ~470 MB) are excluded from the mkdocs build (
exclude_docsin mkdocs.yml) and copied intosite/byfinalize_site.py, which skips files that are already there. This keeps builds fast and avoids re-copying 470 MB every time. The firstfinalize_site.pyrun copies everything; later runs are near-instant.
Re-run these any time you add or change markdown, then refresh the browser.
Edit the SOURCE_ROOTS list near the top of sync_docs.py:
SOURCE_ROOTS = [
("GENAI-AGENTICAI", Path(r"C:\...\GENAI-AGENTICAI")),
("Personal-SourceCode", Path(r"C:\Dev\SoureceCode\Personal")),
("My-New-Section", Path(r"C:\path\to\folder")), # <- add here
]
docs/ and site/ are regenerated; treat them as build output.docs/.