Hardware vs. Software: Does Dev.to even want circuit builds?

I've been hitting a bit of a mental block regarding my recent side projects. I've been messing around with some DIY hardware builds and small electronic circuit experiments lately, but I'm hesitant to dump my documentation on Dev.to. Since the platform is heavily skewed toward the software dev crowd, I'm worried my posts might feel like a total mismatch for the feed.

I don't want to just spam random hardware builds and clutter everyone's timeline if they're only looking for React hooks or Rust optimizations. On one hand, the line between firmware and pure software is getting thinner every day, so hardware content feels relevant. On the other hand, if I start posting schematic walkthroughs, will people just scroll past because it's not "code"?

I'm trying to figure out if there's a sweet spot for this kind of technical content. I’m not looking to become a "hardware influencer" or anything; I just want to share my process without it feeling out of place. If I post a breakdown of a circuit I've been debugging, does that actually add value to a community that's mostly focused on web and backend dev?

I'd love to know if anyone else here bridges that gap between hardware and software, or if I should just stick to pure code-based repos to stay within the scope. If the community is cool with it, I'll keep the posts high-quality and focused on the technical logic rather than just showing off components.