LadderMine / LadderMine/yieldladder

[NF-41] [FRONTEND] Embeddable Vault Widget

Open
#116 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

frontend
Dominant language
TypeScript
Stars
0
Forks
26
Avg merge
4h 36m
Merged PRs (30d)
8

Description

Overview

There's no way for a third-party site (a partner, an ecosystem directory, a content creator) to embed a live YieldLadder vault card on their own page. This issue builds a small embeddable widget for exactly that.

Problem

The existing vault cards (on the landing page and dashboard) only exist as part of the main Next.js app — there's no standalone, iframe-embeddable version, and no distribution mechanism for third parties to showcase live YieldLadder data on their own sites.

Proposed Solution

  • New route app/src/app/embed/vault/[tier]/page.tsx, rendered with a minimal layout (no nav/footer, just the single vault card) suitable for embedding in an <iframe>.
  • Shows live APY and tier parameters using the same data hooks as the existing dashboard cards.
  • Includes a small "Powered by YieldLadder" attribution link back to the main site.
  • Publish embed instructions (an example <iframe> snippet with configurable width/height) on the /developers page (NF-31).
  • Set appropriate CSP/X-Frame-Options headers so the embed route specifically allows iframing while the rest of the app remains protected against clickjacking.

Acceptance Criteria

  • Embed route renders correctly inside a third-party <iframe> with no layout breakage
  • Live APY data matches what's shown on the main dashboard for the same tier
  • Attribution link is present and correctly points back to the main site
  • Only the embed route allows iframing — the rest of the app's existing frame protection is unaffected
  • Embed instructions are published on /developers (NF-31)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with app/src/app/embed/vault/[tier]/page.tsx and inspect the existing dashboard vault cards and their data hooks for the matching live APY and tier parameters. Review the app's current frame-protection headers before configuring the embed route. Done means the route works in a third-party iframe, includes the attribution link, preserves protection elsewhere, and documents an iframe snippet on /developers.

Written by the indexing model from the issue text.

Assessment

Tech stack
nextjs, typescript
Domain
documentation, frontend, security, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.