Markdown - Wikipedia
Plain text markup language| en.wikipedia.org
Comparing the new Bazel build to the old GN build#| pigweed.dev
In technical communication, we don’t talk much about decision support; we talk| technicalwriting.dev
Report an issueopen_in_new| Bazel
Pigweed is an open-source collection of libraries from Google that enables fast and reliable development for embedded systems. Last September, Pigweed decided to migrate from GN to Bazel as their primary build system based on the belief that Bazel has great potential to improve embedded developers' productivity and mental wellbeing. Since then, the Pigweed team collaborated closely with the Bazel team on many improvements to make Bazel a more powerful build system not just for Pigweed develop...| blog.bazel.build
Report an issueopen_in_new| Bazel
Report an issueopen_in_new| Bazel
Documentation home| reproducible-builds.org
Report an issueopen_in_new| Bazel
Should docs stay with the code they document? Or should they rather be in a separate repo, fully managed by tech writers and docs site developers? The matter of where docs should be living when doing docs-as-code isn’t easy to untangle. With the following topologies I’ve tried to describe situations I’ve found myself into or seen in the wild. Each has its own pros and cons, though only the last is my favorite.| passo.uno
