Invoice Template Marketplace

[Kingsman-99]

Description

Creators repeatedly build similar invoice structures from scratch without a way to discover or reuse templates that others have made public. This issue creates an invoice template marketplace at /templates/marketplace where users can publish their saved templates with a title, description, and category tag, browse and preview templates published by others, and clone a marketplace template into their own template library. The marketplace must be moderated: templates go through a brief review status before appearing publicly.

Technical Context

Add app/templates/marketplace/page.tsx as a paginated gallery using server-side rendering for SEO. Implement app/api/templates/marketplace/route.ts for GET (paginated, filterable by category) and POST (submit for review). Extend the templates data model with { isPublic, reviewStatus: 'pending'|'approved'|'rejected', publishedAt, cloneCount }. Build components/templates/MarketplaceCard.tsx displaying preview thumbnail (render invoice structure as a condensed card), creator alias, clone count, and category badge. The clone action calls POST /api/templates/[id]/clone which deep-copies the template into the requesting user's library. Add an admin-only review queue at app/admin/templates/review/page.tsx gated by a role check. Use next/image with a placeholder skeleton for card thumbnails.

Acceptance Criteria

• Submitting a template for publication creates a pending review record and shows the creator a confirmation with review status tracking
• The marketplace gallery renders templates with approved status only; pending and rejected templates are never visible to other users
• Cloning a marketplace template creates an exact copy in the user's template library with a (cloned) suffix and increments the source template's cloneCount
• Category filtering narrows the gallery in under 200 ms (server-side query, not client-side)
• The admin review page lists pending templates with approve/reject actions that update review status and notify the submitter via the activity feed (issue 4)
• All CI checks (npm test, npm run build, ESLint/TypeScript) pass and the branch has no merge conflicts

---

[Baytizz]

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

I have reviewed the issue description and can perfectly fixed it in no time

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

[goldemaverick-ui]

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

I would like to work on this issue

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @goldemaverick-ui as part of the Stellar Wave Program's 7th Wave 🥳

😎 @goldemaverick-ui: You earned 200 Points for completing this issue! After the current Wave ends, 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.