Project code
Readable source files, mode logic, signal processing notes, and version history.
Archive being organizedResources
Open learning, not hidden process.
Useful engineering work includes the files, references, decisions, and failures that allow another student to understand what happened.
07 / TEIOpen-source spirit
Resources will be published when they are clearly named, safely documented, and useful without private explanation.
Resource library
Files that help the next student begin.
CAD files
Enclosure assemblies, component layouts, mounting studies, and export formats.
Archive being organizedBuild notes
Informal wiring reminders, development decisions, and debugging records.
Documentation in progressResearch notes
Sensor references, design constraints, test questions, and source lists.
Documentation in progressLearning paths
Suggested starting points for CAD, microcontrollers, electronics, and prototyping.
Collection in progressProject templates
Problem framing, test plans, reflection prompts, and case-study structures.
Collection in progressPublishing standard
Useful, honest, and safe to follow.
Code should identify its hardware assumptions. CAD files should name components and revisions. Build notes should separate confirmed connections from experiments. Research notes should link to their sources.
Projects involving tools, power systems, or body-connected sensors should also state supervision and safety requirements clearly.
Want to contribute?
Good documentation is engineering work.
Students can help organize files, test instructions, improve diagrams, and make technical knowledge easier to use.
Join the resource team ↗