sidebar reorganization (risc0#1468)

This PR mostly just moves content around in order to make the conceptual
flow clearer.
Rather than looking at the diff in GitHub, I suggest reviewing by
opening the deployment, imagining yourself as a new user, and trying it
out.

The high-level thinking around the conceptual flow for users is
described in this diagram:
<img width="1046" alt="image"
src="https://github.com/risc0/risc0/assets/15272444/08f89eee-adc6-48da-acf2-b905475f9ce2">

- [ ] This PR moves the `bonsai/quickstart.md` doc to
`generating-proofs/remote-proving.md`. If we use this organization, we
need to set up a re-direct so that the QR codes and outstanding links
that point to `bonsai/quickstart` don't 404.
- [ ] This PR deletes the `bonsai/overview.md` doc. We need to set up a
re-direct so that QR codes and outstanding links that point to `bonsai/`
don't 404. The redirect should point to
`generating-proofs/remote-proving.md`

<s>This PR also drops the slug on the `zkvm_overview` doc, which means
links to `/zkvm/` will 404. If we want to drop this slug, we should set
up a re-direct from `/zkvm/` to `/zkvm/zkvm_overview.md` to address
this. </s> resolved by keeping the slug

---------

Co-authored-by: Victor Graf <[email protected]>
Co-authored-by: Frank Laub <[email protected]>
Co-authored-by: Frank Laub <[email protected]>

Author: 3 people

website/api/bonsai/bonsai-on-eth.md renamed to website/api/blockchain-integration/bonsai-on-eth.md

@@ -2,7 +2,7 @@
 
 _Warning: The zkVM and Bonsai are still in development. Do not use in production._
 
-Prove computation with the [RISC Zero zkVM](../zkvm) and verify the results in your Ethereum contract.
+Prove computation with the [RISC Zero zkVM](../zkvm/zkvm_overview.md) and verify the results in your Ethereum contract.
 
 The zkVM and Bonsai together can act as a [coprocessor][coprocessor-article] to the smart contract application.
 This unlocks powerful new applications on Ethereum that offload computationally intensive (i.e. gas expensive) and difficult to implement (e.g. ed25519 signature verification, or HTML parsing) functions to the zkVM.

website/api/bonsai/eth-examples.md renamed to website/api/blockchain-integration/eth-examples.md

@@ -0,0 +1,18 @@
+# Local Proving
+
+RISC Zero offers a fully [open-source] prover.
+Users can run the [zkVM] locally, generating proofs using their own hardware.
+The [feature flags] include options to toggle between CPU and GPU proving.
+
+## Local vs. Remote Proving
+
+For most use cases, we recommend remote proving using [Bonsai].
+The primary reason to consider using local proof generation for your application is to manage private data.
+
+> Whoever is generating the proofs can see all private information involved.
+
+_With local proof generation, you can generate proofs about your private data, while your private data never leaves your machine._
+
+[open-source]: https://risczero.com/news/open-source
+[zkVM]: ../zkvm/zkvm_overview.md
+[feature flags]: https://github.com/risc0/risc0#feature-flags

website/api/bonsai/blockchain-zkvm-guide.md

@@ -0,0 +1,16 @@
+# Options for Proof Generation
+
+To support a variety of use cases, RISC Zero allows users a variety of options for proof generation.
+
+Users can choose between:
+
+1. [dev-mode]: No proofs are generated, enabling rapid prototyping.
+2. [Local Proving]: Proofs are generated on the user's own CPU/GPU.
+3. [Remote Proving]: Proofs are generated by [Bonsai], a highly parallelized, highly performant proving service.
+
+We recommend option 1 during development, option 2 for applications involving private inputs, and option 3 for all other applications.
+
+[dev-mode]: ./dev-mode
+[Local Proving]: ./local-proving
+[Remote Proving]: ./remote-proving
+[Bonsai]: https://bonsai.xyz

website/api/bonsai/bonsai-overview.md

@@ -0,0 +1,33 @@
+# Remote Proving using Bonsai
+
+Bonsai lets users generate proofs for their zkVM applications, without using their own hardware for proof generation.
+Users specify which zkVM application they want to run, as well as the inputs to that program, and Bonsai returns a proof.
+
+Bonsai is highly parallelized and highly performant: proving work on Bonsai is split among a dynamically-sized GPU cluster, offering ultra-fast proving.
+To get a taste of what you can do with Bonsai, check out [Zeth], our [Governance Showcase], [Bonsai Pay], and our twitter thread about using [Bonsai as a zk coprocessor].
+
+If you already have an API key, you can request proofs from Bonsai in any of the following ways:
+
+- via **[cargo risczero]** (great for experimenting or for non-blockchain applications)
+  - Enable Bonsai by setting the environment variables `BONSAI_API_KEY=<YOUR_API_KEY>` and `BONSAI_API_URL=<BONSAI_URL>` when running your program
+- via the **[Bonsai Foundry Template]** (for accessing Bonsai via Ethereum)
+- via the **[Bonsai SDK]** (for accessing Bonsai from Rust)
+- via the **[Bonsai REST API]** (for building your own client or accessing Bonsai directly)
+
+If you don't have an API key, you can [request access].
+While you wait, you can make use of the local proving option on the Bonsai Foundry Template, or you can focus on developing for the [zkVM].
+
+[litepaper]: /litepaper
+[request access]: https://bonsai.xyz/apply
+[Bonsai SDK]: https://crates.io/crates/bonsai-sdk
+[Bonsai REST API]: https://api.bonsai.xyz/swagger-ui/
+[Bonsai as a zk coprocessor]: https://twitter.com/RiscZero/status/1677316664772132864
+[Governance Showcase]: https://github.com/risc0/risc0/tree/main/bonsai/examples/governance#readme
+[Zeth]: https://www.risczero.com/news/zeth-release
+[guest program]: /terminology#guest-program
+[receipt]: /terminology#receipt
+[journal]: /terminology#journal
+[Bonsai Pay]: https://www.risczero.com/news/bonsai-pay
+[Bonsai Foundry Template]: https://github.com/risc0/bonsai-foundry-template/blob/main/README.md
+[cargo risczero]: https://crates.io/crates/cargo-risczero
+[zkVM]: ../zkvm/zkvm_overview.md

website/api/bonsai/quickstart.md

@@ -0,0 +1,57 @@
+# Getting Started
+
+To harness the power of ZK, you'll need to:
+
+1. [Write an application for the RISC Zero zkVM][zkvm-quickstart].
+2. [Generate proofs for your zkVM application][bonsai-quickstart].
+3. [Integrate your proofs into on-chain applications][bonsai-on-eth].
+
+```mermaid
+
+flowchart TD
+    %% Level 0
+    getting_started["Getting Started
+    To use the zkVM and/or Bonsai for blockchain applications, users will need to:
+    1. Build a zkVM app.
+    2. Generate proofs for their zkVM app.
+    3. Integrate proofs into blockchain applications."]
+
+
+
+    zkvm_app["1. zkVM Application Development"]
+        zkvm_quickstart["zkVM Quickstart"]
+    proof_generation["2. Generating proofs for your zkVM application"]
+
+    chain_integration["3. Blockchain Integration"]
+        getting_proofs_on_chain["Post proofs on-chain"]
+        onchain_verifier["Call our on-chain verifier"]
+
+
+    dev_mode["Dev Mode
+    - Skips proving enabling fast prototyping"]
+    local_proving["Local Proving
+    - Made possible by open-source tech
+    - Important for privacy applications"]
+    remote_proving["Remote Proving
+    - Bonsai is a scalable proving service, <br/>ready to generate proofs as needed."]
+
+
+
+    getting_started --> zkvm_app
+        zkvm_app --> zkvm_quickstart
+    getting_started --> proof_generation
+            proof_generation --> dev_mode
+            proof_generation --> local_proving
+            proof_generation --> remote_proving
+    getting_started --> chain_integration
+        chain_integration --> getting_proofs_on_chain
+        chain_integration --> onchain_verifier
+
+
+
+
+```
+
+[zkvm-quickstart]: ./zkvm/quickstart.md
+[bonsai-quickstart]: ./generating-proofs/proving-options.md
+[bonsai-on-eth]: ./blockchain-integration/bonsai-on-eth.md