Render a page about each KEP

[lmktfy]

We have a list of KEPs.

This issue proposes rendering a stub (or longer) page per KEP. It can describe details of the KEP available from metadata, such as:

• title
• stage (eg beta)
• SIG(s) involved
  • Links to more info about each SIG
• link to the issue
• link to the KEP text
• feature gates associated with that KEP
• (optional) link to the end user docs for the thing
• snags!

We might only render pages for KEPs that have progressed beyond provisional.

Pages should be rendered via something like a Hugo content adapter, for low-overhead maintenance. If we want to allow manually adding more content to an important KEP (think DRA), then that's feasible but not required.

/area web-development

A nice to have, not an essential thing.

[k8s-ci-robot]

@lmktfy: The label(s) area/web-development cannot be applied, because the repository doesn't have them.

Details

In response to this:

We have a list of KEPs.

This issue proposes rendering a stub (or longer) page per KEP. It can describe details of the KEP available from metadata, such as:

• title
• stage (eg beta)
• SIG(s) involved
• Links to more info about each SIG
• link to the issue
• link to the KEP text
• feature gates associated with that KEP
• (optional) link to the end user docs for the thing
• snags!

We might only render pages for KEPs that have progressed beyond provisional.

Pages should be rendered via something like a Hugo content adapter, for low-overhead maintenance. If we want to allow manually adding more content to an important KEP (think DRA), then that's feasible but not required.

/area web-development

A nice to have, not an essential thing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[lmktfy]

/kind feature

[bupd]

/assign