Deploy a Jekyll site
Jekyll is an open-source framework for creating websites, based around Markdown with Liquid templates. In this guide, you will create a new Jekyll application and deploy it using Cloudflare Pages. You use the
jekyll CLI to create a new Jekyll site.
Jekyll is written in Ruby, meaning that you will need a functioning Ruby installation, like
rbenv, to install Jekyll.
$ rbenv install 2.7.2
With Ruby installed, you can install the
jekyll Ruby gem:
$ gem install jekyll
Creating a new project
With Jekyll installed, you can create a new project running the
jekyll new in your terminal:
$ jekyll new my-jekyll-site
Create a base
index.html in your newly created folder to give your site content:
<!DOCTYPE html><html><head><meta charset="utf-8" /><title>Hello from Cloudflare Pages</title></head><body><h1>Hello from Cloudflare Pages</h1></body></html>
Before you continue
Creating a GitHub repository
$ git remote add origin https://github.com/yourgithubusername/githubrepo$ git branch -M main$ git push -u origin main
If you are migrating an existing Jekyll project to Pages, confirm that your
Gemfile is committed as part of your codebase. Pages will look at your Gemfile and run
bundle install to install the required dependencies for your project, including the
Deploying with Cloudflare Pages
Deploy your site to Pages by logging into the > Account Home > Pages and selecting Create a project. Select the new GitHub repository that you created and, in the Set up builds and deployments section, provide the following information:
After configuring your site, you can begin your first deployment. You should see Cloudflare Pages installing
jekyll, your project dependencies, and building your site before deploying it.
After deploying your site, you will receive a unique subdomain for your project on
Every time you commit new code to your Jekyll site, Cloudflare Pages will automatically rebuild your project and deploy it. You will also get access to on new pull requests, so you can preview how changes look to your site before deploying them to production.