Am I the only one who finds the 'Getting Started' guide too marketing-heavy?

Okay, let me just get this off my chest. I’ve been trying to onboard a new junior dev to our stack, and I pointed them to the official “Getting Started” guide. The reaction was a slow blink followed by: “So… where do I actually *start*?”

I went back and looked at it with fresh eyes, and… wow. It reads less like a guide and more like a product brochure that’s trying to seduce a VC. We’ve got:

* **The Heroic Mission Statement:** Right up top, before we’ve even confirmed what the product *is*.
* **The “Why Us” Competitive Matrix:** I’m trying to install a CLI tool, not choose a life partner. Save the feature battle cards for the pricing page.
* **Vague, Benefit-Led Headings:** “Transform Your Workflow!” followed by three paragraphs that somehow say nothing about the required environment variables.
* **A distinct lack of the “ugly” first steps.** Where’s the “if you see this error, it’s because you forgot the deprecated flag” honesty? The initial setup has been polished into a fantasy land where everything works on the first `curl | bash`.

It feels like it’s trying to *sell* me on the platform I’m already logged into. I’m already here! The sale is made! Now I need to *use* the thing.

This creates a real adoption tax. The actual technical prerequisites are buried under layers of “revolutionary” and “seamless” jargon. You have to hunt for the system requirements like they’re an embarrassing secret. Is the fear that if they lead with “first, install Docker,” people will run away? If they’ll run from that, they’ll run from the actual product the moment they hit a real problem.

What would I want instead? A clear, linear, slightly cynical “Here’s how not to screw this up” manual.
1. **What this is (in one plain sentence).**
2. **What you need installed first (with version checks).**
3. **The bare minimum to get from zero to “Hello, World” output.** No side-quests into best practices yet.
4. **The first real “Oh, that’s cool” moment** achieved within 5 minutes.
5. *Then*, and only then, maybe a “What’s Next?” section that can link to the visionary stuff.

Am I being too harsh? Has anyone else handed this guide to a newcomer and watched their eyes glaze over while searching for the `--help` equivalent in documentation form?

chloe