feat: add localization for Stellar-specific terminology in the UI

[sanmipaul]

Summary

The Astera frontend uses Stellar-specific technical terms (stroops, ledger, Horizon, XLM, Soroban) that are unfamiliar to users coming from Ethereum or traditional finance backgrounds. Adding contextual tooltips or a glossary would reduce confusion and lower the learning curve.

Terms to Explain In-Context

Term	Plain-language explanation
Stroops	The smallest unit of XLM (like satoshis for Bitcoin). 1 XLM = 10,000,000 stroops
Ledger	A single block in Stellar's blockchain. Closes every ~5 seconds
Horizon	Stellar's API server for querying blockchain data
Soroban	Stellar's smart contract platform
TTL	Time-to-live: how long data stays stored on the blockchain
Collateral Ratio	The value of your collateral vs. the amount you borrowed
Factoring Fee	The protocol's fee for facilitating invoice financing

Implementation Options

Option A: Glossary Page

• `/glossary` page with all terms and definitions
• Linked from the footer and help sections

Option B: Inline Tooltips

• Each technical term underlined with a dotted border
• Hover (or tap on mobile) shows a tooltip with the definition

Option C: Both

• Inline tooltips for frequently-used terms on the dashboard
• Full glossary page for comprehensive reference

Acceptance Criteria

• Glossary page at `/glossary` with all 7 terms above
• Top 5 most-used technical terms have inline tooltips on the dashboard
• Tooltips are accessible (keyboard focusable, screen reader compatible)
• Glossary is linked from the footer
• New terms can be added by editing a single `glossary.ts` data file

References

• `frontend/app/`
• `frontend/components/`

[Anichris-koded]

Hi, my name is Koded, and I am an experienced software engineer with a strong focus on frontend development, localization, and user experience design. I specialize in implementing multilingual interfaces and ensuring domain-specific terminology is accurately represented across different languages and regions. My approach to localizing Stellar-specific terminology emphasizes consistency, clarity, and cultural relevance, helping users better understand blockchain concepts while maintaining a seamless and accessible experience throughout the application.

[Lanhubs]

I’d love to take this on! I have strong experience implementing these exact patterns and can deliver a clean, production-ready solution that hits all acceptance criteria.

My approach will focus on writing modular, well-documented code with comprehensive test coverage for both success paths and edge cases.

I'm ready to get started immediately. Could you please assign this to me?

[Lanhubs]

I’d love to take this on! I have strong experience implementing these exact patterns and can deliver a clean, production-ready solution that hits all acceptance criteria.

My approach will focus on writing modular, well-documented code with comprehensive test coverage for both success paths and edge cases.

I'm ready to get started immediately. Could you please assign this to me?

[anidroid1184]

I'd like to work on this issue. I will implement Option C to deliver both the comprehensive /glossary page and the accessible inline tooltips on the dashboard, lowering the learning curve for users.

Following your development guidelines, my technical approach will be:

1. Create a dedicated feature branch: feat/add-glossary-and-tooltips.
2. Create a new data file from scratch at frontend/src/generated/glossary.ts to strongly type and centralize all 7 technical definitions (Stroops, Ledger, Horizon, Soroban, TTL, Collateral Ratio, and Factoring Fee).
3. Build the /glossary route page and link it properly from the footer component.
4. Implement inline tooltips with a dotted underline border for the top 5 most-used technical terms on the dashboard, ensuring full accessibility compliance (keyboard focusable and screen reader compatible).
5. Verify the entire implementation locally inside the frontend directory by running npm run lint and npm run build to ensure zero compilation or styling errors before opening the PR.

I'm ready to begin as soon as you confirm the assignment!

[Mirabel64]

@Mirabel64 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello maintainer. Can I work on this, I can delivery a PR within 24hrs

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mirabel64 to this issue.

[Joseph-1-Duro]

@Joseph-1-Duro has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi, I would love to work on your project.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Joseph-1-Duro to this issue.

[Kaybee973]

@Kaybee973 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

I would like to work on this issue, please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Kaybee973 to this issue.

[Bigg593]

@Bigg593 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

hi maintainer i will like to work on this issue please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Bigg593 to this issue.

[JamesVictor-O]

@JamesVictor-O has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello! I’d love to take on this issue. I’ve reviewed the requirements and have a clear path forward for the implementation. I estimate I can have a PR ready within about 3 hours of being assigned. Could you please assign this to me?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @JamesVictor-O to this issue.

[drips-wave]

Congratulations, @JamesVictor-O! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @JamesVictor-O: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊