Skip to content

Landing page component reference #630

Closed

Description

@codebestia

Branch: Open your PR against dev. PRs targeting main are closed automatically.

Description:
Write apps/web/docs/components-landing.md for src/components/landing/ (Navbar, Hero, Features, HowItWorks, TechStack, CTA, Footer). The landing page makes public claims about the product, so contributors editing it need to know where the copy lives and what it may claim.

Acceptance criteria:

  • Each component's purpose, props (if any), and where its copy and links are defined
  • An accuracy rule: every feature or technology claim must match what is shipped — for example, the Signal protocol is not the live default (Phase1SessionCrypto is) — with the claims that currently overstate listed for correction
  • Documents responsive breakpoints and the dark-mode approach, linking to the styling guide (Upload confirm: verify object presence + size against real storage #346)

Activity

  1. Netty-kun commented on Oct 19, 2026

    @Netty-kun

    @Netty-kun has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello Maintainer, I’m ready to handle this issue. I’ll begin immediately and target a clean, production-ready PR within 1–2 hours.

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

  2. josephchimebuka commented on Oct 20, 2026

    @josephchimebuka
    Contributor

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

    Hi GM, I have reviewed this issue and taken the time to understand the requirements, current implementation, and the expected outcome. Based on my analysis, I believe this is something I can successfully handle and contribute to... Kindly assign

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

  3. drips-wave commented on Oct 20, 2026

    @drips-wave

    Congratulations, @josephchimebuka! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

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

  4. added 2 commits that reference this issue on Oct 22, 2026
  5. github-actions commented on Oct 22, 2026

    @github-actions

    Closed by #683, merged into dev.

  6. drips-wave commented on Oct 22, 2026

    @drips-wave

    This issue has been completed by @josephchimebuka as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @josephchimebuka: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Stellar WaveIssues in the Stellar wave programdocumentationImprovements or additions to documentationfrontend

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions