Docs/restructure navigation by ulieth · Pull Request #75 · stakewise/stakewise-docs

ulieth · 2026-03-26T13:34:10Z

Goal

Restructure the operator documentation to create a clear, intuitive journey for a new Vault operator — from understanding what a Vault is, to launching the Operator Service, to ongoing management.

Design Principles

Operator docs as a single entry point. The sidebar now reads like a linear path: understand the role → create a Vault → launch the Operator Service → manage your Vault and validators.
V4 is the default. All shared pages (Manage Vault, Manage Validators, Smoothing Pool) assume V4. V4-only pages have a short admonition about the version requirement with an upgrade link.
- V3 is compact, not duplicated. Operator Service V3 lives in its own folder with only the files that differ from V4 (prerequisites, installation, prepare operator, start operator, alternative key management). Common tasks (monitoring, rated network, vault administration, etc.) are shared. The V3 intro page links to these shared pages explicitly.
- Manual Exit uses tabs. Since V3 (validators-exit) and V4 (exit-validators) have different commands, the page uses Tabs to show both versions in one place.

New pages

Becoming a Vault Operator — what a Vault is, why operate one, earnings, costs, responsibilities
StakeWise vs. Native Staking — what StakeWise adds on top of native staking for operators and depositors

Modified pages

Launch Operator Service V4 (Overview, Prerequisites, Installation, Validators Manager, Start Operator)

Open Questions

1. Guides section — who is the audience?

Currently Guides mixes staker-facing content (Staking, DeFi/Boost, Unstaking) with operator-facing content (Fee Splitter, Running a Vault). Two directions to consider:

Keep Guides for stakers only.
Keep Guides as a mixed section but make the split intentional — e.g. rename to "How-To Guides" and organize by persona (Staker / Operator subsections). The Vault creation guide could live here as a lightweight UI walkthrough, while the Operator section covers the technical infrastructure setup.
Operator Service V3 — long-term approach

2. Operator Service V3 — long-term approach.
The current approach (V3 as a subfolder with only distinct files, sharing common pages with V4) works but has trade-offs.

…es and a call to action

…here to start: Create Your Vault, Operator Service V4 (overview,prerequisites, installation, validator kays, validators manager), Relayer (API Mode)

… broken links

vercel · 2026-03-26T13:34:17Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Error		Apr 1, 2026 0:26am

…lure

operator/stakewise-vs-native-staking.mdx

tsudmi · 2026-03-27T12:44:30Z

operator/introduction.mdx

+
+Your costs depend on whether you run your own node or delegate operations to a third party. If you run the node yourself:
+
+- **Infrastructure** — Hardware requirements are an ever-evolving target. As of March 2026, running a node requires a dedicated machine with at least 64 GB, a 4TB SSD, and a stable internet connection. You can use a pre-built staking hardware (from ~€2,000 for plug-and-play devices such as [Home x StakeWise Pro ↗](https://shop.dappnode.io/product/home-x-stakewise-pro/)) or a cloud server if you don't want to deal with building and maintaining your own physical computer.


Suggested change

- **Infrastructure** — Hardware requirements are an ever-evolving target. As of March 2026, running a node requires a dedicated machine with at least 64 GB, a 4TB SSD, and a stable internet connection. You can use a pre-built staking hardware (from ~€2,000 for plug-and-play devices such as [Home x StakeWise Pro ↗](https://shop.dappnode.io/product/home-x-stakewise-pro/)) or a cloud server if you don't want to deal with building and maintaining your own physical computer.

- **Infrastructure** — Hardware requirements are an ever-evolving target. As of March 2026, running a node requires a dedicated machine with at least 64 GB, a 4TB SSD, and a stable internet connection. You can use a pre-built staking hardware i.e. [Home x StakeWise Pro ↗](https://dappnode.com/collections/staking-collection/products/dappnode-home-x-stakewise-pro) or a cloud server if you don't want to deal with building and maintaining your own physical computer.

tsudmi · 2026-03-27T12:51:12Z

operator/introduction.mdx

+
+## Who Operates Vaults Today
+
+Vault operators range from solo stakers running a single private Vault to professional node operators and institutions managing thousands of ETH. StakeWise infrastructure powers staking products for partners like [MetaMask ↗](https://metamask.io/) and [Chorus One ↗](https://chorus.one/).


Better link to case studies in blog

operator/where-to-start-create-your-vault.mdx

tsudmi · 2026-03-27T12:52:23Z

operator/launch-operator-service-v4.mdx

+
+import Image from '@theme/IdealImage'
+
+# Launch Operator Service V4


Suggested change

# Launch Operator Service V4

# Launch Operator Service

tsudmi · 2026-03-28T06:27:01Z

operator/manage-vault/fee-splitter.mdx

+:::custom-warning[V4 Only]
+Fee Splitter is only available for Operator Service V4. [Upgrade →](/operator/operator-service-v3/v4-upgrade-guide)
+:::


Remove this

tsudmi · 2026-03-28T06:28:20Z

operator/manage-validators/manual-exit.mdx

@@ -0,0 +1,75 @@
+---
+title: Manual Exit


Manually Exit Validators

tsudmi · 2026-03-28T06:30:12Z

operator/installation.mdx

    ```

-    Run commands with:
+    Run commands from inside the `v3-operator` folder using this format:


Suggested change

Run commands from inside the `v3-operator` folder using this format:

Run commands using this format:

tsudmi · 2026-03-28T06:34:08Z

operator/manage-validators/monitoring.mdx

@@ -1,7 +1,7 @@
 ---
 title: Monitoring


Rename to Operator Monitoring and move it after 8. Start Operator in sidebar

tsudmi · 2026-03-28T06:36:01Z

operator/smoothing-pool-relays.mdx

-import Admonition from '@theme/Admonition';
-import useBaseUrl from '@docusaurus/useBaseUrl';
-
 # Smoothing Pool Relays


Move it after Operator Monitoring in sidebar

ulieth added 9 commits March 18, 2026 19:24

Restructure operator documentation navigation

cbb085b

updated Where to Start: Operator Sservice section

a4917d5

Update Where to Start: Operator Service section

ba57df4

updated Where to start:... section with details operator service duti…

431e20d

…es and a call to action

Updated the Create your Vault guide

d3db773

Added a new checklist component and updated the following sections: W…

6eebbe2

…here to start: Create Your Vault, Operator Service V4 (overview,prerequisites, installation, validator kays, validators manager), Relayer (API Mode)

Updated Start Operator file in the Launch Operator Service V4

35ab5f1

Restructure operator docs: consolidate V3, reorganize navigation, fix…

b4a818e

… broken links

Resolved conflicts with main and updated guides section

dfcaaff

Fix duplicate description in Obol setup frontmatter causing build fai…

7fc6a2a

…lure

vercel bot had a problem deploying to Preview March 26, 2026 13:37 Failure

Fix prerequisites filename case to match sidebar

9466a77

vercel bot deployed to Preview March 26, 2026 13:45 View deployment

restructure operator docs navigation + fixed broken links

3d08aae

vercel bot deployed to Preview March 27, 2026 15:23 View deployment

resolved conflicts with main

79a1f3e

vercel bot deployed to Preview March 27, 2026 18:41 View deployment

tsudmi reviewed Mar 28, 2026

View reviewed changes

[docs/restructure-navigation] fix custom link component

2384de8

vercel bot deployed to Preview March 30, 2026 09:14 View deployment

[docs/restructure-navigation] fix custom link component 2

b59fd4b

vercel bot deployed to Preview March 30, 2026 09:17 View deployment

update CustomLink component to use Docusaurus Link

5a48ec0

vercel bot had a problem deploying to Preview April 1, 2026 12:26 Failure

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Docs/restructure navigation#75

Docs/restructure navigation#75
ulieth wants to merge 16 commits intomainfrom
docs/restructure-navigation

ulieth commented Mar 26, 2026 •

edited

Loading

Uh oh!

vercel bot commented Mar 26, 2026 •

edited

Loading

Uh oh!

Uh oh!

tsudmi Mar 27, 2026

Uh oh!

tsudmi Mar 27, 2026

Uh oh!

Uh oh!

tsudmi Mar 27, 2026

Uh oh!

tsudmi Mar 28, 2026

Uh oh!

tsudmi Mar 28, 2026

Uh oh!

tsudmi Mar 28, 2026

Uh oh!

tsudmi Mar 28, 2026

Uh oh!

tsudmi Mar 28, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants


		Your costs depend on whether you run your own node or delegate operations to a third party. If you run the node yourself:

		- Infrastructure — Hardware requirements are an ever-evolving target. As of March 2026, running a node requires a dedicated machine with at least 64 GB, a 4TB SSD, and a stable internet connection. You can use a pre-built staking hardware (from ~€2,000 for plug-and-play devices such as [Home x StakeWise Pro ↗](https://shop.dappnode.io/product/home-x-stakewise-pro/)) or a cloud server if you don't want to deal with building and maintaining your own physical computer.


		## Who Operates Vaults Today

		Vault operators range from solo stakers running a single private Vault to professional node operators and institutions managing thousands of ETH. StakeWise infrastructure powers staking products for partners like [MetaMask ↗](https://metamask.io/) and [Chorus One ↗](https://chorus.one/).


		import Image from '@theme/IdealImage'

		# Launch Operator Service V4

	Run commands from inside the `v3-operator` folder using this format:
	Run commands using this format:

Conversation

ulieth commented Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vercel bot commented Mar 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

tsudmi Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

tsudmi Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

tsudmi Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

tsudmi Mar 28, 2026

Choose a reason for hiding this comment

Uh oh!

tsudmi Mar 28, 2026

Choose a reason for hiding this comment

Uh oh!

tsudmi Mar 28, 2026

Choose a reason for hiding this comment

Uh oh!

tsudmi Mar 28, 2026

Choose a reason for hiding this comment

Uh oh!

tsudmi Mar 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

ulieth commented Mar 26, 2026 •

edited

Loading

vercel bot commented Mar 26, 2026 •

edited

Loading

tsudmi Mar 28, 2026 •

edited

Loading