Forking vs Cloning: Which Is Better for Jekyll Themes?

By -

What’s the Best Way to Use Jekyll Themes on GitHub Pages: Forking or Cloning?

When you're getting started with building a blog using Jekyll on GitHub Pages, one of the first decisions you'll face is whether to fork or clone a theme repository. This choice affects how you update, customize, and manage your site over time. Especially if you're working with a theme like Mediumish, which is widely used in the blogging community, understanding this decision is crucial.

Understanding Forking and Cloning in GitHub

Forking and cloning are GitHub-specific terms, and while they may sound similar, they serve different purposes. A fork is essentially a copy of someone else's GitHub repository that lives under your own GitHub account. It's often used when you intend to contribute to the original project or maintain your own version of it.

On the other hand, cloning refers to making a local copy of any repository — whether it's yours or someone else's — so you can work on it using Git on your own computer. You can clone a repository without forking it, and vice versa.

Why This Decision Matters When Using Jekyll Themes

When you're setting up a Jekyll-based site with a pre-designed theme like Mediumish, the way you acquire the theme affects:

  • Your ability to update the theme when new versions are released
  • How you structure your GitHub Pages repository
  • Whether you keep your theme separate from your content
  • Your long-term customization flexibility

When Should You Fork a Jekyll Theme Repository?

Forking is often the easiest way to get started if you plan to use the theme "as-is" with minor modifications. When you fork a theme repository on GitHub, you get an exact copy under your own account, and you can instantly enable GitHub Pages to start serving your site.

Advantages of Forking

  • Quick Setup: No need to create a new repo manually.
  • GitHub Pages Ready: Many Jekyll themes are configured to work immediately on GitHub Pages when forked.
  • Easy Updates: You can pull changes from the original (upstream) repository if the theme is updated.
  • Minimal Git Knowledge Required: Especially beginner-friendly if you're not familiar with Git workflows.

Disadvantages of Forking

  • Inherited Structure: You inherit the theme author's entire repo structure, which may include files you don’t need.
  • Customization Conflicts: Updating the upstream version might overwrite your changes if not managed carefully.
  • Not Ideal for Full Redesigns: If you plan to heavily modify the theme, a fork might become hard to maintain over time.

When Should You Clone Instead?

Cloning is the better choice if you're looking for more control. Instead of depending on the original theme’s GitHub structure, you can download the files and integrate them into a custom repo, tailoring it from the ground up.

Advantages of Cloning

  • Clean Separation: You only take what you need. There’s no GitHub fork relationship involved.
  • Full Control: Perfect for advanced users who want to restructure the theme or combine multiple sources.
  • Better for Learning: Helps you understand how each file works within a Jekyll project.

Disadvantages of Cloning

  • No Built-in Upstream: You won’t get automatic update notifications from the original theme author.
  • Requires Git Experience: You’ll need to manage your commits and project structure manually.
  • Manual Setup: You’ll need to ensure GitHub Pages is configured properly in your custom repo.

Using the Mediumish Theme: What’s the Best Path?

Mediumish is a beautiful and minimalist Jekyll theme designed for content creators. Many users fork it and use it out-of-the-box. But as you scale your blog and add features like tags, collections, search, or multilingual support, you might want to move away from the fork and build a custom site using cloned files.

Scenario 1: You’re a Beginner Blogger

If your primary goal is to publish content quickly and you don't want to deal with Git internals, forking is your best option. You can fork Mediumish, update the `_config.yml`, and push content right away.

Scenario 2: You’re a Developer or Tinkerer

If you plan to customize every aspect of your theme, then cloning gives you better long-term flexibility. You can create your own structure, remove unnecessary files, and optimize the layout for performance and SEO.

How to Fork and Set Up a Jekyll Theme

  1. Go to the theme repository (e.g., Mediumish).
  2. Click on the Fork button in the top-right corner of GitHub.
  3. The repository is now copied to your GitHub account.
  4. Go to your forked repo’s settings and enable GitHub Pages from the correct branch and folder.
  5. Modify the `_config.yml` file to reflect your own site title, author, and base URL.

How to Clone and Build Your Own Jekyll Site

  1. Copy the theme’s repository URL.
  2. Run git clone <repo-url> on your local machine.
  3. Remove the .git folder if you don’t want to track the original Git history.
  4. Create a new GitHub repository and push your files into it.
  5. Enable GitHub Pages and adjust the `_config.yml` as needed.

Can You Switch from Forking to Cloning Later?

Yes. Many users start with a fork and switch to a custom clone later once they understand the theme structure better. You can do this by downloading your current repo, deleting the fork connection, and pushing the files to a fresh GitHub repository. This is a great way to transition without starting from scratch.

Which Approach Is More SEO Friendly?

Both approaches can result in SEO-friendly blogs if the content is structured well. However, a cloned setup often gives more control over:

  • HTML markup and schema
  • Asset optimization (scripts, styles, images)
  • Meta tags and canonical URLs

So if SEO is a major concern, cloning might give you the upper hand in the long run.

Conclusion: Forking or Cloning?

The answer depends on your experience level, goals, and how much customization you want. Here’s a quick summary:

  • Forking: Best for beginners who want quick setup and don’t plan to change the theme much.
  • Cloning: Best for developers and power users who want full control and flexibility.

There’s no right or wrong answer. The key is to understand what each method offers and choose based on how you want to grow your site.

Still Not Sure Which One to Pick?

If you're unsure, start with a fork. It's easier to get up and running and helps you learn the ropes. Later, once you're more comfortable with Git, Jekyll, and theme customization, you can always migrate to a cloned version for better flexibility and control.