Thanks. It's basically middleware for large, professional embedded development teams creating mass market products, usually consumer electronics. The four pillars in the "What is Pigweed?" section on the homepage [1] really do sum up a lot of what we do, but the reality is that it's a difficult "product" to explain in general. But rest assured that it's definitely on my radar that there is huge room for improvement in our "What is Pigweed?" content.
Apparently I'm bad at skimming. I did see that section, though apparently not the heading :)
The first part didn't really do it for me because it seemed too meta:
"Over 150 libraries" - to do what? (Actually, some good examples are in the next section.)
"Automation" - to build, test, and lint what?
"Environments" - to make builds reproducible, to do what?
"Frameworks" - turnkey solutions for what?
They are clickable, though, so maybe I should have clicked. :)
> We provide libraries (modules) for strings, time, assertions, logging, serial communication, remote procedure calls (RPC), and much more.
Maybe put that up front?
Looks like "frameworks" are still work in progress; maybe I'll check back someday when they get to Raspberry Pi Pico support.
[1] https://pigweed.dev/#what-is-pigweed