Patrice Chalin
Patrice Chalin
Ensure that the community page links to at least the following: - [grpc/grpc-community](https://github.com/grpc/grpc-community) - [grpc-ecosystem](https://github.com/grpc-ecosystem)/[awesome-grpc](https://github.com/grpc-ecosystem/awesome-grpc) (This item was formerly a part of #280)
For example, for Dart, you'd probably link to [Dart Generated Code > Compiler Invocation](https://developers.google.com/protocol-buffers/docs/reference/dart-generated#invocation). Context: https://github.com/grpc/grpc.io/pull/423#issuecomment-700293743
Consider adding links to the [proto buf doc Generated Code reference pages](https://developers.google.com/protocol-buffers/docs/reference/overview), particularly for those languages that don't have any such reference already: > For those languages that already have...
We could have a string of GH specific buttons. As an alternative, [cockroachlabs.com](https://www.cockroachlabs.com/docs/cockroachcloud/quickstart.html) uses a dropdown: >
For example, .proto should be styled as `.proto`. Context: https://github.com/grpc/grpc.io/pull/157#discussion_r395914551
API references starting with path `/grpc/` aren't shown as external links (this is inconsistent with how we show `/api/` path links). For example, see [Asynchronous-API tutorial > Overview](https://grpc.io/docs/languages/cpp/async/#overview): > Also,...
The current redirect rules for the local `/api/` links should probably end with a splat. That way we'll be able to change all `/grpc/...` paths (such as `/grpc/cpp/classgrpc_1_1_completion_queue.html`) to `/api/...`....
Who's using gRPC shows up in 3 places: - [Homepage](https://grpc.io/), **Used by** section - https://grpc.io/about/#whos-using-grpc-and-why - https://grpc.io/faq/#whos-using-this-and-why This should be DRYer.
There are a few issues with the blog-page front matter attributes and processing. (These are thoughts that arose as I was working on #376.) - [ ] On the old...