* master:
Update history to reflect merge of #5156 [ci skip]
Update history to reflect merge of #5177 [ci skip]
Update history to reflect merge of #5173 [ci skip]
Minor updates and corrections
Future True on GitHub Pages note
resolve theme root before sanitizing
dont double sanitize theme folder paths
* master:
Update history to reflect merge of #5152 [ci skip]
Missing trailing |
Update history to reflect merge of #5158 [ci skip]
Also include LICENSE and README
note that themes have been released
Update history to reflect merge of #5143 [ci skip]
Update history to reflect merge of #5150 [ci skip]
Revert "Readability: lib/jekyll/static_file.rb."
include theme directories in default gemspec
[site] enable excerpts
Centre align text and use nav styles on helpful links.
Puns FTW
Add helpful links and minor alignment tweak.
Create error template that has no main nav or footer.
Use more generic wording.
sitemap: false so that the error page is not indexed
Initial 404 page
With gem-based themes being bundled in the new site via the `Gemfile`, we
should ask folks to use Bundler wherever possible. This should lead to more
successful installations and getting the base site setup properly.
The only trouble this introduces is it puts a dependency on Bundler. That
said, I'm totally fine with requiring everyone use Bundler for this site.
How could we best install bundler in these instructions?
/cc @jekyll/documentation
Presently, on a Windows machine, you get an ArgumentError on Windows:
Generating...
C:/Ruby23-x64/lib/ruby/2.3.0/pathname.rb:520:in `relative_path_from':
different prefix: "/" and "C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/minima-1.0.1" (ArgumentError)
from C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/jekyll-3.2.0/lib/jekyll/layout.rb:61:in `relative_path'
from C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/jekyll-3.2.0/lib/jekyll/renderer.rb:161:in `place_in_layouts'
from C:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/jekyll-3.2.0/lib/jekyll/renderer.rb:71:in `run'
This doesn't affect filesystems which do not use drive names.
