There are two ways to create a new repository for this theme:
- Using the Chirpy Starter - Easy to upgrade, isolates irrelevant project files so you can focus on writing.
- Forking on GitHub - Convenient for custom development, but difficult to upgrade. Unless you are familiar with Jekyll and are determined to tweak or contribute to this project, this approach is not recommended.
Create a new repository from the Chirpy Starter and name it
GH_USERNAME represents your GitHub username.
Fork Chirpy on GitHub and rename it to
<GH_USERNAME>.github.io. Please note that the default branch code is in development. If you want the site to be stable, please switch to the latest tag and start writing.
And then execute:
1 $ bash tools/init.sh
If you don’t want to deploy your site on GitHub Pages, append option
--no-ghat the end of the above command.
The above command will:
- Removes some files or directories from your repository:
- files under
If the option
--no-ghis provided, the directory
.githubwill be deleted. Otherwise, set up the GitHub Action workflow by removing the extension
.github/workflows/pages-deploy.yml.hook, and then remove the other files and directories in the folder
- Creates a new commit to save the changes automatically.
Before running for the first time, go to the root directory of your site, and install dependencies as follows:
1 $ bundle
Update the variables of
_config.yml as needed. Some of them are typical options:
If you need to customize the stylesheet, copy the theme’s
assets/css/style.scss to the same path on your Jekyll site, and then add the custom style at the end of the style file.
v4.1.0, if you want to overwrite the SASS variables defined in
_sass/addon/variables.scss, create a new file
_sass/variables-hook.scss and assign new values to the target variable in it.
Static assets configuration was introduced in version
5.1.0. The CDN of the static assets is defined by file
_data/assets/cross_origin.yml, and you can replace some of them according to the network conditions in the region where your website is published.
Also, if you’d like to self-host the static assets, please refer to the chirpy-static-assets.
You may want to preview the site contents before publishing, so just run it by:
1 $ bundle exec jekyll s
Or run the site on Docker with the following command:
1 2 3 4 $ docker run -it --rm \ --volume="$PWD:/srv/jekyll" \ -p 4000:4000 jekyll/jekyll \ jekyll serve
After a while, the local service will be published at http://127.0.0.1:4000.
Before the deployment begins, check out the file
_config.yml and make sure the
url is configured correctly. Furthermore, if you prefer the project site and don’t use a custom domain, or you want to visit your website with a base URL on a web server other than GitHub Pages, remember to change the
baseurl to your project name that starts with a slash, e.g,
Now you can choose ONE of the following methods to deploy your Jekyll site.
For security reasons, GitHub Pages build runs on
safe mode, which restricts us from using plugins to generate additional page files. Therefore, we can use GitHub Actions to build the site, store the built site files on a new branch, and use that branch as the source of the GitHub Pages service.
Quickly check the files needed for GitHub Actions build:
Ensure your Jekyll site has the file
.github/workflows/pages-deploy.yml. Otherwise, create a new one and fill in the contents of the sample file, and the value of the
on.push.branchesshould be the same as your repo’s default branch name.
Ensure your Jekyll site has file
tools/deploy.sh. Otherwise, copy it from here to your Jekyll site.
Furthermore, if you have committed
Gemfile.lockto the repo, and your runtime system is not Linux, don’t forget to update the platform list in the lock file:
$ bundle lock --add-platform x86_64-linux
After the above steps, rename your repository to
<GH_USERNAME>.github.io on GitHub.
Now publish your Jekyll site by:
Push any commit to remote to trigger the GitHub Actions workflow. Once the build is complete and successful, a new remote branch named
gh-pageswill appear to store the built site files.
Browse to your repository on GitHub. Select the tab Settings, then click Pages in the left navigation bar, and then in the section Source of GitHub Pages, select the
/(root)directory of branch
gh-pagesas the publishing source. Remember to click Save before leaving.
Visit your website at the address indicated by GitHub.
On self-hosted servers, you cannot enjoy the convenience of GitHub Actions. Therefore, you should build the site on your local machine and then upload the site files to the server.
Go to the root of the source project, and build your site as follows:
1 $ JEKYLL_ENV=production bundle exec jekyll b
Or build the site on Docker:
1 2 3 4 5 $ docker run -it --rm \ --env JEKYLL_ENV=production \ --volume="$PWD:/srv/jekyll" \ jekyll/jekyll \ jekyll build
Unless you specified the output path, the generated site files will be placed in folder
_site of the project’s root directory. Now you should upload those files to the target server.
It depends on how you use the theme:
If you are using the theme gem (there will be
gem "jekyll-theme-chirpy"in the
Gemfile), editing the
Gemfileand update the version number of the theme gem, for example:
- gem "jekyll-theme-chirpy", "~> 3.2", ">= 3.2.1" + gem "jekyll-theme-chirpy", "~> 3.3", ">= 3.3.0"
And then execute the following command:
$ bundle update jekyll-theme-chirpy
As the version upgrades, the critical files (for details, see the Startup Template) and configuration options will change. Please refer to the Upgrade Guide to keep your repo’s files in sync with the latest version of the theme.
If you forked from the source project (there will be
Gemfileof your site), then merge the latest upstream tags into your Jekyll site to complete the upgrade. The merge is likely to conflict with your local modifications. Please be patient and careful to resolve these conflicts.