N1 Console. Review use of overview.md content
Open
@mjang is already working on this.
Since Oct 13, 2025.
enhancement
P3 - Normal (TTR: 1 month)
stale
- Dominant language
- HTML
- Stars
- 94
- Forks
- 174
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 66
Description
I'm not convinced this needs to be its own page. Would it make sense to add this type of context to content/nginx-one/k8s/_index.md instead? Should we link to the appropriate location in the docs for each of the items in this list?
Note: This doesn't need to be resolve now; more something for us to continue to think about as we evolve our landing pages to reflect the user journey.
Originally posted by @jputrino in https://github.com/nginx/documentation/pull/736#discussion_r2175616780
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.