Codexse

Making templates is one job; selling them is a different one. A storefront for digital products needs a catalogue two kinds of buyer can navigate — one knows the technology they want, the other only knows the industry they are in — plus accounts, a cart, a checkout, and enough social proof for a stranger to pay for a download from someone they have never heard of. There is no client to sign any of it off, and no one else to build it.

I built it as a Laravel application with a Vite front end, browsable both ways so neither buyer has to translate their question into someone else’s taxonomy. Every listing carries its price, its sales count and its rating, because that is what a first-time visitor actually reads, and a live chat widget sits behind the pre-sale questions that would otherwise end in a closed tab.

• Catalogue browsable by technology — HTML, React, WordPress, Vue — and by industry
• Per-template pricing with discounts, sales counts and ratings on each listing
• Accounts, cart and checkout, plus a live chat widget for pre-sale questions
• A blog and newsletter, because a marketplace has to bring its own traffic

A Laravel application with a Vite-built front end — Tailwind for styling and Alpine for the interactive parts, rather than a single-page framework a catalogue does not need. Fonts are served through Bunny rather than Google, so the store makes no third-party font requests:

• Laravel
• Tailwind CSS
• Alpine.js
• Vite
• Bunny Fonts

Codexse is a running product rather than a finished delivery, and it is where Velour and my other templates are sold. It is also the reason several entries here exist at all: building things to sell to strangers is a different discipline from building to a brief, and the two have made each other better.