You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The current install instructions of adding: theme: jekyll-theme-gcweb
To the _config.yml file gives an error: jekyll 3.8.7 | Error: The jekyll-theme-gcweb theme could not be found.
To Reproduce
Steps to reproduce the behavior:
Open the _config.yml file
Add theme: jekyll-theme-gcweb
Build with Jekyll: jekyll build
Expected behavior
Error free installation
Desktop (please complete the following information):
OS: Linux, MacOS
Version 0.1.0
Additional context
Adding: gem "gcweb-jekyll", "~> 0.1.0", git: "https://github.com/wet-boew/gcweb-jekyll"
to the Gemfile fixed it, as well as: theme: gcweb-jekyll # not jekyll-theme-gcweb
to the _config.yml fixes this.
However, adding gcweb-jekyll from GitHub is risky as it's not necessarily a release. Is there a different way to do this?
The text was updated successfully, but these errors were encountered:
at88mph
added a commit
to at88mph/gcweb-jekyll
that referenced
this issue
Dec 9, 2022
@at88mph These instructions are definitely out of date! We're working on improving the developer experience for the GCWeb-Jekyll, with appropriate translated documentation and all.
Describe the bug
The current install instructions of adding:
theme: jekyll-theme-gcweb
To the
_config.yml
file gives an error:jekyll 3.8.7 | Error: The jekyll-theme-gcweb theme could not be found.
To Reproduce
Steps to reproduce the behavior:
_config.yml
filetheme: jekyll-theme-gcweb
jekyll build
Expected behavior
Error free installation
Desktop (please complete the following information):
Additional context
Adding:
gem "gcweb-jekyll", "~> 0.1.0", git: "https://github.com/wet-boew/gcweb-jekyll"
to the
Gemfile
fixed it, as well as:theme: gcweb-jekyll # not jekyll-theme-gcweb
to the
_config.yml
fixes this.However, adding
gcweb-jekyll
from GitHub is risky as it's not necessarily a release. Is there a different way to do this?The text was updated successfully, but these errors were encountered: