Repository files navigation

A minimal, sidebar, responsive web design Jekyll theme that focuses on text presentation. Designed to help you easily record and share your knowledge.

Live Demo »

• Localized Layout
• Configurable Theme Mode
• Pinned Posts
• Hierarchical Categories
• Last Modified Date for Posts
• Table of Contents
• Automatically Recommend Related Posts
• Syntax Highlighting
• Mathematical Expressions
• Mermaid Diagram & Flowchart
• Search
• Atom Feeds
• Disqus Comments
• Google Analytics
• GA Pageviews Reporting (Advanced)
• SEO & Performance Optimization

Follow theJekyll Docs to complete the installation ofRuby,RubyGems,Jekyll andBundler. Please note that the version ofRuby must meet the requirements of the theme onRubyGems.org.

There are two ways to get the theme:

• Install from RubyGems - Easy to update, isolate irrelevant project files so you can focus on writing.
• Fork on GitHub - Convenient for custom development, but difficult to update, only suitable for web developers.

Add this line to your Jekyll site'sGemfile:

gem"jekyll-theme-chirpy"

And add this line to your Jekyll site's_config.yml:

theme:jekyll-theme-chirpy

And then execute:

$bundle

Next, go to the installed local theme path:

$cd"$(bundle info --path jekyll-theme-chirpy)"

And then copy the critical files (for details, seestarter project) from the theme's gem to your Jekyll site.

⚠️Watch out for duplicate files!

If your Jekyll site is created by thejekyll new command, there will beindex.markdown andabout.markdown in the root directory of your site. Please be sure to remove them, otherwise they will overwrite theindex.html and_tabs/about.html from this project, resulting in blank or messy pages.

As an alternative, which we recommend, you can create a Jekyll siteusing the starter template to save time copying files from the theme's gem. We've prepared everything you need there!

ForkChirpy on GitHub and then clone your fork to local. (Please note that the default branch code is in development. If you want the blog to be stable, please switch to thelatest tag and start writing.)

Install gem dependencies by:

$bundle

And then execute:

$bash tools/init.sh

Note: If you don't plan to deploy your site on GitHub Pages, append parameter option--no-gh at the end of the above command.

What it does is:

1. Remove some files or directories from your repository:

   • .travis.yml
   • files under_posts
   • folderdocs

2. If you use the--no-gh option, the directory.github will be deleted. Otherwise, setup the GitHub Action workflow by removing the extension.hook of.github/workflows/pages-deploy.yml.hook, and then remove the other files and directories in the folder.github.

3. Automatically create a commit to save the changes.

Update the variables of_config.yml as needed. Some of them are typical options:

• url
• avatar
• timezone
• lang

If you need to customize stylesheet, copy the theme'sassets/css/style.scss to the same path on your Jekyll site, and then add the custom style at the end of the style file.

Starting fromv4.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.

You may want to preview the site contents before publishing, so just run it by:

$bundleexec jekyll s

Or run the site on Docker with the following command:

$ docker run -it --rm \    --volume="$PWD:/srv/jekyll" \    -p 4000:4000 jekyll/jekyll \    jekyll serve

Open a browser and visit tohttp://localhost:4000.

Before the deployment begins, checkout the file_config.yml and make sure theurl is configured correctly. Furthermore, if you prefer theproject site and don't use a custom domain, or you want to visit your website with a base URL on a web server other thanGitHub Pages, remember to change thebaseurl to your project name that starting with a slash, e.g,/project-name.

Now you can choose ONE of the following methods to deploy your Jekyll site.

For security reasons, GitHub Pages build runs onsafe mode, which restricts us from using plugins to generate additional page files. Therefore, we can useGitHub Actions to build the site, store the built site files on a new branch, and use that branch as the source of the GH 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 theworkflow file, and the value of theon.push.branches should be the same as your repo's default branch name.
• Ensure your Jekyll site has filetools/test.sh andtools/deploy.sh. Otherwise, copy them from this repo to your Jekyll site.

And then rename your repository to<GH-USERNAME>.github.io on GitHub.

Now publish your Jekyll site by:

1. Push any commit to remote to trigger the GitHub Actions workflow. Once the build is complete and successful, a new remote branch namedgh-pages will appear to store the built site files.

2. Browse to your repo's landing page on GitHub and select the branchgh-pages as thepublishing source throughSettings →Options →GitHub Pages:

   

3. Visit your website at the address indicated by GitHub.

On platforms other than GitHub, we cannot enjoy the convenience ofGitHub Actions. Therefore, we should build the site locally (or on some other 3rd-party CI platform) and then put the site files on the server.

Go to the root of the source project, build your site by:

$JEKYLL_ENV=production bundleexec jekyll b

Or build the site with Docker by:

$ 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 your web server.

For more details and a better reading experience, please check out thetutorials on the demo site. In the meanwhile, a copy of the tutorial is also available on theWiki. Please note that the tutorials on the demo website or Wiki are based on the latest release, and the features ofmaster branch usually ahead of the documentation.

The old saying, "Two heads are better than one." Consequently, welcome to report bugs, improve code quality or submit a new feature. For more information, seecontributing guidelines.

This theme is mainly built withJekyll ecosystem,Bootstrap,Font Awesome and some other wonderful tools (their copyright information can be found in the relevant files). The avatar and favicon design comes fromClipart Max.

🎉 Thanks to all the volunteers who contributed to this project, their GitHub IDs are onthis list. Also, I won't forget those guys who submitted the issues or unmerged PR because they reported bugs, shared ideas, or inspired me to write more readable documentation.

Last but not least, thankJetBrains for providing the open source license.

If you like this theme or find it helpful, please consider sponsoring me, because it will encourage and help me better maintain the project, I will be very grateful!

This work is published underMIT License.