[about-page][Section] Why we built this (mission)

[Benjtalkshow]

Context

This is the heart of the About page: why the builders directory exists. It should feel like a genuine mission statement, focused on the people who build, not on the Boundless product. Three value points give it structure.

What to build

A WhyWeBuiltThis section: an eyebrow, a heading, a paragraph, and a three-item value list (icon + title + one line each). No data fetching.

Web copy (use exactly this)

• Eyebrow: Why we built this
• Heading: Great products are easy to find. The people who build them are not.
• Paragraph: Every project on Boundless represents months of work by developers, designers, and founders. But while the products get attention, the people behind them often stay invisible. We built this directory to change that: a home where the ecosystem's builders can be discovered, followed, and celebrated for what they ship.
• Value points (title + line):
  1. Visibility — Put builders and their work in front of the whole ecosystem, not just their own network.
  2. Discovery — Help founders, collaborators, and funders find the right people and the projects worth backing.
  3. Recognition — Celebrate the teams turning ideas into real, shipped products on Stellar.

Where files go

• components/about/why-we-built-this.tsx.

How Boundless builds this (reference)

Boundless "value" sections (private repo) pair a SectionHeading (eyebrow + title + description) with a responsive row of feature items, each a small icon in a tinted square, a bold title, and a muted one-line description. Reuse the vendored primitives, do not rebuild:

• components/marketing/section.tsx -> Section, SectionHeading, Eyebrow for the header block.
• components/icons (or lucide-react) for the three value-point icons.
• For the feature-item look, see components/marketing/four-steps.tsx and components/marketing/feature-list-section.tsx already in the repo for the established pattern.

Design system (must follow)

• Read design.md. Use token utilities only. Icons in text-primary-500 on a subtle tinted surface (bg-primary-500/8 or similar token-based tint). Titles use the heading scale; descriptions use text-muted-foreground.
• Content caps at max-w-page.

Out of scope

No stats, no data fetching. Static mission copy only.

Acceptance criteria

• Renders the exact eyebrow, heading, paragraph, and three value points above.
• Uses Section / SectionHeading and the icon library.
• Value points read well on mobile (stack) and desktop (row).
• npm run lint and npm run build pass.
• Screenshot attached to the PR.

References (in this repo)

• components/marketing/section.tsx, components/marketing/four-steps.tsx, components/marketing/feature-list-section.tsx, components/icons, design.md.

[linear]

BOU-334

[coderabbitai]

🔗 Related PRs

#315 - feat: use badge pill for hero eyebrow [merged]
#325 - feat(cards): add BuilderCard component and skeleton [merged]
#328 - #324 [landing-page][Page] Compose landing page and states FIXED [open]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[vj570145-web]

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

After reviewing the requirements, I'm sure I can deliver a solid fix that satisfies all criteria. Please assign this to me.

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

[daameeloolaa-png]

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

Am interested in working on this issue and can start right away. Please assign it to me.

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

[Ayodele06]

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

Hello Maintainer, I have reviewed the requirements thoroughly and can implement the requested changes efficiently. I have experience debugging applications, following coding standards, and submitting high-quality pull requests.

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

[barnabasolutayo-lgtm]

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

Hello maintainer. I can resolve this issue quickly. Please assign to me. Thank you

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

[chigozzdevv]

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

Good day, I’d like to work on this issue.
I’ll build the mission section with the exact provided copy, reuse the existing section and feature patterns, and ensure the three value points display cleanly across mobile and desktop. I’ll also run lint and build checks and attach a screenshot.

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

[OmniZlatoon]

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

Good day sir, Ready to deliver the task A.S.A.P. Gone through the issue and to be honest, i can work the task with the right tools at hand. please assign me maintainer . My eta is 5 hours

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

[od-hunter]

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

Hi can I be assigned this issue please?

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

[drips-wave]

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

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