Problem
The Getting Started section introduces two distinct ways to self-host a ContextVM server — the TypeScript SDK and the CVMI CLI tool — but gives no guidance on which one to use or when.
A new user landing on this page faces an immediate, unresolved question: Which path is for me? Without an answer, most will either pick the wrong one and get stuck or leave entirely.
Concretely:
- "TypeScript SDK" signals to non-developers that they need to write code, which may not be true for their use case
- "CVMI" is an unfamiliar acronym with no one-line plain-language description at the point of decision
- There is no decision criteria, comparison, or recommendation anywhere on the page
Current Behaviour
The Getting Started page lists both options at roughly equal weight. The user must navigate into each section individually to figure out which applies to their situation, after already committing to a path.
Expected Behaviour
Before presenting any technical content, the page should answer one question for the user: are you running a server quickly with no code, or building a custom integration?
A simple two-card chooser at the top of the Getting Started page would solve this.
| Card |
Label |
One-line description |
| A |
Quick Setup (CVMI) |
No code required. Expose any MCP server to Nostr in under 5 minutes using the CLI. |
| B |
Custom Integration (TypeScript SDK) |
Building an app or custom server? Implement ContextVM directly in your codebase. |
Each card links directly to its respective guide. The user never has to guess.
Why This Matters
Decision paralysis at the very start of an onboarding flow is one of the most common causes of developer abandonment. The fix here is small — a path-chooser section requires no new documentation, only reorganisation of what already exists — but the impact on first-time user success is significant.
Proposed Change
Add a "Choose your path" section at the top of the Getting Started page, above any technical content, with two clearly labelled options and a one-sentence description of each. The existing CVMI and SDK documentation
pages remain unchanged as the destinations.
Problem
The Getting Started section introduces two distinct ways to self-host a ContextVM server — the TypeScript SDK and the CVMI CLI tool — but gives no guidance on which one to use or when.
A new user landing on this page faces an immediate, unresolved question: Which path is for me? Without an answer, most will either pick the wrong one and get stuck or leave entirely.
Concretely:
Current Behaviour
The Getting Started page lists both options at roughly equal weight. The user must navigate into each section individually to figure out which applies to their situation, after already committing to a path.
Expected Behaviour
Before presenting any technical content, the page should answer one question for the user: are you running a server quickly with no code, or building a custom integration?
A simple two-card chooser at the top of the Getting Started page would solve this.
Each card links directly to its respective guide. The user never has to guess.
Why This Matters
Decision paralysis at the very start of an onboarding flow is one of the most common causes of developer abandonment. The fix here is small — a path-chooser section requires no new documentation, only reorganisation of what already exists — but the impact on first-time user success is significant.
Proposed Change
Add a "Choose your path" section at the top of the Getting Started page, above any technical content, with two clearly labelled options and a one-sentence description of each. The existing CVMI and SDK documentation
pages remain unchanged as the destinations.