blocks|key|440355|text|虽然可以通过分叉新主题将迁移到现有安装，然后在_includes中的CSS、JS、HTML、_layouts和其他您可能需要的文件上手动复制和粘贴资源，但这可能不是一个好主意，因为您最终会将不同名称的旧资源和新资源混在一起，但在这样的情况下(例如，您没有覆盖您的帖子引用的旧样式表)，这可能会导致需要调试和缓慢修复的CSS样式的混合。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|440356|，因为我假设您有一个带有Git的Jekyll安装(如果不是真的应该的话)，您可以创建一个名为new-theme的分支，然后从master切换到该分支作为工作分支。(如果您不想处理Git分支，只需复制整个Jekyll安装并将其粘贴到old-Jekyll-install中即可，这是一种简单的方法(但实际上，您应该这样做)。这里有一个教程帮助我学习)|440357|拉下新主题的文件。|ordered-list-item|440358|手动复制_posts和您的自定义更改。|440359|通过手动比较_config.yml并移动所需的内容，将它们移植到您的上。|440360|构建这个站点，看看你遗漏了什么，哪些可能会搞砸(例如，在过去，您可能为间距添加了一些<br+\>标记，而您不希望在新的主题中这样做)。|440361|与master合并(或将其推向生产)|440362|话虽如此，所有这些都是很费劲的，但至少你不需要处理资源上的冲突。但是，这样做的缺点是您的存储库不会与主题回购同步。这样你就不会得到上游的更新。我仍然建议您使用叉主题回购，将您的个人自定义移植到您的Jekyll站点上，然后为生产重命名该回购。(当然，这将不再使用“现有”Jekyll安装)|440363|entityMap|0|LINK|mutability|MUTABLE|url|https://www.atlassian.com/git/tutorials/using-branches/git-branch^0|2|A|N|9|1A|8|0|0|F|1A|9|1Q|6|37|I|4G|7|0|0|0|4|6|0|6|B|0|16|6|0|1|6|0|13|2W|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|D]|$9|18|A|19|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|D]|$9|1F|A|1G|B|D]|$9|1H|A|1I|B|D]]|E|@$9|1J|A|1K|1|1L]]|F|$]]|$1|I|3|J|5|K|7|1M|8|@]|E|@]|F|$]]|$1|L|3|M|5|K|7|1N|8|@$9|1O|A|1P|B|D]]|E|@]|F|$]]|$1|N|3|O|5|K|7|1Q|8|@$9|1R|A|1S|B|D]]|E|@]|F|$]]|$1|P|3|Q|5|K|7|1T|8|@$9|1U|A|1V|B|D]]|E|@]|F|$]]|$1|R|3|S|5|K|7|1W|8|@$9|1X|A|1Y|B|D]]|E|@]|F|$]]|$1|T|3|U|5|6|7|1Z|8|@$9|20|A|21|B|C]]|E|@]|F|$]]|$1|V|3|-4|5|6|7|22|8|@]|E|@]|F|$]]]|W|$X|$5|Y|Z|10|F|$11|12]]]]

While you could migrate to an existing installation by forking a new theme and then manually copy and pasting over resources like CSS, JS, HTML in the <code>_includes</code>, <code>_layouts</code> and other files you may need, this probably isn't a great idea as you end up having a mash up of old and new resources, which may not be of the same name, but in the scenario that they are (for example you didn't overwrite an old stylesheet that your post references), it will cause mixed up CSS styles that you'll have to debug and slowly fix. 

Since I'm assuming you have a Jekyll install with Git (if you don't you really should), you could create a branch called <code>new-theme</code> and switch to that branch from the <code>master</code> as the working branch. (A simpleton way of having something like this is to just copy your entire Jekyll install and paste it elsewhere as <code>old-Jekyll-install</code> if you don't want to deal with Git branches (but really, you should. <a href="https://www.atlassian.com/git/tutorials/using-branches/git-branch" rel="noreferrer">Here's a tutorial</a> that helped me learn)

<ol>
<li>Pull down the files for the new theme. </li>
<li>Manually copy over <code>_posts</code> and your customized changes. </li>
<li>Port over your <code>_config.yml</code> by manually comparing them and moving over what is necessary.</li>
<li>Build the site and see what you're missing, what might be messed up (for example in the past you might have added a few <code>&lt;br \&gt;</code> tags for spacing and you don't want that in the new theme).</li>
<li>Merge with <code>master</code> (or push it to production)</li>
</ol>

That being said all this is fairly manual and a pain, but at least you won't have to deal with conflicts in resources. The downside of doing this though is that your repository won't be synced with the theme repo. So you won't get upstream updates. I would still suggest that you fork the theme repo, port over your personal customizations for your Jekyll site, and then rename that repo for production. (this would of course no longer be using the 'existing' Jekyll installation)

blocks|key|403975|text|有GH页|type|unstyled|depth|inlineStyleRanges|entityRanges|data|403976|我是测试过这个，但是我在一个项目中完成了它，在这个项目中，我没有任何想要保存的东西，而且主题非常简单，所以随着复杂性的增加，这样的效果可能不太好。|offset|length|403977|为了安全起见，创建一个新分支签出-b新主题|ordered-list-item|403978|然后将新主题添加为远程处理，添加新主题-上游https://github.com:drjekyllthemes/jekyll-minimal-theme.git+git拉动新主题-上游头。|403979|最麻烦的是，你会有一堆合并冲突。检查哪些文件与git+status有合并冲突，希望这些冲突只在您想要覆盖的样式文件中。如果您想保留任何文件，可以使用文本编辑器编辑它们:+git将标记文件中的更改。|style|CODE|403980|推到原点--推原点新主题|403981|转到github上的项目页面，您会注意到如下所示：|403982|📷|atomic|403983|创建一个拉请求并合并新的更改。|403984|您的项目仍将显示为第一个主题的分叉，您将无法为新主题的上游创建拉请求。但是，您可以使用git+pull+new-theme-upstream合并新主题的新更新。|403985|如果您没有使用gh页面，或者在推到github之前在本地构建jekyll+(我认为)|403986|您可以将主题保留在git子模块中，作为单独的文件夹，然后将jekyll的关键元素进行符号链接。这个在盖-页粗糙示例中不起作用|BOLD|403987|blog
%7C
%2B--+theme_1/
%7C
%2B--+theme_2/
%7C++%7C
%7C++%2B--+_layouts/
%7C
%2B--+_layouts+ln+-+theme_2/_layouts|code-block|syntax|javascript|403988|这样，当主题发生变化时，主题就不会发生冲突。|403989|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/radumas/theme-switch-test|1|https://github.com:drjekyllthemes/jekyll-minimal-theme.git|2|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/9b61947ac6ff02a802287807fee185dc.png|imageAlt|3|https://help.github.com/articles/page-build-failed-file-is-a-symlink/^0|0|2|5|0|0|0|M|1M|1|0|N|A|0|0|0|0|1|2|0|0|17|R|0|0|1D|D|1E|3|3|0|0|0|M|0^^$0|@$1|2|3|4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1U|8|@]|9|@$D|1V|E|1W|1|1X]]|A|$]]|$1|F|3|G|5|H|7|1Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|H|7|1Z|8|@]|9|@$D|20|E|21|1|22]]|A|$]]|$1|K|3|L|5|H|7|23|8|@$D|24|E|25|M|N]]|9|@]|A|$]]|$1|O|3|P|5|H|7|26|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|27|8|@]|9|@]|A|$]]|$1|S|3|T|5|U|7|28|8|@]|9|@$D|29|E|2A|1|2B]]|A|$]]|$1|V|3|W|5|H|7|2C|8|@]|9|@]|A|$]]|$1|X|3|Y|5|H|7|2D|8|@$D|2E|E|2F|M|N]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2G|8|@]|9|@]|A|$]]|$1|11|3|12|5|6|7|2H|8|@$D|2I|E|2J|M|13]]|9|@$D|2K|E|2L|1|2M]]|A|$]]|$1|14|3|15|5|16|7|2N|8|@]|9|@]|A|$17|18]]|$1|19|3|1A|5|6|7|2O|8|@$D|2P|E|2Q|M|13]]|9|@]|A|$]]|$1|1B|3|-4|5|6|7|2R|8|@]|9|@]|A|$]]]|1C|$1D|$5|1E|1F|1G|A|$1H|1I]]|1J|$5|1E|1F|1G|A|$1H|1K]]|1L|$5|1M|1F|1N|A|$1O|1P|1Q|-4]]|1R|$5|1E|1F|1G|A|$1H|1S]]]]

<h3>With GH-Pages</h3>

I <a href="https://github.com/radumas/theme-switch-test" rel="nofollow noreferrer">tested this</a>, but I did it with a project where I didn't have anything I wanted to save, and with fairly simple themes, so this might not work so well with the increased complexity.

<ol>
<li>For safety, create a new branch 

<pre><code>git checkout -b newtheme
</code></pre></li>
<li>And then add the new theme as a remote 

<pre><code>git remote add new-theme-upstream https://github.com:drjekyllthemes/jekyll-minimal-theme.git
git pull new-theme-upstream HEAD
</code></pre></li>
<li>The messy part, you're going to have a bunch of merge conflicts. Check which files have merge conflicts with <code>git status</code>, hopefully these conflicts should only be in style files that you want to overwrite. If there any files you want to keep you can either edit them with a text editor: git will have labelled the changes in the file </li>
<li>Push to your origin 

<pre><code>git push origin newtheme
</code></pre></li>
<li>Go to your project's page on github and you'll notice something like this: 
<img src="https://raw.githubusercontent.com/radumas/theme-switch-test/gh-pages/images/Selection_004.png" alt=""> </li>
<li>Create a pull-request and merge the new changes in. </li>
<li>Your project is still going to show as being a fork of the first theme, and you won't be able to create pull-requests for the upstream of the new theme. But you can merge in new updates for your new theme by using <code>git pull new-theme-upstream</code></li>
</ol>

<h3>If you are not using gh-pages or if you are building jekyll locally before pushing to github (I think)</h3>

You could keep your themes in git submodules, as separate folders and then symlink the key elements for jekyll. This won't work in <a href="https://help.github.com/articles/page-build-failed-file-is-a-symlink/" rel="nofollow noreferrer">gh-pages</a> crude example

<pre><code>blog
|
+-- theme_1/
|
+-- theme_2/
| |
| +-- _layouts/
|
+-- _layouts ln - theme_2/_layouts
</code></pre>

That way when changing themes the themes don't collide.

blocks|key|404789|text|这就是我为更改现有Jekyll安装的主题所做的工作。根据您的需要调整这些说明。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|404790|拉出新主题|404791|我们创建一个新的孤儿分支newtheme，并确保它是空的。|offset|length|style|CODE|404792|git+checkout+--orphan+newtheme
git+rm+-rf+.
git+clean+-dfx|code-block|syntax|javascript|404793|然后，我们将主题文件作为上游遥控器添加到其中。在本例中，我使用John的Pixyll主题的master分支。|404794|git+remote+add+upstream+https://github.com/johnotander/pixyll.git
git+fetch+upstream
git+pull+upstream+master|404795|构建主题并测试它。|404796|bundler+install
jekyll+serve|404797|合并您的更改|404798|现在我们合并我们的文章，配置等。您可以使用Git+checkout从旧的Jekyll站点复制文件或文件夹。请注意，如果主题的文件存在，这将覆盖它。|404799|git+checkout+master+--+_posts|404800|或者，您可以以新名称复制文件，例如手动合并文件。|404801|git+show+master:_config.yml+>+_config.yml.old|404802|如果您不小心重写了主题文件，则可以还原它。|404803|git+checkout+upstream/master+--+about.md|404804|以下是我必须复制、合并、调整或删除的文件：|404805|在根文件夹中标记文件。|unordered-list-item|404806|在_posts文件夹中发布。|404807|_drafts文件夹中的草稿。|404808|_config.yml配置文件。|404809|Gemfile创业板文件。|404810|CNAME文件(用于GitHub页面)。|404811|Rakefile+(如果有的话)。|404812|图标文件(如果有的话)。|404813|手动主题更改，如谷歌分析，Disqus，SEO字段(如果有的话)。|404814|提交您的更改，不要忘记再次测试主题。|404815|替换主分支|404816|最后，我们将现有的master分支替换为新的newtheme分支。假设我们在newtheme分支上：|404817|git+checkout+newtheme
git+merge+-s+ours+master
git+checkout+master
git+merge+newtheme|404818|推动变革。|404819|git+push|404820|清理当地的newtheme分支机构。|404821|git+branch+-d+newtheme|404822|就这样!你成功地取代了你的主题。如果我遗漏了什么，或者你有什么要补充的，请留下评论。|404823|更新主题|404824|如果您希望在以后的任何时候更新主题以包括最新的上游更改，只需：|404825|git+pull+upstream+master|404826|并修复任何合并冲突。在这里，我假设upstream远程仍然设置为主题的存储库(您可以使用git+remote+-v来检查这一点)。|404827|entityMap^0|0|0|C|8|0|0|19|6|0|0|0|0|0|P|8|0|0|0|0|0|0|0|0|1|6|0|0|7|0|0|B|0|0|7|0|0|5|0|0|8|0|0|0|0|0|9|6|M|8|12|8|0|0|0|0|5|8|0|0|0|0|0|0|H|8|18|D|0^^$0|@$1|2|3|4|5|6|7|2N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|2P|8|@$F|2Q|G|2R|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|2S|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|2T|8|@$F|2U|G|2V|H|I]]|9|@]|A|$]]|$1|Q|3|R|5|L|7|2W|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|2X|8|@]|9|@]|A|$]]|$1|U|3|V|5|L|7|2Y|8|@]|9|@]|A|$M|N]]|$1|W|3|X|5|6|7|2Z|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|30|8|@$F|31|G|32|H|I]]|9|@]|A|$]]|$1|10|3|11|5|L|7|33|8|@]|9|@]|A|$M|N]]|$1|12|3|13|5|6|7|34|8|@]|9|@]|A|$]]|$1|14|3|15|5|L|7|35|8|@]|9|@]|A|$M|N]]|$1|16|3|17|5|6|7|36|8|@]|9|@]|A|$]]|$1|18|3|19|5|L|7|37|8|@]|9|@]|A|$M|N]]|$1|1A|3|1B|5|6|7|38|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|1E|7|39|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|1E|7|3A|8|@$F|3B|G|3C|H|I]]|9|@]|A|$]]|$1|1H|3|1I|5|1E|7|3D|8|@$F|3E|G|3F|H|I]]|9|@]|A|$]]|$1|1J|3|1K|5|1E|7|3G|8|@$F|3H|G|3I|H|I]]|9|@]|A|$]]|$1|1L|3|1M|5|1E|7|3J|8|@$F|3K|G|3L|H|I]]|9|@]|A|$]]|$1|1N|3|1O|5|1E|7|3M|8|@$F|3N|G|3O|H|I]]|9|@]|A|$]]|$1|1P|3|1Q|5|1E|7|3P|8|@$F|3Q|G|3R|H|I]]|9|@]|A|$]]|$1|1R|3|1S|5|1E|7|3S|8|@]|9|@]|A|$]]|$1|1T|3|1U|5|1E|7|3T|8|@]|9|@]|A|$]]|$1|1V|3|1W|5|6|7|3U|8|@]|9|@]|A|$]]|$1|1X|3|1Y|5|6|7|3V|8|@]|9|@]|A|$]]|$1|1Z|3|20|5|6|7|3W|8|@$F|3X|G|3Y|H|I]|$F|3Z|G|40|H|I]|$F|41|G|42|H|I]]|9|@]|A|$]]|$1|21|3|22|5|L|7|43|8|@]|9|@]|A|$M|N]]|$1|23|3|24|5|6|7|44|8|@]|9|@]|A|$]]|$1|25|3|26|5|L|7|45|8|@]|9|@]|A|$M|N]]|$1|27|3|28|5|6|7|46|8|@$F|47|G|48|H|I]]|9|@]|A|$]]|$1|29|3|2A|5|L|7|49|8|@]|9|@]|A|$M|N]]|$1|2B|3|2C|5|6|7|4A|8|@]|9|@]|A|$]]|$1|2D|3|2E|5|6|7|4B|8|@]|9|@]|A|$]]|$1|2F|3|2G|5|6|7|4C|8|@]|9|@]|A|$]]|$1|2H|3|2I|5|L|7|4D|8|@]|9|@]|A|$M|N]]|$1|2J|3|2K|5|6|7|4E|8|@$F|4F|G|4G|H|I]|$F|4H|G|4I|H|I]]|9|@]|A|$]]|$1|2L|3|-4|5|6|7|4J|8|@]|9|@]|A|$]]]|2M|$]]

This is what I did to change the theme of an existing Jekyll installation. Adjust these instructions to suit your needs.



<h2>Pull the new theme</h2>

We create a new orphan branch <code>newtheme</code> and ensure it's empty.

<pre class="lang-sh prettyprint-override"><code>git checkout --orphan newtheme
git rm -rf .
git clean -dfx
</code></pre>

Then we pull the theme files into it by adding the theme as an upstream remote. In this example I pull John Otander's Pixyll theme's <code>master</code> branch.

<pre class="lang-sh prettyprint-override"><code>git remote add upstream https://github.com/johnotander/pixyll.git
git fetch upstream
git pull upstream master
</code></pre>

Build the theme and test it.

<pre class="lang-sh prettyprint-override"><code>bundler install
jekyll serve
</code></pre>

<h2>Merge your changes</h2>

Now we merge our posts, configuration, etc. You can use Git <code>checkout</code> to copy a file or folder from your old Jekyll site. Note that this will overwrite the theme's file if it exists.

<pre class="lang-sh prettyprint-override"><code>git checkout master -- _posts
</code></pre>

Alternatively, you can copy a file under a new name, for example to merge it manually.

<pre class="lang-sh prettyprint-override"><code>git show master:_config.yml &gt; _config.yml.old
</code></pre>

If you accidently overwrote a theme file, you can restore it.

<pre class="lang-sh prettyprint-override"><code>git checkout upstream/master -- about.md
</code></pre>

These are the files I had to copy, merge, adjust or remove:

<ul>
<li>Markdown files in the root folder.</li>
<li>Posts in the <code>_posts</code> folder.</li>
<li>Drafts in the <code>_drafts</code> folder.</li>
<li>The <code>_config.yml</code> configuration file.</li>
<li>The <code>Gemfile</code> gem file.</li>
<li>The <code>CNAME</code> file (for GitHub pages).</li>
<li>The <code>Rakefile</code> (if any).</li>
<li>The favicon files (if any).</li>
<li>Manual theme changes such as Google Analytics, Disqus, SEO fields (if any).</li>
</ul>

Commit your changes, and don't forget to test the theme again.

<h2>Replace the master branch</h2>

Finally we replace our existing <code>master</code> branch with the new <code>newtheme</code> branch. Assuming we're on the <code>newtheme</code> branch:

<pre class="lang-sh prettyprint-override"><code>git checkout newtheme
git merge -s ours master
git checkout master
git merge newtheme
</code></pre>

Push the changes.

<pre class="lang-sh prettyprint-override"><code>git push
</code></pre>

And clean up the local <code>newtheme</code> branch.

<pre class="lang-sh prettyprint-override"><code>git branch -d newtheme
</code></pre>

That's it! You've successfully replaced your theme. If there's anything I missed, or you have anything to add, please leave a comment.

<hr>

<h2>Updating the theme</h2>

If at any later point you want to update the theme to include the latest upstream changes, simply:

<pre class="lang-sh prettyprint-override"><code>git pull upstream master
</code></pre>

And fix any merge conflicts. Here I assume the <code>upstream</code> remote is still set to the theme's repository (you can check this with <code>git remote -v</code>).

blocks|key|404091|text|Jekyll+v3.2引入了创业板主题+(关于未来的计划，参见这里)：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|404092|基于创业板的主题使得主题开发人员可以很容易地将更新提供给任何拥有主题宝石的人。当有更新时，主题开发人员将更新推到RubyGems
基于创业板的主题的目标是允许您获得一个健壮的、不断更新的主题的所有好处，而不会让所有主题的文件妨碍您的方式，使您的主要关注点变得复杂:创建内容。|blockquote|404093|安装基于宝石的主题很简单：|404094|将主题添加到站点的Gemfile：gem+"jekyll-theme-awesome"|ordered-list-item|style|CODE|404095|安装主题：bundle+install。|404096|在站点的_config.yml中添加以下内容以激活主题：theme:+jekyll-theme-awesome|404097|构建您的站点：bundle+exec+jekyll+serve|404098|为了转换主题，我认为这样的事情应该有效：|404099|更改到站点的Gemfile：gem+"jekyll-theme-new"中的新主题|404100|安装主题：bundle+install|404101|更改站点的_config.yml以引用新主题：theme:+jekyll-theme-new|404102|构建您的站点：bundle+exec+jekyll+serve|404103|(可选-从计算机中卸载旧主题)注意，记下旧主题的安装文件夹(bundle+show+jekyll-theme-awesome)，然后用gem+uninstall+jekyll-theme-awesome卸载它。为了安全起见，请确保其文件夹确实已被删除。|404104|更新基于gem的主题很容易：|404105|如果您有主题gem，您可以(如果愿意)运行bundle+update来更新项目中的所有宝石。或者您可以运行bundle+update+<THEME>，替换为主题名(如minima+)，只更新主题gem。主题开发人员所做的任何新文件或更新(例如样式表或包含)都将自动拖到项目中。|404106|重要注意事项：在撰写本文时，GitHub+pages只支持基于创业板的特定主题集：架构师、开曼、丁基、哈克、Leap+day、Merlot、午夜、Minima、最小、现代派、石板、触觉和时间机器。其中，似乎只有Minima是面向博客的(例如，它是唯一的内置Disqus支持)。但是，如果您愿意使用自己运行Jekyll构建过程，您应该能够使用任何主题。|BOLD|404107|另一种选择是GitLab页面+(教程，样点)。|404108|entityMap|0|LINK|mutability|MUTABLE|url|https://jekyllrb.com/news/2016/07/26/jekyll-3-2-0-released/|1|https://jekyllrb.com/docs/themes/|2|https://github.com/jekyll/jekyll/issues/5434|3|https://pages.github.com/themes/|4|https://4brunu.github.io/blog/2017/01/29/using-jekyll-gem-based-themes-on-github-pages|5|https://about.gitlab.com/features/pages/|6|https://docs.gitlab.com/ee/user/project/pages/getting_started_part_four.html|7|https://gitlab.com/pages/jekyll^0|0|B|0|E|5|1|V|2|2|0|0|0|H|Q|0|5|E|0|4|B|S|R|0|7|O|0|0|E|M|0|5|E|0|5|B|N|N|0|7|O|0|U|W|1V|Y|0|0|L|D|1H|L|2B|6|0|0|6|T|B|3|44|E|4|0|6|8|5|G|2|6|J|2|7|0^^$0|@$1|2|3|4|5|6|7|20|8|@]|9|@$A|21|B|22|1|23]|$A|24|B|25|1|26]|$A|27|B|28|1|29]]|C|$]]|$1|D|3|E|5|F|7|2A|8|@]|9|@]|C|$]]|$1|G|3|H|5|6|7|2B|8|@]|9|@]|C|$]]|$1|I|3|J|5|K|7|2C|8|@$A|2D|B|2E|L|M]]|9|@]|C|$]]|$1|N|3|O|5|K|7|2F|8|@$A|2G|B|2H|L|M]]|9|@]|C|$]]|$1|P|3|Q|5|K|7|2I|8|@$A|2J|B|2K|L|M]|$A|2L|B|2M|L|M]]|9|@]|C|$]]|$1|R|3|S|5|K|7|2N|8|@$A|2O|B|2P|L|M]]|9|@]|C|$]]|$1|T|3|U|5|6|7|2Q|8|@]|9|@]|C|$]]|$1|V|3|W|5|K|7|2R|8|@$A|2S|B|2T|L|M]]|9|@]|C|$]]|$1|X|3|Y|5|K|7|2U|8|@$A|2V|B|2W|L|M]]|9|@]|C|$]]|$1|Z|3|10|5|K|7|2X|8|@$A|2Y|B|2Z|L|M]|$A|30|B|31|L|M]]|9|@]|C|$]]|$1|11|3|12|5|K|7|32|8|@$A|33|B|34|L|M]]|9|@]|C|$]]|$1|13|3|14|5|K|7|35|8|@$A|36|B|37|L|M]|$A|38|B|39|L|M]]|9|@]|C|$]]|$1|15|3|16|5|6|7|3A|8|@]|9|@]|C|$]]|$1|17|3|18|5|F|7|3B|8|@$A|3C|B|3D|L|M]|$A|3E|B|3F|L|M]|$A|3G|B|3H|L|M]]|9|@]|C|$]]|$1|19|3|1A|5|6|7|3I|8|@$A|3J|B|3K|L|1B]]|9|@$A|3L|B|3M|1|3N]|$A|3O|B|3P|1|3Q]]|C|$]]|$1|1C|3|1D|5|6|7|3R|8|@]|9|@$A|3S|B|3T|1|3U]|$A|3V|B|3W|1|3X]|$A|3Y|B|3Z|1|40]]|C|$]]|$1|1E|3|-4|5|6|7|41|8|@]|9|@]|C|$]]]|1F|$1G|$5|1H|1I|1J|C|$1K|1L]]|1M|$5|1H|1I|1J|C|$1K|1N]]|1O|$5|1H|1I|1J|C|$1K|1P]]|1Q|$5|1H|1I|1J|C|$1K|1R]]|1S|$5|1H|1I|1J|C|$1K|1T]]|1U|$5|1H|1I|1J|C|$1K|1V]]|1W|$5|1H|1I|1J|C|$1K|1X]]|1Y|$5|1H|1I|1J|C|$1K|1Z]]]]

<a href="https://jekyllrb.com/news/2016/07/26/jekyll-3-2-0-released/" rel="noreferrer">Jekyll v3.2</a> introduced <a href="https://jekyllrb.com/docs/themes/" rel="noreferrer">gem-based themes</a> (for future plans see <a href="https://github.com/jekyll/jekyll/issues/5434" rel="noreferrer">here</a>):

<blockquote>
 Gem-based themes make it easy for theme developers to make updates
 available to anyone who has the theme gem. When there’s an update,
 theme developers push the update to RubyGems
 
 The goal of gem-based themes is to allow you to get all the benefits
 of a robust, continually updated theme without having all the theme’s
 files getting in your way and over-complicating what might be your
 primary focus: creating content.
</blockquote>

Installing a gem-based theme is simple:

<ol>
<li>Add the theme to your site’s Gemfile: <code>gem "jekyll-theme-awesome"</code></li>
<li>Install the theme: <code>bundle install</code>.</li>
<li>Add the following to your site’s <code>_config.yml</code> to activate the theme: <code>theme: jekyll-theme-awesome</code></li>
<li>Build your site: <code>bundle exec jekyll serve</code></li>
</ol>

To switch themes, I believe something like this should work:

<ol>
<li>Change to the new theme in your site’s Gemfile: <code>gem "jekyll-theme-new"</code></li>
<li>Install the theme: <code>bundle install</code></li>
<li>Change you site’s <code>_config.yml</code> to reference the new theme: <code>theme: jekyll-theme-new</code></li>
<li>Build your site: <code>bundle exec jekyll serve</code></li>
<li>(optional - uninstall the old theme from your machine) Note down the old theme's installation folder (<code>bundle show jekyll-theme-awesome</code>) and uninstall it with <code>gem uninstall jekyll-theme-awesome</code>. To be on the safe side, make sure its folder was indeed deleted.</li>
</ol>

Updating gem-based themes is easy:

<blockquote>
 If you have the theme gem, you can (if you desire) run <code>bundle update</code>
 to update all gems in your project. Or you can run <code>bundle update &lt;THEME&gt;</code>, replacing with the theme name, such as <code>minima</code>, to
 just update the theme gem. Any new files or updates the theme
 developer has made (such as to stylesheets or includes) will be pulled
 into your project automatically.
</blockquote>

Important note: at the time of writing, GitHub pages only supports a <a href="https://pages.github.com/themes/" rel="noreferrer">specific set of gem-based themes</a>: Architect, Cayman, Dinky, Hacker, Leap day, Merlot, Midnight, Minima, Minimal, Modernist, Slate, Tactile, and Time machine. Of those, it seems only Minima is blog-oriented (e.g. it's the only one with built-in Disqus support). However, you should be able to use any theme if you are willing to <a href="https://4brunu.github.io/blog/2017/01/29/using-jekyll-gem-based-themes-on-github-pages" rel="noreferrer">run the Jekyll build process yourself</a>. 

Another alternative is <a href="https://about.gitlab.com/features/pages/" rel="noreferrer">GitLab pages</a> (<a href="https://docs.gitlab.com/ee/user/project/pages/getting_started_part_four.html" rel="noreferrer">tutorial</a>, <a href="https://gitlab.com/pages/jekyll" rel="noreferrer">sample site</a>).

blocks|key|404113|text|在现有的或新的jekyll安装中切换主题的最简单方法是使用以下插件：jekyll-远程主题，自2017年11月开始使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|404114|尽管它目前处于测试版，但它工作正常，最重要的是它已经在Github页面上被白名单列出，所以没有必要在本地构建，除非所请求的主题包括不支持的Gems。|404115|因此，对于带有页面和博客的简单网站，您可以直接在Github基础结构上托管和编辑内容，并通过键入新的远程主题的地址来切换站点主题。另一个好处是，在提交其中一个内容之前，您可以使用若干现有主题测试您的内容。|404116|除了更容易切换之外，jekyll-+remote主题方法应该会自动地引入一个新版本的远程主题，只要您做了一个更改，主题的维护者就会有一个新的版本。如果主题的维护者做了一个你不喜欢的根本改变，那么你总是只需要几下键就可以离开一个新的主题。|404117|我有几个jekyll安装，我已经使用它，而不是打算在短期内切换，因为它是最优雅和未来的证明解决方案，暂时。|404118|如果您现有的jekyll安装是纯的(即，您只编辑了页面、帖子、配置)，则切换是无缝的。如果您现有的主题有特殊的布局(例如，和新的主题没有)，那么使用各自布局的页面就会成为孤儿(即，基本html没有特殊格式)。我已经切换了一个已经被广泛编辑过的现有安装，所以我得到了几个孤立的页面，但是我没有得到任何可能与这里讨论的其他方法可能的git合并冲突。|style|BOLD|404119|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/benbalter/jekyll-remote-theme|1|https://github.com/topics/jekyll-theme^0|Y|B|0|0|0|2H|6|1|0|0|0|1P|33|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|H|3|I|5|6|7|18|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|1A|8|@$A|1B|B|1C|N|O]]|9|@]|C|$]]|$1|P|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|Q|$R|$5|S|T|U|C|$V|W]]|X|$5|S|T|U|C|$V|Y]]]]

The easiest way to switch theme in an existing or new jekyll installation is to use the following plugin: <a href="https://github.com/benbalter/jekyll-remote-theme" rel="nofollow noreferrer">jekyll-remote-theme</a>, which is available since November 2017.

Although it is currently in beta, it works fine and most importantly it is already white-listed on Github Pages, so there is no need to build locally, unless the requested theme includes unsupported Gems. 

Therefore, in the case of a simple web site with pages and blog, you can host and edit your content directly on the Github infrastructure and switch your site theme by typing-in the address of the new remote theme. An extra benefit is that you can test your content with <a href="https://github.com/topics/jekyll-theme" rel="nofollow noreferrer">several existing themes</a> before committing to one of them.

In addition to easier switching, the jekyll-remote-theme method should automatically bring-in a new version of the remote theme, as soon as you make a change and there is a new version by the maintainer of the theme. If the maintainer of the theme makes a radical change that you don't like then you are always a few keystrokes away from a new theme.

I have several jekyll installations and I am already employing it without intending to switch in the short term, since it is the most elegant and future proof solution, for the time being.

If your existing jekyll installation is pure (i.e., you have edited only pages, posts, configuration) then the switch is seamless. If your existing theme has special layouts (e.g., splash.html and the new one does not have it) then your pages that employ the respective layout become orphans (i.e., basic html with no special formatting). I have switched an existing installation that had been extensively edited, so I got several orphan pages, but I did not get any of the git merge conflicts that are possible with other methods discussed here.

There are many themes for Jekyll, e.g. <a href="https://github.com/jekyll/jekyll/wiki/Themes" rel="noreferrer">https://github.com/jekyll/jekyll/wiki/Themes</a>.

What is the easiest way to switch to a new theme in an EXISTING Jekyll installation?

Switch theme in an existing Jekyll installation

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

Jekyll有许多主题，例如。在现有的Jekyll安装中，切换到新主题的最简单方法是什么？

问切换现有Jekyll安装中的主题
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问切换现有Jekyll安装中的主题EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问切换现有Jekyll安装中的主题
EN