What about we add a README.md (docs/resource/k8s/README.md) ? Then we can just use that as the entry point for both the k8s.md and openshift.md. With something like:

Container orchestration

Status: Development

This document defines semantic conventions for resource in container orchestration systems.

• K8s: Semantic Conventions for K8s.
• OpenShift: Semantic Conventions for OpenShift.

What about we add a README.md (docs/resource/k8s/README.md) ? Then we can just use that as the entry point for both the k8s.md and openshift.md. With something like:

Sure, that works, if it is what you prefer. It's just that what you propose feels a bit less natural. E.g., you write "conventions for resource in K8s" twice: once for the landing page and then again for a subpage. WDYT?

Yeah maybe we have the landing page with "Container Orchestration" instead :). Fixed the example above.

Yeah maybe we have the landing page with "Container Orchestration" instead :). Fixed the example above.

@joaopgrassi - hmm, but then the folder name should be changed too? So rename the k8s folder to, say, container? Otherwise, I can't create a redirect for the moved k8s page. If I try, it creates a loop for the index page.

If the section really is about k8s resources, then I think the change proposed in this PR is probably best. But I defer to you.

Alright, let's keep your suggestion then, and we can revisit later if necessary.

@joaopgrassi I like your idea of having page with links to k8s and openshift but let’s first merge as is to unblock