LisaFC
LisaFC
Where would we put it on the landing page? I just don't want the landing page to get too cluttered, it already has quite a lot of information on it.
Should we document both approaches in the Quickstart or just mention the static option? I know in the Tutorial we just use the dynamic model and mention the static version...
I think the <!--more--> (excerpt separator) section is less a workaround and more how Jekyll actually expects you to write blog posts - the idea is that you get snippets...
Not that I'm aware of, no. :( Markdown is essentially kind of fragile given how much it relies on whitespace and the fact that it isn't actually standardized....
Objective C is actually covered in its own tutorial, so can link to it.
The standard mapping used by Endpoints (and indeed inside Google) is documented in more detail in the [API Design Guide](https://cloud.google.com/apis/design/), which we should also at least link to - it...
Would a good approach be to add a document called Integrating With Other Systems or similar, and then adding a HTTP/JSON Transcoding section (or just have a separate Transcoding concepts...
I like that, though I'm not sure about duplicating content from http.proto, which is already web-page-i-fied, eg, here: https://cloud.google.com/endpoints/docs/grpc-service-config/reference/rpc/google.api#google.api.Http. That's in the Endpoints docset but we could also add that...
Or we might be able to generate content from http.proto without the Cloudsite templating and put it in grpc.io, though that might be a bit fiddly.