How does each component in Compliant Kubernetes help the Application Developers succeed?

[cristiklein]

Describe the bug

This page hasn't aged very well.

Ideally, it should be replaced with a page containing:

• A visual overview of the DevSecOps loop, with a mapping of all Compliant Kubernetes components onto it;
• A textual explanation of how each component contributes to the DevSecOps story.

[cristiklein]

@viktor-f and @llarsson Can you check if I capture what you need sufficiently?

[viktor-f]

Yeah that looks good. The textual explanations can be rather short, but should preferably link to more information.

[llarsson]

Yeah, that would help explain what is going on under the hood, and why things are there. If at all possible, it would be nice if the text works also without the loop (then it is more copy-paste-able for people in other contexts). I know that we have training material (currently internal at Elastisys) that already has like a short bullet list for each component, just to introduce what it does. That could be a very good starting point. I'll send a link to you over Slack, since this is a public repo.

[cristiklein]

Related to this issue, we brought the "Application Developer overview" page back into the navbar. This was done to eliminate "not in navbar" warnings that mkdocs was issuing.