Fix hidden/broken pages
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90
- Forks
- 92
- Avg merge
- 1h 6m
- Merged PRs (30d)
- 2
Description
There are hidden/broken pages that need to be moved or deleted.
https://docs.yearn.fi/getting-started/products/yvaults/vault-tokens
https://docs.yearn.fi/getting-started/products/ybal/overview
https://docs.yearn.fi/developers/addresses/yprisma-contracts
https://docs.yearn.fi/developers/data-services/yearn-api
https://docs.yearn.fi/developers/security/risks/risk-score-legacy
https://docs.yearn.fi/developers/v2/CONTRACTS_REVIEW
https://docs.yearn.fi/developers/v2/hacking-with-yearn
https://docs.yearn.fi/contributing/governance/governance-and-operations
https://docs.yearn.fi/contributing/governance/proposal-repository
https://docs.yearn.fi/contributing/governance/veyfi
https://docs.yearn.fi/contributing/operations/decision-making
https://docs.yearn.fi/contributing/operations/osc-levels
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking the listed pages under the getting-started, developers, and contributing documentation paths, then inspect the repository structure and links that reference them. Determine for each page whether it should be moved or deleted, and verify the documentation build and navigation after the changes. Done means the listed pages are no longer hidden or broken.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100