Hi everyone, I’m trying to figure out the best way to organize documentation for a small hardware project inside a Hugo site. I’m building a simple ESP32 motion-detection setup: https://www.theengineeringprojects.com/2022/03/iot-based-motion-detection-with-email-alert-using-esp32.html, and I want to publish the build steps, diagrams, and code snippets cleanly without the layout feeling cluttered. I’ve seen people in Arduino forum threads using section bundles for each project, and some Raspberry Pi bloggers seem to prefer putting all hardware guides in dedicated content folders with shortcodes for code blocks. A few IoT community posts even suggest using taxonomies for hardware, sensors, etc. For those who’ve documented hardware/electronics builds in Hugo before, what structure worked best for you?
I don’t have such a website, but after recently restructuring my site, here is what I recommend—
- Use dedicated branch bundles for each project.
- Use leaf bundles for pages with resources like images, etc.
- Use taxonomies as you suggested
title: "ESP32 Motion Sensor Build Guide" tags: ["esp32", "pir-sensor", "iot"] categories: ["hardware", "tutorial"]