libdrone as proof¶
I documented the complete system before the hardware was finished.
That is not a confession. It is the point.
What the documentation stack is¶
libdrone.eu is a complete open hardware documentation system for a 6-inch modular drone platform. One person. Nights and weekends. The result:
- Variables file — single source of truth for all geometry, every value in one place
- Master Specification — complete system specification, near-aerospace standard
- Hardware document — every component, why it was chosen, where to source it
- Shopping list — sourcing guide with alternatives and cost notes
- FreeCAD Cookbook — step-by-step build guide for the CAD work
- Onshape Cookbook — reference and verification workflow
- Payload SDK — complete developer reference for the GX12-7 payload interface standard
- PRUSA Print Guide — print settings, material choices, quality notes
- CadQuery generator — 1,815-line parametric Python generator for all printed parts
The documentation is designed so that a competent stranger — someone who has never met me, never asked me a question — can reproduce the hardware entirely from the published files.
Why I built it this way¶
Because documentation written after the hardware is finished is almost always wrong.
When you document as you design, you find the errors. A measurement that cannot be expressed clearly in a specification is a measurement that has not been fully thought through. A process that cannot be written down is a process that is not yet understood. The documentation is not a record of the design — it is part of the design process.
The variables file discipline in particular: when every value lives in one place, you cannot contradict yourself. You are forced to be precise. The act of writing the number down once, correctly, and then referencing it everywhere else is the act of making a decision.
What it demonstrates¶
That one person with the right tools, the right discipline, and the right editorial instinct can produce documentation at a standard that most engineering teams do not achieve with a full team.
Not because AI is magic. Because architecture is the work, not word count. Because the single source of truth principle scales from a technology magazine to a hardware platform without changing. Because falling in love with the craft of documentation — the smell of a well-structured spec, the satisfaction of a variables file with no contradictions — is a real professional skill that produces real results.
One open gap¶
The "libdrone Pro" design is fully specified. The documentation exists. The payload interface is defined. What is missing is someone who can translate the specification into FreeCAD geometry.
If you work in FreeCAD and the idea of building the reference implementation of a fully documented open hardware drone platform interests you — get in touch.
The design files, the specification, and the variables file are all waiting. The CAD work is the unlock.