Files
openclaude/docs
Ahmar YaseenandGitHub 661b5ad8cd docs(non-technical-setup): add Getting Help section with support link… (#1631)
* docs(non-technical-setup): add Getting Help section with support links and diagnostic check

The non-technical setup guide ended abruptly after the advanced setup
reference. New users — especially non-technical ones — had no clear path
to follow when they encountered issues beyond the common problems listed.

Add a Getting Help section at the end that includes:
- GitHub Discussions link for Q&A and setup help
- GitHub Issues link for bugs and feature requests
- A quick diagnostic check (openclaude --version) with actionable
  next steps for when the command is not found

This also cross-references the Windows Quick Start guide for npm Path
configuration, reusing existing documentation rather than duplicating
instructions.

Impact: improves first-run experience for the guide's target audience
without changing any code or behavior.

* docs(non-technical-setup): add Getting Help section and restructure around /provider flow

The guide previously directed users to set environment variables before launching the CLI. This misses the simpler onboarding path: users can install, run openclaude, and use /provider for guided setup inside the CLI without any env vars.

Changes:
- Remove required API key from 'Before You Start' prerequisites
- Rewrite 'Fastest Path' to recommend install -> run -> /provider
- Remove env variable step from the fast path
- Add note under provider descriptions that /provider handles setup
- Update 'Invalid API key' troubleshooting to use /provider instead of re-pasting env vars
- Add 'Getting Help' section with support links and diagnostic check

Impact: better aligns the non-technical guide with the current recommended onboarding flow. No code changes.

* docs(non-technical-setup): restore API key prerequisite, restructure Fastest Path around /provider

Re-add the API key to prerequisites. The key is still needed - the /provider flow is just the recommended way to enter it instead of env vars.

Changes:
- Keep API key in prerequisites
- Rewrite Fastest Path to install -> run -> /provider instead of env vars
- Add note under provider descriptions that /provider handles setup
- Update Invalid API key troubleshooting to use /provider
- Add Getting Help section with support links and diagnostic check

Impact: aligns the non-technical guide with the current recommended onboarding flow. No code changes.
2026-06-15 08:49:49 +08:00
..