Tim Bannister

Help, from any contributor, is welcome.

We don't [we try hard not to] split topics by audience expertise @mrgiles. See if you can find a different way to slice up these concepts.

This is important work; however, changes are costly (people bookmark docs), so we like to avoid any need to redo things. That means we invest more effort in getting the...

Tasks are one of [what we see as] the [four kinds of documentation](https://www.writethedocs.org/videos/eu/2017/the-four-kinds-of-documentation-and-why-you-need-to-understand-what-they-are-daniele-procida/); Pods are not. I **wouldn't** make a landing page for Pods, but I would try to help...

I like that last suggestion. If you're now convinced @shirady, I suggest you open new issues about each improvement that you support from the outline in https://github.com/kubernetes/website/issues/38867#issuecomment-2375441883 and close this...

What I'm suggesting is: a set of new issues, each one capturing a single chunk of the outline @tengqm made earlier - see https://github.com/kubernetes/website/issues/38867#issuecomment-2375441883 That will let different authors work...

If folks want to make a PR that aligns with the overall idea, getting ahead of the issue tracking work: you can! It's open source, and help of all kinds...

@sergeyshevch: do you have the time to address the feedback so far?

How will we persuade all container runtimes to adopt this special layer format; how will we provide compatibility for runtimes that don't yet include that support?

Alternative: define a new type OCI artefact (not a layer) that represents a chunk of application data. This can then be mapped to something that looks like a file and...