To fully use all the features of **Chirpy**, you need to copy the other critical files from the theme's gem to your Jekyll site

[inikishev]

Checklist

• I have read and accepted the contributing guidelines.

How did you create the site?

Generated from chirpy-starter

Description

I have successfully followed the tutorial in https://chirpy.cotes.page/posts/getting-started/, by pressing "Use this template". So the readme says this:

When installing the [Chirpy][chirpy] theme through [RubyGems.org][gem], Jekyll can only read files in the folders
_data, _layouts, _includes, _sass and assets, as well as a small part of options of the _config.yml file
from the theme's gem. If you have ever installed this theme gem, you can use the command
bundle info --path jekyll-theme-chirpy to locate these files.

The Jekyll team claims that this is to leave the ball in the user’s court, but this also results in users not being
able to enjoy the out-of-the-box experience when using feature-rich themes.

To fully use all the features of Chirpy, you need to copy the other critical files from the theme's gem to your
Jekyll site. The following is a list of targets:

.
├── _config.yml
├── _plugins
├── _tabs
└── index.html

To save you time, and also in case you lose some files while copying, we extract those files/configurations of the
latest version of the Chirpy theme and the [CD][CD] workflow to here, so that you can start writing in minutes.

I see those files in my repository. Where do I copy them?

Operations you have already tried

I tried copying them to all folders other than themselves but I don't know if it worked or not

Anything else?

No response

[sionalarsen-sys]

Hey! Pretty sure I know the answer to this - you're supposed to copy them from the original Jekyll repo. You'll see where they are by using this command they gave bundle info --path jekyll-theme-chirpy and then copy those files into your blog's repo. I'm still pretty new at this as well so not fully sure.

but if you go here (https://github.com/cotes2020/jekyll-theme-chirpy/tree/master) you'll see there's a lot more folders and files in it than the starter pack they suggest you fork the copy from. Your repo is referring back to this repo for everything that didn't get copied over - I believe this helps with them sending out updates, you'll get them automatically. But git pages prioritizes all the files in your repo before looking at these files, so if you want to change or customize anything, copying their files over and then changing them means your copy takes priority.