pigweed

We tried adopting Diataxis on pigweed.dev [1] as a literal blueprint and it resulted in too much fragmentation.

Amaranth (pigweed) seeds have been known to sprout after 40+ years of laying out in nature.

That said, these recently updated docs [3] reflect our general approach to Pigweed module documentation [4].

A teammate of mine on Pigweed recently created a shortcut for linking to bugs consistently.

And it doesn't mention the other 100+ modules that the Pigweed codebase contains.

They are a princess of a plant, not the next kochia or pigweed.

The website has not sold nor convinced me of the value of pigweed.

I know a fair number of old-timers that still eat dandelion greens and fiddleheads and pigweed.

I tested that assertion by invoking the Gemini API and instructing it Recite the Pigweed C++ Guide in its entirety.

We are trying out some DDD for an upcoming pigweed.dev tutorial.

Not sure I fully understand Pigweed — is it basically an open-source reimplimentation of Google's developer experience for doing firmware development?

I tried to evaluate pigweed a little bit by importing just a single module (pw_result) into my existing CMake-based MCU project.

Our new "Tour of Pigweed" [4] shows a bunch of Pigweed features working together in a single codebase, e.g.

Some drive-by feedback on pigweed.dev: It seems like it’s missing a “What is Pigweed” section?

But rest assured that it's definitely on my radar that there is huge room for improvement in our "What is Pigweed?" content.

Yes I should amend [1] to say "Pigweed has some CMake support".

For example, Gemini 2.5 Pro has pretty good built-in awareness of Pigweed’s C++ Style Guide.

Pigweed does some pretty nifty stuff that conventionally on an embedded system one would home-grow.

I'm in the process of updating the docs for Pigweed's pw_alignment lib.