Create a developer quickstart guide

[Marvell69]

New contributors need a single document that gets them from a fresh clone to a running local environment. Without this, every new contributor loses hours to setup issues.

Requirements and context

• Create docs/developer-quickstart.md
• Cover: prerequisites (Node 20+, pnpm, Stellar CLI, Freighter), clone and install, environment variables (.env.local template), run dev server, run tests, connect to testnet, common errors and fixes
• Test all instructions on a fresh machine (Windows WSL, macOS, Ubuntu)
• Link prominently from README

Suggested execution

git checkout -b docs/developer-quickstart

• Create quickstart guide
• Verify on fresh environment
• Add .env.local.example file
• Link from README

Example commit message
docs: create frontend developer quickstart guide

[Favourof]

Hi maintainer, I'd like to take on this issue as i'll fully implement what is requested as i'm a full-stack developer with experiences.

[huazhuang80-star]

I have opened PR #258 for this issue. The change is scoped to contributor documentation: a new docs/developer-quickstart.md, a safe .env.local.example, and a prominent README link. I focused on the requested local setup path, Stellar testnet/Freighter notes, validation commands, and common setup issues so new contributors can get from a fresh clone to a running frontend faster.

[GauravKarakoti]

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

Allow me to work on this one

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

[CHKM001]

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

I like the suggestion you made and will defs use that in completing the task
Also I lwk need to start getting points so if you can assign this P!!
Make i run amm jehh
eTa as expected (not typo)

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

[abimbolaalabi]

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

Hi Maintainer! I’m interested in contributing to this task and can ensure timely delivery with clean implementation. I’ve thoroughly read the issue description and understand the expected outcome. I’d love to work on it. Thank You!

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

[cladiousdoff-glitch]

@cladiousdoff-glitch has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd like to work on this issue! I am sure i can solve problems like this

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

[drips-wave]

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

🧑‍💻 @cladiousdoff-glitch: 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 🌊