How to Sell a Jekyll Theme: A Complete Guide for Developers
A step-by-step guide to building, packaging, and selling Jekyll themes — where to sell, how to price, what buyers expect, and how to handle support.
Building a great Jekyll theme is one thing. Turning it into a product people will pay for is another. This guide covers everything — from what buyers expect to how to handle support — based on what works in the Jekyll theme marketplace in 2026.
Is there a market for Jekyll themes?
Yes, but it is a niche one. Jekyll has a dedicated, technical user base that values quality over quantity. Buyers are typically developers, technical writers, and small businesses who understand what they are paying for.
The upside: buyers in this market are more tolerant of complexity, less likely to expect a point-and-click theme manager, and willing to pay fair prices for well-built themes. The downside: the audience is smaller than WordPress or Webflow.
A good premium Jekyll theme priced at $29–$49 with minimal marketing can realistically earn $200–$1,000/month from a marketplace. The ceiling is higher with traffic from your own audience or SEO.
What makes a sellable Jekyll theme
1. A genuine use case
The best-selling themes solve a specific problem for a specific audience. “A clean blog theme” competes with hundreds of free options. “A documentation theme for developer tools with versioned sidebars and dark mode” has a clearly defined buyer.
Before you build, ask: who buys this, and why would they pay instead of using a free alternative?
2. Real demo content
Buyers make decisions based on the demo. A theme with placeholder “Lorem ipsum” text and grey boxes looks unfinished. Fill your demo with realistic, well-written content that makes the design shine.
3. Multiple screenshots
Buyers want to see the theme across contexts: the homepage, a post page, the mobile view, dark mode, and key components. Plan for at least 5–8 high-quality screenshots at 1440×900px.
4. Clean, documented code
Premium buyers will customise your theme. They will read your HTML, SCSS, and Liquid. Code quality matters. Use meaningful class names, comment complex logic, and follow a consistent structure.
5. A _config.yml that does the work
Great themes expose customisation through _config.yml — colours, fonts, nav links, social handles, analytics IDs. Buyers should be able to personalise the theme without touching a single layout file.
# Example theme config
theme_color: "#2563EB"
show_newsletter: true
footer_links:
- title: "Twitter"
url: "https://twitter.com/yourhandle"
- title: "GitHub"
url: "https://github.com/yourhandle"
6. Solid documentation
Write a README that covers: requirements, installation, configuration, customisation, and common questions. Buyers who cannot install your theme will ask for refunds. Good docs prevent support tickets.
How to package your theme for sale
File structure
A well-packaged Jekyll theme includes:
your-theme/
├── _includes/
├── _layouts/
├── _sass/
├── assets/
│ ├── css/
│ ├── js/
│ └── images/
├── _config.yml
├── Gemfile
├── index.html
├── README.md
└── LICENSE.md
The Gemfile
Specify your dependencies explicitly:
source "https://rubygems.org"
gem "jekyll", "~> 4.3"
gem "jekyll-feed"
gem "jekyll-seo-tag"
gem "jekyll-sitemap"
The LICENSE
Most Jekyll themes use the MIT licence for the code, with an extended licence for commercial use. Be explicit about what buyers can and cannot do:
- Can they use the theme on a client project? (Usually yes with an extended licence)
- Can they resell or redistribute the theme? (Usually no)
- Can they use the demo images? (Usually no — stock photos have their own licences)
Demo content
Include sample posts, pages, and data files that demonstrate every feature. The goal is that a buyer can run bundle install && jekyll serve and immediately see a polished demo, not a broken shell.
Where to sell Jekyll themes
JekyllHub
JekyllHub is a dedicated Jekyll theme marketplace — the only one focused exclusively on Jekyll. This means buyers are qualified: they are looking specifically for Jekyll themes, not browsing a general marketplace. Submit your theme at /submit/.
Gumroad
Simple, low-friction digital product sales. You keep 91% of revenue (9% fee). Great for selling directly to your own audience. No approval process.
Lemon Squeezy
Similar to Gumroad with better checkout localisation and VAT handling for European customers. Worth considering if you have international buyers.
Your own site
The highest margin option. A dedicated product page on your own site with a Stripe-powered checkout (via Snipcart, Gumroad embed, or Lemon Squeezy) keeps 95–98% of revenue. Requires you to drive your own traffic.
ThemeForest / Envato
The largest marketplace but extremely competitive and with higher fees. Requires an exclusive or non-exclusive listing decision. Approval takes weeks. Worth it if you want maximum reach; not worth it for a first theme.
Pricing your theme
Jekyll themes typically sell in three tiers:
| Tier | Price | What buyers expect |
|---|---|---|
| Basic | $19–$29 | Clean design, standard features, minimal docs |
| Standard | $39–$59 | Polished design, full features, good docs, 6 months support |
| Extended | $99–$149 | White-label rights, priority support, future updates included |
Do not underprice to compete with free themes. Buyers who choose premium are paying for quality, support, and trust. A $9 premium theme signals low value, not a bargain.
Handling support
Support is where theme sales get complicated. Budget time for it before you launch.
Set expectations upfront: State clearly in your listing what is and is not covered by support. “I will help with installation and configuration issues. I do not customise the theme for individual buyers.”
Create a FAQ page: Document the ten most common questions before launch. Most support requests cover the same ground.
Use GitHub Issues: Keep support conversations in a public Issue tracker where answers are searchable. This reduces repeat questions.
Set a timeline: Respond within 48 business hours. Anything slower leads to chargebacks.
Marketing your theme
Get listed on JekyllHub. Buyers browse theme directories. Being listed is the minimum.
Write a blog post about how you built it. The Jekyll community reads technical content. A behind-the-scenes build post can drive hundreds of qualified visitors.
Tweet the launch. The Jekyll and static site community on Twitter is small but engaged.
SEO the demo. Your live demo site should be indexed by Google. Name the demo something like your-theme-demo.com and optimise the title and description. Searches for “jekyll [niche] theme” will find it.
Offer a free version. A stripped-down free version with a link to the premium version is one of the most effective ways to convert. People try the free, like the structure, and pay to unlock the full version.
Update and maintain your theme
A theme you abandon becomes unsellable. Jekyll versions change, browser behaviour changes, and buyers expect their purchase to keep working.
Commit to a minimum support period (6–12 months) and communicate updates clearly. A Jekyll 4 → 5 migration guide for your theme buyers will generate goodwill and reduce chargeback requests.
The short version
- Build for a specific audience with a clear use case
- Make a polished demo with real content
- Write proper documentation
- List on JekyllHub and Gumroad at minimum
- Price for value, not to undercut free alternatives
- Budget time for support before you launch
The Jekyll theme market is small enough that a high-quality, well-marketed theme can stand out without a large audience. Start there.