Frequently Asked Questions

JekyllHub is a curated marketplace for Jekyll themes — both free open source themes from GitHub and premium themes built by independent developers. You can browse, preview, and download themes for blogs, portfolios, documentation sites, landing pages, and more.

Yes. Browsing and discovering themes on JekyllHub is completely free. Free themes cost nothing to download. Premium themes have a one-time price set by the theme author, paid directly to them — JekyllHub does not charge a platform fee on top.

Free themes are hand-picked based on quality, active maintenance, GitHub stars, and documentation. We don't list every theme on GitHub — only the ones we'd actually use. Premium themes go through a review for design quality, code standards, and documentation before being listed.

Yes! We welcome submissions from theme creators. Visit the Submit a Theme page to get started. Both free and premium themes are accepted, subject to a quality review.

Yes. All free themes listed on JekyllHub are open source and available at no cost, typically under the MIT licence. You can use them for personal or commercial projects. Always check the individual theme's licence file for the exact terms.

Each free theme links directly to its GitHub repository. From there you can clone it, fork it, or download a ZIP. The theme's page on JekyllHub also links to the live demo so you can preview it first.

If you're new to Jekyll, check our Installation Guide for step-by-step setup instructions.

Free themes are maintained by their original authors on GitHub. JekyllHub is a discovery platform — we don't fork or re-host the themes. If you have a bug or feature request for a free theme, open an issue on the theme's GitHub repository.

Every premium theme on JekyllHub includes:

• The full theme source code
• A documentation site or README covering installation and configuration
• A licence for use on your own projects
• Updates when Jekyll or its dependencies require changes
• Support from the theme author via email or GitHub Issues

When you click "Buy" on a premium theme, you're taken to the theme author's store — usually Gumroad or LemonSqueezy. The payment is processed there and the theme files are delivered directly to you. JekyllHub is not involved in the transaction.

Yes. Premium themes are updated when there are breaking changes in Jekyll or its dependencies, and when bug fixes or improvements are made. How you receive updates depends on the platform — Gumroad and LemonSqueezy both notify you by email when a new version is available.

Licence terms vary by theme. Most single-purchase licences cover one site. Some authors offer extended licences for multiple sites or client use. Check the theme's listing or documentation for the specific licence terms before purchasing.

It depends on the theme's licence. Many themes allow client use with a single purchase; others require an extended licence. This is stated on the theme's detail page. When in doubt, contact the theme author directly before starting the project.

A basic understanding of the command line and editing text files goes a long way. You don't need to know Ruby or deep web development — most configuration is done in _config.yml and Markdown files. Our Installation Guide walks you through everything from scratch.

GitHub Pages is the simplest option — free, with automatic builds every time you push. It works well for most free themes and simpler premium themes.

Netlify or Cloudflare Pages give you more control — custom build commands, environment variables, and faster builds. Recommended for premium themes that use plugins not supported by GitHub Pages.

The steps vary slightly by theme, but the general process is: clone or download the theme, run bundle install, edit _config.yml with your details, and run bundle exec jekyll serve to preview locally.

See our full Installation Guide for detailed instructions covering GitHub Pages, Netlify, and custom domains.

Most themes target Jekyll 4.x, which is the current stable version. Free themes hosted on GitHub Pages may target Jekyll 3.9.x due to platform restrictions. Each theme's detail page notes the Jekyll version it requires.

Refund policies are set by each theme author. Most offer a refund within 14–30 days if the theme has a critical bug that isn't fixed in a reasonable timeframe, or if the theme is materially different from its description.

Because digital products can be copied, most authors do not offer refunds simply because you changed your mind after downloading. Read the refund policy on the purchase page before buying.

If you have a dispute you can't resolve with the author, contact us and we'll do our best to help.

Each premium theme has a support channel listed on its detail page — usually email or GitHub Issues. Reach out to the theme author directly for installation help, bug reports, or customisation questions.

If you're struggling to reach an author or the support channel is unresponsive, let us know at hello@jekyllhub.com.

Free themes are maintained by their authors on GitHub. Open an issue on the theme's GitHub repository for bug reports or questions. Many popular themes also have community forums or Discord servers.

You can reach us at hello@jekyllhub.com for anything not covered here — partnership enquiries, theme submissions, or feedback. We aim to reply within 2 business days.