Docs navigation

[vfarcic]

I suggest the following navigation structure for the left-hand menu:

• Concepts
  • What Is Jenkins X?
  • Lifecycle Of An Application
  • Best Practices As a Service
  • GitOps
  • ChatOps
  • Preview Environments
  • Cloud-Native
  • Kubernetes
• Setup
  • Getting Started (a quick demo setup in a few Cloud providers)
  • Infrastructure Setup
  • AWS
  • Azure
  • Google Cloud
  • OpenShift
  • Something else
  • Install
  • Upgrade
  • Reference
• Tasks
  • Create A New Project
  • Import An Existing Project
  • Manage Pull Requests
  • Promote To Environments
• Examples
• Operations
  • Configure TLS
  • Secrets Management
  • Logging
  • Reporting
• Reference

I believe that the proposed structure is self-explanatory. If it is not, it would mean that the structure is wrong, rather than that it requires additional explanation.

[hferentschik]

IMO we definitely need the concepts part back and another landing page into the docs. Right now there are concepts under "About" but that feels wrong.

[hferentschik]

https://istio.io/latest/docs/ could be an example/reference for a similar structure.

[deanesmith]

I am good with this. There are deep assumptions in the Infrastructure Setup section that would require substantial effort.

[vfarcic]

@deanesmith Those are only example items. The final ones would certainly differ.

[sharepointoscar]

Not sure if Operations replaces Guides but I feel we still need a Guides section that has multiple real-world scenario configuration guidance.

• How do I use my own SSL Certificates
• Bring my own Vault
• How do I give other developers access to the cluster, and why do I need to?
• How do I add users to Jenkins X for specific roles defined by Jenkins X?
• How do I harden my Jenkins X cluster

And the list goes on...

[ankitm123]

Would be nice to have a production hardening sub-section under operations (similar to what hashicorp has: https://learn.hashicorp.com/vault/operations/production-hardening)

[sharepointoscar]

Would be nice to have a production hardening sub-section under operations (similar to what hashicorp has: https://learn.hashicorp.com/vault/operations/production-hardening)

Exactly @ankitm123 , this is the last bullet I added above.

[jenkins-x-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://jenkins-x.io/community. /lifecycle rotten

[jenkins-x-bot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten. Provide feedback via https://jenkins-x.io/community. /close

[jenkins-x-bot]

@jenkins-x-bot: Closing this issue.

In response to [this](https://github.com/jenkins-x/jx-docs/issues/2869#issuecomment-730636494): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. >Provide feedback via https://jenkins-x.io/community. >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [jenkins-x/lighthouse](https://github.com/jenkins-x/lighthouse/issues/new?title=Command%20issue:) repository.