docs: restructure Layered Zero Trust documentation

[p-rog]

Summary

• Restructure the Layered Zero Trust documentation with a customer-first, value-driven approach
• Add GUI installation as the primary path with 9 screenshots and an installation video
• Create three new pages: Architecture, Data Protection, and Security Monitoring
• Rewrite the landing page to lead with problems and outcomes instead of technical abstractions

New site structure

Tab	Description
About (rewritten)	Value proposition, problem statement, capability grid
Architecture (new)	Layered model, component tables, sidecar pattern, deployment variants
Getting Started (rewritten)	GUI-first with screenshots/video, CLI as advanced option
Data Protection (new)	qtodo Zero Trust walkthrough — accessible for demos and field engineers
Security Monitoring (new)	ACS custom policies, network policy monitoring, runtime threat response
Secure Multitiered Apps	Existing (updated weight + cross-ref to Data Protection)
Secure Supply Chain	Existing (updated weight)
Automated Supply Chain	Existing (unchanged)

Key changes

• Landing page leads with static defense and data protection problems before CVEs
• Vault highlighted beyond secret storage — includes JWT auth for workload identity
• GUI installation marked as "batteries included" baseline; CLI for advanced feature sets
• "Argo CD" spelling corrected throughout; proper instance navigation documented
• Keycloak credentials retrieval updated — keycloak-users Secret removed, credentials now in Vault only
• Security monitoring policies wording updated to "Projects/Namespaces should have..."
• ACS policies deployment location referenced (charts/acs-policies)
• Both Data Protection and Security Monitoring note they are part of the default installation

Test plan

• Verify all cross-references resolve correctly when the site builds
• Verify screenshots render properly
• Verify video embed works (may need format conversion for Hugo)
• Review content accuracy with team

Made with Cursor

[openshift-ci]

Hi @p-rog. Thanks for your PR.

I'm waiting for a validatedpatterns member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[p-rog]

@sabre1041 @mlorenzofr Please review this update. I tried to cover everything we discussed.