Found a broken link at /docs/index.md

[AdityaC45]

The link is present under the

• Links section:
  - user guide
  - How to write a COSI driver
  - How to make your application COSI-compatible
• Advanced section:
  - Protocols
  - Architecture
  - Internals
• Other:
  - Weekly Meetings

[AdityaC45]

These documents are not yet created, I can work on this issue but will need help on the content that needs to be added to these documents

[guymguym]

I think the docs moved here - https://container-object-storage-interface.github.io/
Still worth updating the main README.md because it's just bad that those links are broken...
CC @wlan0

[guymguym]

The docs source project:

• https://github.com/container-object-storage-interface/container-object-storage-interface.github.io

[AdityaC45]

Hi , I went through that link but still there are no contents added to some of the docs so if we are going to update the documentation in the link shared then it will be good otherwise we again have to change the link

[tparikh]

Thanks for reporting this issue @AdityaC45. I will take a look into this and update the docs and links.

/assign @tparikh

[AdityaC45]

If you need any help, I will be glad to help you @tparikh

[tparikh]

@AdityaC45 I have raised PR to fix the broken link to documentation. Team is working on populating the empty pages on the documentation site.

[AdityaC45]

Ohkk thanks👍

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten