“(unknown current hero — feature-list platform pattern)”
The hero attempts to communicate the entire product surface in one viewport. Builds, deploys, databases, jobs, cron, add-ons — the visitor processes none of them because cognitive load exceeds the 5-second attention window. Feature completeness kills clarity when it arrives before context.
“Kubernetes power without the YAML. Deploy, scale, and manage everything from one dashboard — or our API.”
Names the pain (Kubernetes YAML complexity), the solution (one dashboard/API), and the scope (everything). The feature list can live below the fold where interested visitors actively seek depth.