---
# System prepended metadata

title: Documentation for Prysm V2

---

# Documentation for Prysm V2

## Outline

- Ensure the install/setup guides follow the ideal workflow
    - Prerequisites
    - Setting up eth1 node, being ready before you send out your deposit
    - Prepare your nodes before sending your deposit, this should be emphasized
- Refactor the sidebars to be more standardized
- Prevent confusion around testnet/mainnet, choosing your network
- Check out other docs from similar software to see what we're missing
    - go-ethereum https://geth.ethereum.org/docs/
    - nethermind https://nethermind.io/
- Should we format docs to be flexible to other projects?
- Beacon node has two public interfaces: cli and api
- Validator has three public interfaces: cli, api, and web
- Keep the docs focused on how to run the software. For developers, the docs should be kept separate or in a more maintainable manner
- Validator lifecycle
- Add a tool to list the --help text from prysm.sh on a docs page
- Add the troubleshooting section
- Filing a bug report maybe troubleshooting section
- https://docs.prylabs.network/docs/contribute/required-reading is outdated, linked on https://docs.prylabs.network/docs/introduction/on-ethereum-2/ about sharding
- atempt to remove notions of eth2, ethereum 2

## Questions

- Project groups things together in the docs despite having multiple different components
- Maybe we can have similar docs for each of the components: beacon, validator, slasher