Hollow Architecture
Parametric Component Library — Open Reference
- CATEGORY
- Archive
- CLIENT
- OPEN REFERENCE
- ROLE
- Designer, Documenter
- DURATION
- ONGOING
Hollow Architecture is a library of parametric mechanical components maintained as open reference for designers and engineers who work in fictional product design. The core premise: speculative objects should have the same internal logic as real ones. A hinge should hinge. A latch should latch.
Every component is fully parametric — key dimensions exposed as named parameters so the part scales and adapts correctly when proportions change. Tolerance families are included for each interface: sliding, press, and transition fits all documented. Nothing is guessed.
The archive began as a personal tool — a library built from project need, retained for reuse. It became an open reference after requests from other designers who encountered it in work-in-progress material. The library grows with every project that requires a component not yet documented.
- COMPONENTS
- 140+ individual parts
- FAMILIES
- 8 (joints, latches, hinges, sliders, actuators, brackets, fasteners, closures)
- FILE FORMATS
- Fusion 360 native, STEP, IGES, STL
- PARAMETRIC
- Yes — all key dimensions exposed as parameters
- TOLERANCE SET
- H7/h6 sliding fit, H7/p6 press fit, H7/k6 transition
- LICENSE
- Creative Commons CC BY 4.0
- LAST UPDATE
- 2024-03
Audited 4 years of project files for recurring mechanical elements. Identified 8 functional families. Established naming and parameterization conventions before building the library proper.
Every component rebuilt from scratch to library standards: fully parametric, no hardcoded dimensions, correct tolerance callouts, consistent origin placement. Old project geometry was reference only.
Each component documented with: function description, parameter table, tolerance specification, typical application notes, and known limitations. Documentation maintained alongside geometry files.
Library updated continuously. New components added when projects introduce recurring needs. Existing components revised when practice or standards knowledge improves. Changelog maintained.