envoyproxy/envoy

Use tabs for API info on docs pages

Open

#16,329 opened on 2021年5月5日

GitHub で見る
 (4 comments) (0 reactions) (1 assignee)C++ (5,373 forks)batch import
api/v3area/docsarea/protobufhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (平均マージ 8d) (30d で 378 merged PRs)

説明

description

atm there are various appendages to API info - security status, canonical name, config, extension info

we are also going to add canonical uri, examples, formerly known as info, lifecycle status, and richer extension info

atm it uses .. notes, and .. tips and in some places warnings in others - this is making for a bit of an angry fruit salad

i think we need to shift this info into tabs for API files and fields and figure out how best to prioritize

this will also allow extension examples which adds significantly to the complexity here

コントリビューターガイド