Learn it.
Question it.
Make it better.
EmbeddexAI is free and open source. The chapters, exercises and code live on GitHub, anyone can read them, and anyone can help make them better.

Small contributions count.
You do not need to write a whole chapter. Start with something you can check.
Reproduce the lesson
Run the commands in the documented environment. Keep your exact output and software versions.
Make one clear improvement
Fix a typo, explain an error, improve an accessible description, or add a tested hardware note.
Show how you checked it
Open an issue or a pull request with the problem, your change and the command or screenshot that verifies it.
Use, share and adapt
The intended approach: use it, share it and adapt it, with credit. If you share changes to the text, share them under the same licence.
Your first contribution
- Fix a typo: open any page and choose “Edit this page on GitHub”. Change the text and submit it for review.
- Add an exercise: pick a track, write the task, the three hint levels and a check, and open a pull request.
- Report an issue: found a wrong command, a broken link or an unclear step? Choose “Report an issue” on the page.
Before you open a pull request
- Read the contributing guide in the repository before your first change.
- Keep changes small, one idea per pull request.
- Test commands and code on a board or in a VM, and say which one.
- Follow the style rules: plain language, sentence case, active voice.
- A maintainer reviews every change and may ask for edits.
Be kind and be specific. Everyone who contributes agrees to follow the code of conduct in the repository.
Repository, contributing-guide and code-of-conduct links will be connected when the public repository URL is supplied.
Questions about learning and sharing
Is EmbeddexAI really free?
Yes. Every tutorial and exercise is free to read and use, with no account and no paywall.
What licence does the content use?
Text is planned as CC BY-SA 4.0 and code as MIT. [Owner to confirm the licences before launch.]
Can I use the material in my own class or team training?
Once the owner confirms the licences, use the material with credit and under those terms. Link back to the page you used.
Can I share or translate a chapter?
Share the link now. Copying and adapting the text will follow the confirmed licence. Translations are welcome as pull requests.
How do I fix a mistake I found?
Choose 'Edit this page on GitHub' on that page, make the change and submit it. If you are unsure, choose 'Report an issue' instead.
Do I need to be an expert to contribute?
No. Typo fixes, clearer wording and tested commands on your own board are all useful.
How do I get help when I am stuck?
Ask in the discussions on GitHub. Say which board or VM you use and paste the exact output.
What hardware do I need?
A Raspberry Pi covers the Linux labs. Track-specific boards, such as an STM32MP157 for embedded Linux or a Jetson for GPU work, are recommended and listed per module. Much of the work also runs in QEMU.
The people behind the work
Your first contribution belongs here.
Contributor names will be added from verified contributions. No sample profiles or testimonials.
How to contributeYour browser, your progress
Path preferences, theme, recent searches, lesson progress and exercise notes are stored only in this browser. No account, ads or tracking scripts are included. Notes are not sent to a server.
Shared computers share browser storage. You can download your notes and then clear your saved learning data here. Theme preference is kept.
Newsletter privacy
The newsletter is not connected in this preview and no email addresses are collected.