惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

C
Check Point Blog
罗磊的独立博客
量子位
Microsoft Azure Blog
Microsoft Azure Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
J
Java Code Geeks
M
MIT News - Artificial intelligence
月光博客
月光博客
IT之家
IT之家
D
DataBreaches.Net
A
About on SuperTechFans
博客园 - 三生石上(FineUI控件)
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Last Week in AI
Last Week in AI
D
Docker
The GitHub Blog
The GitHub Blog
B
Blog
V
Visual Studio Blog
博客园 - Franky
N
Netflix TechBlog - Medium
博客园 - 【当耐特】
Martin Fowler
Martin Fowler
博客园 - 聂微东
U
Unit 42

CloudCannon Blog

Building with AI: Git-based vs headless vs traditional CMS CloudCannon + Astro: performance meets powerful content management Introducing the Astro Component Starter Introducing Jetstream — built on the Astro Component Starter Why we switched to the system font stack Redesigning CloudCannon’s docs with Diátaxis, Lume, and Pagefind Make content editing more visual: upgraded Editable Regions How Configuration Mode makes building editing interfaces easy Your hosting just got an upgrade (and a price cut) Custom testing domains for professional branding Keep your content consistent with input validation Managing multilingual content in CloudCannon Simplify team publishing with conflict resolution and domain tools Open Beta: Publishing Conflict Resolution Getting started with CloudCannon and Astro: Bookshop, components, and live editing Welcome to the CloudCannon Community! Omnichannel delivery is just marketing spin from API-based CMS companies Getting started with CloudCannon and Astro: Snippets and Collections Managing digital assets in CloudCannon: a guide to smart asset storage Understanding CloudCannon's branching workflows and Projects: a complete guide What is a static website? CloudCannon’s 2024 wrapped Getting started with CloudCannon and Astro: WYSIWYG blogging Jamstack vs. WordPress: reasons to make the change The top five static site generators for 2025 (and when to use them!) Free Jekyll themes for 2025: ten great community options Eleventy (11ty) vs. Hugo How to set up WYSIWYG editing with MkDocs Material The rise of static-first websites: why major brands are making the switch Watching your Core Web Vitals on Jamstack
Private Jekyll themes with Gemfury
2019-06-13 · via CloudCannon Blog

Jekyll themes allow styles and site structures to be reused across any number of sites. This eliminates the need to duplicate content, layouts, includes and assets across multiple sites.

Themes are a necessity when managing more than one site that use the same designs or styles. All sites using a theme are updated whenever changes are made to the theme.

Gemfury offers a secure hosting for gems/themes. All interactions with Gemfury are secure over HTTPS.

Creating Jekyll Themes Direct link to this section

The Jekyll new-theme command creates a basic theme structure which includes the _layouts, _includes and _sass directories. Start building a theme by entering the following into your command line:

$ jekyll new-theme mytheme

This essentially generates a standard Jekyll site which other sites can inherit from.

Packaging Themes Direct link to this section

Themes need to be packaged as a .gem file before being hosted on Gemfury. It is good practice to add all relevant details to the .gemspec file (mytheme.gemspec), and the readme before packaging. Errors will be displayed when packaging a theme if the .gemspec and readme files contain "FIXME" and "TODO" entries.

Themes are packaged into a gem file by using the gem build command:

$ gem build mytheme.gemspec

This packages all files and directories within your theme into a single gem file (yourtheme.gem).

Uploading Themes Direct link to this section

Create an account with Gemfury and install the Gemfury CLI by entering the following within the command line:

$ gem install fury

Log into Gemfury to enable uploading:

$ fury login

Upload the gem theme to your account:

$ fury push mytheme-0.1.0.gem

If you're pushing to a shared account you will need to enter the username parameter :

$ fury push mytheme-0.1.0.gem --as USERNAME

Using Themes Direct link to this section

To build a themed site the Gemfile needs to be adjusted so the theme is downloaded during the build process. Open the site's Gemfile and add the following:

source 'https://gem.fury.io/USERNAME/' do
gem 'GEMNAME', '~> 0.1.0'
end

The above Ruby code searches for the gem/theme from the source on build, and downloads the latest version.

Jekyll also needs to know that a site uses a theme. This is achieved by specifying the theme within your site's _config.yml file.

theme: mytheme

Authentication Direct link to this section

A deploy token can be generated on Gemfury's website to provide authentication for theme usage. Log in to Gemfury's website and navigate to Tokens > Deploy Tokens. Create a new deploy token and be sure to save it in a secure location. This key provides access to your theme and should not be shared publicly.

Adding authentication for local builds can be done using bundle config:

$ bundle config https://gem.fury.io/USERNAME/ DEPLOYTOKEN

Authentication also needs to be added to your site on CloudCannon, which can be done using environment variables . In CloudCannon navigate to Settings > Configuration > Environment Variables.

Add the key BUNDLE_GEM__FURY__IO and add your deploy token as the value. These steps only need to be performed once with each site using a theme.

Test your theme by building it locally. Note that you need to install your new theme so run bundle install before serving your site:

$ bundle install
$ bundle exec jekyll serve

Updating Themes Direct link to this section

Each time a theme is updated you will need to run bundle update mytheme within your site's directory. This updates your Gemfile.lock which tells the site to use the latest theme version. Pushing this file will update the version used by CloudCannon.

Public Themes Direct link to this section

All packages uploaded to Gemfury are made private by default. To make a package public you will need to change it's privacy settings:

  • Upload your package/theme to Gemfury
  • Open your account Dashboard
  • Open the relevant package and select 'Settings', or select the lock icon displayed beside the package's version
  • Select the 'Make package public' button

Your package/theme can now be accessed following your Repo-URL https://repo.fury.io/USERNAME/