[GROWTH] Public campaign discovery marketplace + SEO landing pages

[joelpeace48-cell]

Growth initiative. Net-new, high-priority. Organic acquisition surface.

Why this matters (acquisition)

Today campaigns are only reachable if an operator shares a direct link. There is no discovery surface, so Trivela captures none of the organic/search traffic that compounds growth. A public, SEO-optimized discovery marketplace turns every campaign into an acquisition funnel and makes Trivela itself a destination.

Goal

Build a public campaign discovery marketplace + SEO-optimized, server-rendered campaign/landing pages so new users find and join campaigns organically.

Technical design

• Discovery feed: public /explore listing active campaigns with search/filter/sort (category, ending-soon, popularity), sourced from indexed rollups for speed. Featured/curated slots.
• SEO: server-rendered (or pre-rendered) campaign pages with structured data (JSON-LD Event/Offer), Open Graph/Twitter cards (reuse PageMeta.jsx), sitemap.xml, canonical URLs, and fast LCP (lazy-load heavy chunks).
• Shareability: rich link previews per campaign; "trending" + "new" rails driven by indexed metrics.
• Performance: virtualized lists + cursor pagination over indexed data; CDN-cacheable public pages.

Edge cases

• Private/invite-only campaigns excluded from discovery.
• Spam/abusive campaigns filtered (ties to moderation/abuse review).
• Stale data → show as_of_ledger freshness; CDN invalidation on change.

Task breakdown

• /explore discovery feed (search/filter/sort + featured) over indexed rollups.
• SSR/pre-render campaign + landing pages with JSON-LD + OG/Twitter + sitemap + canonicals.
• Trending/new rails from indexed metrics; CDN caching + invalidation.
• Lighthouse/SEO + Core Web Vitals budget in CI.

Acceptance criteria

• Public campaigns are discoverable/searchable at /explore; campaign pages render rich previews + valid structured data and pass a Lighthouse SEO/perf budget.

Verification

• Lighthouse CI (SEO + perf), structured-data validation, OG-card preview, sitemap correctness.

Dependencies

• Indexed rollups (feat: Materialized analytics rollup tables from indexed events #559) + cursor read API (feat: Public read API over indexed data (cursor-paginated, cached) #560); respects privacy/abuse controls.

Priority: high · Difficulty: hard · Effort: L · growth (acquisition)

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[jaynomyaro]

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

[dolaoluwa574-source]

I’m excited to contribute to impactful software improvements. My experience includes backend engineering, object-oriented programming, API development, Git collaboration, and building scalable, maintainable applications.