You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
can we increase the width of column one so the lines don't wrap for the header?
rename columns from Term --> Header and Definition --> Description
do we need to repeat "AI Gateway" in each description? This glossary is within AI Gateway docs so i would hope they know what we're referring to
can the deprecated headers be it's own separate table?
Reword description --> "AI Gateway supports a variety of headers to help you configure, customize, and manage your API requests. This page provides a complete list of all supported headers, along with a short description"
can we link each header to the specific part of each page it's on?
can we increase the width of column one so the lines don't wrap for the header?
rename columns from Term --> Header and Definition --> Description
do we need to repeat "AI Gateway" in each description? This glossary is within AI Gateway docs so i would hope they know what we're referring to
can the deprecated headers be it's own separate table?
Reword description --> "AI Gateway supports a variety of headers to help you configure, customize, and manage your API requests. This page provides a complete list of all supported headers, along with a short description"
can we link each header to the specific part of each page it's on?
We can't adjust this table unfortunately.
Researching on how to do this because a glossary is more like a changelog in format (also for 4)
Move the header hierarchy info to the bottom of the page because the main point of this page is the glossary. So it should be a) intro paragraph about headers b) the table c) followed by the configuration hierarchy
--> The page should start with
"AI Gateway supports a variety of headers to help you configure, customize, and manage your API requests. This page provides a complete list of all supported headers, along with a short description"
IS the spacing of the numbered list in "configuration hierarchy" correct? seems like there's a lot of empty space between each number
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Screenshots (optional)
Documentation checklist