Proposal for vendor-specific documentation

[geriom]

To improve the real world usability of the documentation, it would be helpful to include vendor-specific documentation for common tasks like installation and authentication.

This proposal shows an example of how this can be implemented with the current documentation tools.

• Create a vendors folder with subfolders for each vendor. For example:

  content/en/vendor/
  ├── google
  │   └── registry_authentication.md
  ├── ibm
  │   └── registry_authentication.md
  └── microsoft
    └── registry_authentication.md

• Use the readfile shortcut to include that documentation wherever it's reelevant. For example, for the authentication section of the Kaniko build how-to, we can do this:

  {{< tabs >}}
  
  {{< tab "Google" >}}
  {{< readfile "/vendor/google/registry_authentication.md" >}}
  {{< /tab >}}
  
  {{< tab IBM >}}
  {{< readfile file="/vendor/ibm/registry_authentication.md" >}}
  {{< /tab >}}
  
  {{< tab Microsoft >}}
  {{< readfile file="/vendor/microsoft/registry_authentication.md" >}}
  {{< /tab >}}
  
  {{< /tabs >}}
  

  The corresponding output:

  

  Site preview available here

• Each vendor (or the community) will have ownership of their documentation and it's their responsibility to keep it up-to-date

• We can go a step further and make each folder their own repository. We can either use git submodules or the sync script to pull the content from the repo and render it on the website.

[tekton-robot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale with a justification. 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 with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten with a justification. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen with a justification. Mark the issue as fresh with /remove-lifecycle rotten with a justification. If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to [this](https://github.com/tektoncd/website/issues/432#issuecomment-1406867425): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen` with a justification. >Mark the issue as fresh with `/remove-lifecycle rotten` with a justification. >If this issue should be exempted, mark the issue as frozen with `/lifecycle frozen` with a justification. > >/close > >Send feedback to [tektoncd/plumbing](https://github.com/tektoncd/plumbing). 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 [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.