Architecture Overview
Project Categories
Hardware Projects
Philosophy: Minimal design, open source electronics
esp32_minimal/
- ESP32 dev board with minimal componentsrp2040_minimal/
- RP2040 dev board with minimal componentsgame-console/
- Handheld gaming device based on RP2040allwinner-h3_minimal/
- ARM Cortex-A7 Linux boardpico_st7789/
- Display breakout boardtars/
- Custom hardware projectrockchip-rk3399_minimal/
- ARM64 Linux board
Stack: KiCad for PCB design, minimal BOM approach
Web Projects
Philosophy: Serverless-first, TypeScript, minimal dependencies
mayphus.org/
- Personal website/blog (Astro + org-mode content)agents/
- AI agent platformvocabvibe/
- Vocabulary learning apptravel-tango/
- Travel planning with AIslidesnap/
- Slide generation tooltangmeifa.com/
- Chinese learning platform
Stack: Cloudflare Workers, TypeScript, React/Astro, Tailwind CSS
Tooling & MCP
Purpose: Extend LLM capabilities, automate workflows
emacs-mcp-server/
- Emacs integration for MCPllm-mcp-server/
- General LLM tooling
Stack: Python, Node.js, MCP protocol
Infrastructure
Purpose: Server deployment, networking, containerization
infrastructures/
- FreeBSD, Linux configs, proxy setups
Stack: FreeBSD, Linux, LXD, Docker, networking tools
Content & CAD
notes/
- Personal knowledge base using org-mode, publishes to mayphus.orgCADs/
- FreeCAD mechanical designs
System Connections
Hardware Projects → Firmware → Web Interface
↓ ↓ ↓
PCB Files Embedded C Cloudflare Workers
↓ ↓ ↓
Manufacturing MCU Flash Global CDN
Integration Patterns
Hardware ↔ Web:
- ESP32/RP2040 → HTTP/WebSocket → Cloudflare Workers
- Real-time sensor data streaming
- Web-based device configuration
Content Flow:
- notes/ → mayphus.org/ → Cloudflare Pages
- Automated content sync via org-mode
Development Tools:
- MCP servers bridge LLM ↔ Development environment
- Emacs as primary development interface
Design Principles
- Minimal Complexity: Favor simple solutions over feature-rich ones
- Open Source: All projects use open toolchains and formats
- Serverless-First: Web projects deploy to edge computing
- Documentation as Code: Content lives in version control
- Cross-Platform: Hardware designs work across environments
Dependencies
Shared Libraries
- TypeScript across all web projects
- Tailwind CSS for styling
- Cloudflare Workers runtime
Tool Dependencies
- KiCad for hardware design
- FreeCAD for mechanical design
- Emacs + org-mode for content creation
- Git for version control across all projects
Deployment Architecture
Hardware: KiCad → Gerber Files → PCB Manufacturing
Web: Git Push → Cloudflare Workers → Global Edge
Content: notes/ → Astro build → Cloudflare Pages
Infrastructure: Config files → FreeBSD/Linux deployment