How IoTClass Works
Start Here
A two-minute orientation before you pick a module: what this platform actually is, how to choose your first stop, how the reading depth system works, and where to go when something doesn't click.
Sammy your guide, not a professor
“I felt exactly the way you might feel right now the first time I saw this site — nine module groups, dozens of tools, more chapters than one person reads in a year. This page is the short version: what everything is, and where to click first.”
I'm not a protocol expert — I just ask the questions you're probably asking too. When a page needs real technical authority, you'll meet a specialist like Shield Shelly or Gateway Gus along the way.
What IoTClass Actually Is
IoTClass.org teaches Internet of Things systems end to end: electronics and sensors, networking and protocols, cloud and edge computing, security, data, human factors, and real engineering practice. It's organized into 9 module groups covering roughly 40 modules and well over a thousand chapters — but you're never expected to read it front to back.
Every chapter carries short knowledge checks built in, and the platform layers on interactive simulators, hands-on labs, books, and kits so ideas get tested against real behavior, not just read once. Everything ties back to one map of concepts and prerequisites, so wherever you start, you can always see what feeds into what.
Pick Your First Module
There's no single correct entry point. Four common starting positions:
Every one of these routes rejoins the same nine-module curriculum eventually. The Modules & Learning Paths guide covers all nine groups and five role-based paths in full if you want the detailed version.
Sammy says: if none of the four feels exactly right, that's normal — pick the closest match and switch later. Nobody gets this choice perfectly right on the first click, including me.
How Depth Levels Work
Most chapters are written in three layers you can move between freely:
You never have to read all three. Stop at Overview and move on, or drop straight into Under the Hood if that's the layer your problem actually lives in.
Where to Get Help
If an inline check comes back low, Quizzes & Checking Yourself explains what the score means and how to close the gap. If a simulator or lab isn't behaving the way you expect, When You're Stuck has a symptom-based decision tree plus command and error-code references. If you'd rather work through a real trade-off than read a straight lesson, Design Studio walks through one with worked numbers.