Documentation update for issue #920 #131
Draft
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.
Attempt to resolve issue 920
The user's intent is to incorporate practical, real-world examples from existing blog posts into the official NGINX documentation, update the content to current standards, organize it around common use cases, and ensure it is easy to find and maintain. The potential documents include various technical and informational pages, such as product overviews, configuration guides, API references, and tutorials. To fulfill this, the most relevant documents are those that contain technical content, usage examples, and API details, specifically the "Metrics API" documentation, the "Overview" page, and the "Configuration" guide. These pages can be enhanced by integrating practical examples, clarifying use cases, and updating content for clarity and current standards. Other documents like changelogs, index pages, or redirect dummy pages are less relevant for content updates. The plan is to update the "Metrics API" documentation with real-world examples and use cases, improve the "Overview" page with practical insights, and enhance the "Configuration" guide with clearer instructions and examples. The other documents will not be updated as they are either placeholders or less relevant for content enhancement.