I think longer term, we might want to split out the ESP32 Wireless stuff into its own sub-module like we do in our Intro to Arduino lessons where we have a sub-module on Output and Input. This gives us more breathing room and let's us focus the first ESP32 sub-module on "Intro/Basic" material before having our very own sub-module on one of the key things that makes the ESP32 unique (plus, I'd like to expand the wireless section on WiFi to show building a little custom server and not relying on Adafruit I/O, etc.).
Could be something like:
ESP32 (parent)
├── Fundamentals (sub-module, has_children: true)
│ ├── L1: Introduction to the ESP32
│ ├── L2: Blinking an LED
│ ├── L3: Fading an LED with PWM
│ ├── L4: Analog Input
│ ├── L5: Playing Tones
│ └── L6: Capacitive Touch Sensing
│
└── Wireless (sub-module, has_children: true)
├── L1: Internet of Things (WiFi)
├── L2: Bluetooth Serial
├── L3: Introduction to BLE
├── L4: Bidirectional BLE
└── (future: WiFi Web Server, ESP-NOW, BLE HID, ...)
I think longer term, we might want to split out the ESP32 Wireless stuff into its own sub-module like we do in our Intro to Arduino lessons where we have a sub-module on Output and Input. This gives us more breathing room and let's us focus the first ESP32 sub-module on "Intro/Basic" material before having our very own sub-module on one of the key things that makes the ESP32 unique (plus, I'd like to expand the wireless section on WiFi to show building a little custom server and not relying on Adafruit I/O, etc.).
Could be something like: