Add Enso zap/router integration docs and partner template guidance
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90
- Forks
- 92
- Avg merge
- 1h 6m
- Merged PRs (30d)
- 2
Description
Summary
Add Enso zap/router integration guidance to the docs, and consider including a reusable partner integration template for external distribution/frontends.
Motivation
Distribution partners should have a clearer path to enabling zap deposits into Yearn vaults on their frontends.
Proposed changes
- document Enso zap and router integration basics in the docs
- add or link a partner-facing integration template / dev-doc example
- clarify the minimum requirements for enabling zap deposits into Yearn vaults
Acceptance criteria
- docs explain the Enso zap/router integration path clearly
- partner-facing implementation guidance exists in a reusable form
- a frontend/distribution partner can understand how to support zap deposits into Yearn vaults
Tracker
- To-do ID: T-008
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 locating the documentation sections covering vault deposits and integration guidance, then identify where Enso zap/router basics and a partner-facing template would fit. Done means the docs clearly explain the integration path, minimum requirements, and reusable guidance for frontend or distribution partners.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100