Template Catalog and Distribution

Selling or distributing templates is a product business, not a zip file drop. Buyers need to understand who the template is for, what stack it assumes, how to install it, what is included in free versus paid tiers, and how updates work. A public catalog page is the contract: screenshots, honest scope, and a path to support.

What a strong template listing includes

Clear positioning for audience and vertical (blog, marketing site, portfolio). Stack details—Astro version assumptions, EmDash features used, and hosting targets like Cloudflare Pages. Visual proof through representative screenshots across light and dark modes when applicable. Setup steps that a competent developer can follow without your Slack. A changelog so returning customers know what changed between versions.

Concrete rollout steps

1. Package the template like a product. Version it, document breaking changes, and keep a README that mirrors what appears on the public page so GitHub and your site do not diverge.

2. Define pricing and licensing up front. MIT versus proprietary matters for remixing and client work. If you sell a “pro” bundle, list exactly what extra components, sections, or integrations it unlocks.

3. Provide a demo path. A live demo URL or a short screen recording reduces pre-sales friction. If a public demo is not possible yet, offer a downloadable preview build with sample content.

4. Support boundaries. State response times, channels (email, GitHub issues), and what is excluded (custom design work, hosting setup on exotic providers).

5. Plan distribution. GitHub releases, npm packages, or a private customer portal—pick one primary channel and link it prominently.

Example: onboarding a new buyer

Day 0: customer purchases or clones the template. Day 1: they follow install steps, run locally, and deploy a staging site. Day 2: they replace placeholder brand assets and connect analytics. Day 3: they launch production with redirects and DNS verified. Your documentation should make that timeline realistic; if step two requires undocumented secrets, fix the docs before marketing harder.

When EmDash runtime matters

Templates that rely on browser editing, dynamic forms, or authenticated workflows may assume the full EmDash CMS runtime. Call that out early so static-only buyers do not hit a wall after purchase.

Outcome

Template creators earn trust, reduce refund pressure, and build a repeatable revenue or distribution channel around EmDash—not one-off favors disguised as products.