clean up

Author: hdevalence

pages/SUMMARY.md

@@ -1,9 +1,9 @@
 {
-  "index": "Penumbra Guide",
+  "index": "Overview",
   "web": "Using Penumbra on the web",
   "pcli": "Using Penumbra from the command line",
   "node": "Running a node",
+  "frontend": "Running a frontend",
   "dev": "Development",
-  "resources": "Resources",
-  "tutorials": "Tutorials"
-}
+  "resources": "Resources"
+}

pages/_meta.json

@@ -0,0 +1,13 @@
+Penumbra's web tooling is designed to support a decentralized ecosystem of
+frontends.  This allows different frontend codebases to focus on different user
+profiles and ensures that no single frontend deployment or codebase has control
+over users' access to the protocol.
+
+Penumbra wallets like [Prax] sync, scan, decrypt, and locally index user data. When users connect to a frontend, the wallet acts as a "personal RPC", granting that frontend access to the user's private data.
+
+This chapter has information about deploying a Penumbra frontend, for users who do not wish to rely on existing third-party frontends:
+
+- [**Minifront**](./frontend/minifront.md): the minimal, embeddable static-site
+  frontend that runs entirely on the end-user device. A (possibly outdated) copy of Minifront is embedded in every single Penumbra fullnode and served on the RPC endpoint, but it can also be hosted standalone.
+
+[Prax]: https://chromewebstore.google.com/detail/prax-wallet/lkpmkhpnhknhmibgnmmhdhgdilepfghe

pages/frontend.md

@@ -0,0 +1,3 @@
+{
+    "minifront": "Minifront"
+}

pages/frontend/_meta.json

@@ -1,22 +1,13 @@
-# Running a frontend
-
-In order to use the [Prax] wallet web extension, users must visit a trusted
-website that leverages the web extension in order to interact with the [Penumbra] network.
-While users can choose to grant access to website run by a party they trust,
-this guide demonstrates how a user can self-host a frontend for use by themselves and others.
-
-## About minifront
-
 [Minifront] is minimal frontend for interacting with the [Penumbra] chain.
 A number of technical decisions were made to ensure minifront is maximally client side and does not leak
 information unnecessarily:
 
-- Client-side biased js framework ✅ Hash routing ✅
-- Pre-load all static assets ⚠️ (in progress...)
-- Server rendering ❌
-- Route-based code splitting ❌
-- Idiomatic urls & query params ❌
-- Build-time pre-rendering ❌
+- ✅ Client-side biased js framework with hash routing
+- ⚠ Pre-load all static assets  (in progress...)
+- ❌ Server rendering
+- ❌ Route-based code splitting
+- ❌ Idiomatic urls & query params
+- ❌ Build-time pre-rendering
 
 [Read more](https://x.com/grod220/status/1760217326245285923) about how this frontend embraces censorship resistance and
 privacy.

pages/tutorials/running-frontend.md pages/frontend/minifront.md

@@ -1,14 +1,12 @@
-# Penumbra Guide
-
-[Penumbra] is a fully private, cross-chain proof-of-stake network and
+Penumbra is a fully private, cross-chain proof-of-stake network and
 decentralized exchange for the Cosmos and beyond. Penumbra brings privacy to
 IBC, allowing anyone to shield any IBC asset just by transferring it into
 Penumbra's multi-asset shielded pool.  Within Penumbra, users can transact,
 stake, swap, or marketmake without broadcasting their personal information to
 the world.
 
 <picture>
-  <img src="./assets/interchain-shielded-pool.jpg" />
+  <img src="./images/interchain-shielded-pool.jpg" />
 </picture>
 
 Unlike a transparent chain, where all information is public, Penumbra is

pages/index.mdx

@@ -1,4 +1,4 @@
 {
-  "pd": "Full node: `pd`",
-  "pclientd": "Ultralight node: `pclientd`"
-}
+  "pd": "Full node: pd",
+  "pclientd": "Ultralight node: pclientd"
+}

pages/node/_meta.json

@@ -1,3 +1,5 @@
+import { PENUMBRA_VERSION, COMETBFT_VERSION } from '../../../versions.js';
+
 # Installing pd
 There are many ways to configure and run Penumbra. The easiest is to download
 binaries for `pd` and `cometbft` on a Linux system. For alternatives, see
@@ -12,7 +14,7 @@ match the software currently running on the network, to choose the correct platf
 After downloading the `.tar.gz` file, extract it, and copy its contents to your `$PATH`. For example:
 
 ```
-curl -sSfL -O https://github.com/penumbra-zone/penumbra/releases/download/{{ #include ../../penumbra_version.md }}/pd-x86_64-unknown-linux-gnu.tar.gz
+curl -sSfL -O https://github.com/penumbra-zone/penumbra/releases/download/v0.79.2/pd-x86_64-unknown-linux-gnu.tar.gz
 tar -xf pd-x86_64-unknown-linux-gnu.tar.gz
 sudo mv pd-x86_64-unknown-linux-gnu/pd /usr/local/bin/
 
@@ -25,7 +27,7 @@ There's also a one-liner install script available on the release page, which wil
 ### Installing CometBFT
 
 You'll need to have [CometBFT installed](https://docs.cometbft.com/v0.37/guides/install) on your system to join your node to the testnet.
-You must use a compatible version of CometBFT. Any version in the `v0.37.x` series will work, such as `{{ #include ../../cometbft_version.md }}`,
-which you can download [from the CometBFT releases page](https://github.com/cometbft/cometbft/releases/tag/{{ #include ../../cometbft_version.md }}).
+You must use a compatible version of CometBFT. Any version in the `v0.37.x` series will work, such as `v0.37.9`,
+which you can download [from the CometBFT releases page](https://github.com/cometbft/cometbft/releases/tag/v0.37.9).
 If you prefer to compile from source instead, make sure you are compiling the correct version by checking out its tag
 in the CometBFT repo before building.

pages/node/pd/install.md pages/node/pd/install.mdx

@@ -1,5 +1,5 @@
 {
-  "install": "Installing `pcli`",
+  "install": "Installing pcli",
   "wallet": "Generating a Wallet",
   "update": "Updating to the latest testnet",
   "balance": "Viewing Balances",

pages/pcli/_meta.json

@@ -0,0 +1,2 @@
+export const PENUMBRA_VERSION = 'v0.79.1';
+export const COMETBFT_VERSION = 'v0.37.9';