Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions documentation/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,7 @@ If you're interested in contributing to the [NGINX documentation website](https:
- [Using include files](/documentation/include-files.md)
- [Contributing closed content](/documentation/closed-contributions.md)
- [Review deprecated content](/documentation/deprecated-content.md)
- [nginx.org content](/documentation/nginx-org-source.md)

## Writing guidance

Expand Down
9 changes: 9 additions & 0 deletions documentation/prepare-issue.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,15 @@ We strive to make each issue a single source of truth: as a result, each ticket

This document exists to explain concepts you may be unfamiliar with, and provide examples of the types and amount of detail preferred.

Here are examples of well-formed issues using the templates:

- [\[Request\]: Clarify NGINX configuration limitations for F5 WAF for NGINX](https://github.com/nginx/documentation/issues/1436)
- [\[Story\]: Replace examples of sensitive values with explicit placeholders](https://github.com/nginx/documentation/issues/1363)

*General request* and *Bug report* are the most common issue types, with *Documentation idea* available for conceptual improvements.

The *User story* and *Content release plans* are largely for maintainer use, though we do have [guidance for user stories](#user-stories-and-acceptance-criteria) in this document.

## Use active voice

Much like writing user-facing documentation, we prefer [active voice](https://developers.google.com/tech-writing/one/active-voice) when describing an issue.
Expand Down
Loading