|
| 1 | +# Ecosystem Implementation Todo |
| 2 | + |
| 3 | +## Goal |
| 4 | + |
| 5 | +Build a database-driven `/ecosystem` marketplace and submission flow without blocking the partner-page SEO work. |
| 6 | + |
| 7 | +## Product Goals |
| 8 | + |
| 9 | +- Create an `/ecosystem` directory page that acts like a marketplace |
| 10 | +- Let users sort and filter entries by the fields that actually matter |
| 11 | +- Let companies submit new listings through a first-party submission flow |
| 12 | +- Seed the marketplace with existing TanStack partners when the DB work starts |
| 13 | +- Let TanStack maintainers add an official review and comparisons to each listing |
| 14 | +- Keep partner-backed entries aligned with `/partners/[partner]` pages |
| 15 | + |
| 16 | +## Scope To Build Later |
| 17 | + |
| 18 | +### Data model |
| 19 | + |
| 20 | +- Add a new `ecosystemEntries` table |
| 21 | +- Add a dedicated moderation capability like `moderate-ecosystem` |
| 22 | +- Keep the schema intentionally small and high-value |
| 23 | + |
| 24 | +Suggested v1 fields: |
| 25 | + |
| 26 | +- `id` |
| 27 | +- `userId` |
| 28 | +- `slug` |
| 29 | +- `name` |
| 30 | +- `websiteUrl` |
| 31 | +- `kind` |
| 32 | +- `tags` |
| 33 | +- `libraries` |
| 34 | +- `pricingModel` |
| 35 | +- `isOpenSource` |
| 36 | +- `preferenceScore` |
| 37 | +- `isPartner` |
| 38 | +- `logoUrl` |
| 39 | +- `screenshotUrl` |
| 40 | +- `summary` |
| 41 | +- `officialReviewMd` |
| 42 | +- `competitorSlugs` |
| 43 | +- `status` |
| 44 | +- `moderationNote` |
| 45 | +- `moderatedBy` |
| 46 | +- `moderatedAt` |
| 47 | +- `createdAt` |
| 48 | +- `updatedAt` |
| 49 | + |
| 50 | +### Taxonomy |
| 51 | + |
| 52 | +Use a very small taxonomy surface: |
| 53 | + |
| 54 | +- `kind`: `integration | service | tool | template | plugin` |
| 55 | +- `pricingModel`: `free | freemium | paid | contact | oss` |
| 56 | +- `tags: string[]` absorbs both "type" and "service" |
| 57 | + |
| 58 | +### Comparison model |
| 59 | + |
| 60 | +Use slugs everywhere. |
| 61 | + |
| 62 | +- Partners compare against other partner ids, which are also their slugs |
| 63 | +- Ecosystem entries compare against ecosystem slugs |
| 64 | +- Partner-backed ecosystem entries should reuse the same slug namespace |
| 65 | + |
| 66 | +Suggested v1 field: |
| 67 | + |
| 68 | +- `competitorSlugs: string[]` |
| 69 | + |
| 70 | +No UUID-based comparison references for v1. |
| 71 | +No partner-only comparison system. |
| 72 | +No extra comparison tables unless the simple shape breaks down. |
| 73 | + |
| 74 | +### Canonical URL rules |
| 75 | + |
| 76 | +- Partner-backed entries should be canonical at `/partners/[partner]` |
| 77 | +- Non-partner entries should be canonical at `/ecosystem/[slug]` |
| 78 | +- If a partner-backed entry is reachable from `/ecosystem/[slug]`, redirect or canonicalize to `/partners/[partner]` |
| 79 | + |
| 80 | +### Submission flow |
| 81 | + |
| 82 | +Build a user-facing submission portal similar in spirit to showcase, but for ecosystem listings. |
| 83 | + |
| 84 | +Suggested v1 required fields: |
| 85 | + |
| 86 | +- `name` |
| 87 | +- `websiteUrl` |
| 88 | +- `kind` |
| 89 | +- `tags` |
| 90 | +- `libraries` |
| 91 | +- `pricingModel` |
| 92 | +- `isOpenSource` |
| 93 | +- `logoUrl` |
| 94 | +- `screenshotUrl` |
| 95 | +- `summary` |
| 96 | + |
| 97 | +Maintainer-only fields for v1: |
| 98 | + |
| 99 | +- `preferenceScore` |
| 100 | +- `officialReviewMd` |
| 101 | +- `competitorSlugs` |
| 102 | +- moderation fields |
| 103 | + |
| 104 | +### Admin flow |
| 105 | + |
| 106 | +- Add `/admin/ecosystem` |
| 107 | +- Add `/admin/ecosystem/[id]` |
| 108 | +- Let maintainers moderate submissions |
| 109 | +- Let maintainers edit all listing fields |
| 110 | +- Let maintainers set `preferenceScore` |
| 111 | +- Let maintainers author `officialReviewMd` |
| 112 | +- Let maintainers manage `competitorSlugs` |
| 113 | + |
| 114 | +### Account flow |
| 115 | + |
| 116 | +- Add `/account/ecosystem` |
| 117 | +- Let users view, edit, and delete their own submissions |
| 118 | +- Keep this separate from `/account/integrations`, which already means something else |
| 119 | + |
| 120 | +## Seeding Plan |
| 121 | + |
| 122 | +- Seed existing partners into the ecosystem table when the DB work starts |
| 123 | +- Preserve current partner ids as ecosystem slugs for partner-backed entries |
| 124 | +- Seed `preferenceScore` from the existing `partners[].score` values |
| 125 | +- Start seeded partner entries as `approved` |
| 126 | +- Keep the current score scale and revisit later if needed |
| 127 | + |
| 128 | +## Suggested Implementation Order |
| 129 | + |
| 130 | +1. Add ecosystem capability, enums, and DB schema |
| 131 | +2. Add ecosystem server functions and query options |
| 132 | +3. Seed partner rows into the new table |
| 133 | +4. Build `/ecosystem` index and `/ecosystem/[slug]` |
| 134 | +5. Build `/ecosystem/submit` and edit flows |
| 135 | +6. Build `/account/ecosystem` |
| 136 | +7. Build `/admin/ecosystem` |
| 137 | +8. Add SEO metadata and JSON-LD |
| 138 | +9. Run `pnpm test` |
| 139 | + |
| 140 | +## Notes |
| 141 | + |
| 142 | +- Reuse showcase architecture patterns, not the showcase schema |
| 143 | +- Keep the implementation intentionally small at first |
| 144 | +- Avoid over-modeling comparison data until real usage demands it |
| 145 | +- Partner pages ship first; ecosystem follows later |
0 commit comments