[LorenzBischof]

This change targets the homepage with the goal of better communicating what Capsule is and what it does. Please look at it as experimentation. Suggestions are welcome.

Yes, it was generated with the help of AI, but I did lots of back and forth to try and get it usable.

Tell me what you think!

[netlify]

✅ Deploy Preview for docs-projectcapsule ready!

Name	Link
🔨 Latest commit	ed516bf
🔍 Latest deploy log	https://app.netlify.com/projects/docs-projectcapsule/deploys/6ad36d8fbe79f552682c7b08
😎 Deploy Preview	https://deploy-preview-156--docs-projectcapsule.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[sandert-k8s]

Nice work! I like the style that the front page already covers some basic resources to show what it does!

Some ideas:

• The title is now Self-service namespaces instead of Capsule. I'm not so sure about that. The subtext (Capsule is a multi-tenancy framework for Kubernetes. Give teams the freedom to create and manage their own namespaces. Keep access, resource budgets and policies under platform control.) is very strong!

• I always liked the "developed in" part on the main page, to shown european sovereignty; although I also understand that the footer is maybe a better place.

• The tenant spec now shows a registry rule. Maybe this could be switched to resource quota's, since thats the most used feature of Capsule.

• The section of CNCF Sandboxed is gone, I think it's good to still have that.

Overall I like the style, looks way more modern and it gives a good summary of Capsule!

[sandert-k8s]

The section with examples still has the registry example. Or was that intended?

[LorenzBischof]

Thanks for the review ❤️ I updated the homepage according to your comments. Happy to do more changes if you notice something else.

[sandert-k8s]

I like it! 🚀

[oliverbaehler]

• "The Problem" section is very vague and does not really layout a problem statement:

• Features should have 6 items

[LorenzBischof]

Thanks for the review ❤️

• "The Problem" section is very vague and does not really layout a problem statement:

I agree. Its not very strong. I adapted mine from https://projectcapsule.dev/docs/overview/#the-problem but left out the grouping, because that can be achieved with labels. I see lots of companies use their own custom namespace CRD, which is why I added that point. Basically they are supposed to be the three self-service steps: no self-service at all, a custom CRD (usually via a central repository), your own cluster with lots of permission.

I tried to use the least amount of text as possible to keep it skimmable.

Let's discuss and refine this in person the next time we see each other, because I think its really important to get it right for the homepage.

• Features should have 6 items

What's missing?

[oliverbaehler]

Alright lets make these really strong points:

• Namespaces: Namespaces are provisioned trough custom processes and developers cannot list their own namespaces.
• Custom CRD: More like Moving APIs. You must create an API where the Platform Team and Kuberentes Users can agree on the guardrails needed by the platform or the workloads. These processes are often custom and need some sort of platform authority in the loop
• Scaling Control Planes: Another control plane per team to upgrade, secure and pay for. (Good)
• Responsability: It gets difficult to define who is responsible for what, no concrete API contract may reflect the needed structure to reflect namespace/workload ownership

For the missing. feature, i would add Permissions (https://deploy-preview-156--docs-projectcapsule.netlify.app/docs/tenants/rules/#permissions). Just that there is even amount of tiles.