[KV] Get started improvements

[Oxyjun]

Summary

1. Clarifying the distinction between binding name and namespace for the CLI workflow.
2. Adding a parallel workflow which uses the dashboard.
3. General cleanup for unclear points.

Screenshots (optional)

Documentation checklist

• The documentation style guide has been adhered to.
• If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
• Files which have changed name or location have been allocated redirects.

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11021221	Triggered	Generic High Entropy Secret	b7a3ed2	astro.config.mjs	View secret
11021221	Triggered	Generic High Entropy Secret	b7a3ed2	astro.config.mjs	View secret
11021221	Triggered	Generic High Entropy Secret	b7a3ed2	astro.config.mjs	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[hyperlint-ai]

2 files reviewed, 2 total issue(s) found.

[cloudflare-workers-and-pages]

Deploying cloudflare-docs with    Cloudflare Pages

Latest commit:	3bb619d
Status:	✅  Deploy successful!
Preview URL:	https://72b5b42b.cloudflare-docs-7ou.pages.dev
Branch Preview URL:	https://jun-kv-get-started-dashboard.cloudflare-docs-7ou.pages.dev

View logs

[github-actions]

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/kv/get-started/	https://jun-kv-get-started-dashboard.cloudflare-docs-7ou.pages.dev/kv/get-started/
https://developers.cloudflare.com/d1/get-started/	https://jun-kv-get-started-dashboard.cloudflare-docs-7ou.pages.dev/d1/get-started/

[hyperlint-ai]

We noticed a change to the style guide files, We resolved the existing comments to account for any changes to your style guide.