Homepage UX rework: there are too many CTA buttons

[chalin]

Per website UX guidance, a page should ideally have at most one primary Call-To-Action (CTA) button, and one or two secondary CTA buttons. Any more and this exponentially dilutes the "call" power of the buttons.

Our homepage currently has 5 CTA buttons. That is way too many!

We need to rethink and refocus our CTA real estate, and delegate the remaining links to, say, the OTel-highlights ribbon a little further below on the homepage.

References:

• Spotlight project integrations #3306 - had a good intention, but adding a CTA wasn't IMHO the right UX design choice

[theletterf]

I think the most powerful is "Try the demo". Looking now at the PR!

[chalin]

I agree that we could give more prominence to the demo. I'm wondering if the demo is running somewhere, and whether there is a publicly available web interface into at least rudimentary telemetry of the demo? That might be a better "try the demo" experience for a drive-by reader, vs. "install the demo yourself". WDYT?

[chalin]

We need to revisit the "Getting started" pages IMHO. At the moment, those pages read more like guiddance on how to read through the rest of the docs. I'd rather see some form of "quick start", but I understand the challenge in setting that up. As I mentioned elsewhere, I think that this would make a good topic of discussion for an upcoming Comms meeting.

[theletterf]

Hard agree on revisiting Getting Started. Let's make it a topic for the next call.

[svrnm]

Yeah, those getting started guides never turned out to be the way we envisioned them, so maybe we should rethink them and find a different way to get people started.

[cartermp]

I think we can axe the dev/ops persona-ish getting started.