jekyll / jekyll-help Goto Github PK

NO LONGER MAINTAINED. USE JEKYLL TALK INSTEAD.

jekyll-help's Introduction

Jekyll

Jekyll is a simple, blog-aware, static site generator perfect for personal, project, or organization sites. Think of it like a file-based CMS, without all the complexity. Jekyll takes your content, renders Markdown and Liquid templates, and spits out a complete, static website ready to be served by Apache, Nginx or another web server. Jekyll is the engine behind GitHub Pages, which you can use to host sites right from your GitHub repositories.

Philosophy

Jekyll does what you tell it to do — no more, no less. It doesn't try to outsmart users by making bold assumptions, nor does it burden them with needless complexity and configuration. Put simply, Jekyll gets out of your way and allows you to concentrate on what truly matters: your content.

See: https://jekyllrb.com/philosophy

Getting Started

Install the gem
Read up about its Usage and Configuration
Take a gander at some existing Sites
Fork and Contribute your own modifications
Have questions? Check out our official forum community Jekyll Talk and #jekyll Channel on Libera IRC

Diving In

Migrate from your previous system
Learn how Front Matter works
Put information on your site with Variables
Customize the Permalinks your posts are generated with
Use the built-in Liquid Extensions to make your life easier
Use custom Plugins to generate content specific to your site
Watch video tutorials from Giraffe Academy

Need help?

If you don't find the answer to your problem in our docs, or in the troubleshooting section, ask the community for help.

Code of Conduct

In order to have a more open and welcoming community, Jekyll adheres to a code of conduct adapted from the Ruby on Rails code of conduct.

Please adhere to this code of conduct in any interactions you have in the Jekyll community. It is strictly enforced on all official Jekyll repositories, websites, and resources. If you encounter someone violating these terms, please let one of our core team members know and we will address it as soon as possible.

Credits

Contributors

This project exists thanks to all the people who contribute.

Backers

Thank you to all our backers! 🙏 Become a backer

License

See the LICENSE file.

jekyll-help's People

Contributors

Stargazers

Watchers

Forkers

m1cloud dreamcodez troyscott starius thelavamelon knsam erlend-sh kikidesign mountain-teahouse pkdevboxy ocsana kleopatra999 codecommunity ektapopat caiwei-ebay dalavancloud seanpm2001

jekyll-help's Issues

Rename repository to eg. jekyll-help

People who are watching via emails get a tag in the subject line of [help] where the repository name is. This isn't terribly helpful, renaming the repo while it's still in it's infancy could help people out a lot long-term.

Trying to install RVM on OSX 10.9.2

I know this isn't specifically a Jekyll issue, but I cannot get to the point where I can even install Jekyll.

rvm install ruby-2.0.0-p451

Searching for binary rubies, this might take some time.
Found remote file https://rvm.io/binaries/osx/10.9/x86_64/ruby-2.0.0-p451.tar.bz2
Checking requirements for osx.
Installing requirements for osx.
Updating system....
Installing required packages: libksba.....
Error running 'requirements_osx_brew_libs_install libksba',
showing last 15 lines of /Users/Pat/.rvm/log/1399438313_ruby-2.0.0-p451/package_install_libksba.log
++ case "$1" in
++ [[ -t 1 ]]
++ return 1
++ printf %b 'There were package installation errors, make sure to read the log.

Try `brew tap --repair` and make sure `brew doctor` looks reasonable.

Check Homebrew requirements https://github.com/mxcl/homebrew/wiki/Installation\n'
There were package installation errors, make sure to read the log.

Try `brew tap --repair` and make sure `brew doctor` looks reasonable.

Check Homebrew requirements https://github.com/mxcl/homebrew/wiki/Installation
++ case "$_system_version" in
++ return 1
Requirements installation failed with status: 1.

brew install libksba

Warning: A newer Command Line Tools release is available
Update them from Software Update in the App Store.
==> Downloading ftp://ftp.gnupg.org/gcrypt/libksba/libksba-1.3.0.tar.bz2
Already downloaded: /Library/Caches/Homebrew/libksba-1.3.0.tar.bz2
==> ./configure --prefix=/usr/local/Cellar/libksba/1.3.0
checking for clang option to accept ISO C89... (cached) unsupported
checking dependency style of clang... (cached) none
checking how to run the C preprocessor... clang -E
checking whether clang and cc understand -c and -o together... yes
configure: error: No C-89 compiler found
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1

READ THIS: https://github.com/Homebrew/homebrew/wiki/troubleshooting

brew doctor

Warning: A newer Command Line Tools release is available
Update them from Software Update in the App Store.

xcode-select --install

Can't install the software because it is not currently available from the Software Update server.

xcode-select -p

/Applications/Xcode.app/Contents/Developer

gcc -v

Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)
Target: x86_64-apple-darwin13.1.0
Thread model: posix

Installation fails

Hi,
just wante to give jekyll a try and can't pass the installation on MacOSX.
I did a "sudo gem update --system" and then tried to install jekyll with "sudo gem install jekyll", which results in:

Building native extensions.  This could take a while...
ERROR:  Error installing jekyll:
    ERROR: Failed to build gem native extension.

    /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby extconf.rb
creating Makefile

make "DESTDIR=" clean

make "DESTDIR="
compiling porter.c
porter.c:359:27: warning: '&&' within '||' [-Wlogical-op-parentheses]
      if (a > 1 || a == 1 && !cvc(z, z->k - 1)) z->k--;
                ~~ ~~~~~~~^~~~~~~~~~~~~~~~~~~~
porter.c:359:27: note: place parentheses around the '&&' expression to silence this warning
      if (a > 1 || a == 1 && !cvc(z, z->k - 1)) z->k--;
                          ^
                   (                          )
1 warning generated.
compiling porter_wrap.c
linking shared-object stemmer.bundle
clang: error: unknown argument: '-multiply_definedsuppress' [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
make: *** [stemmer.bundle] Error 1

make failed, exit code 2

Gem files will remain installed in /Library/Ruby/Gems/2.0.0/gems/fast-stemmer-1.0.2 for inspection.
Results logged to /Library/Ruby/Gems/2.0.0/extensions/universal-darwin-13/2.0.0/fast-stemmer-1.0.2/gem_make.out

What am I doing wrong?

Output different on GH-Pages vs local build

Wondering if any of you have seen this sort of thing?

I'm running jekyll (1.5.1), liquid (2.5.5), which are the same version GH Pages is running (https://pages.github.com/versions/), yet, I'm getting an odd difference between what I'm seeing on my local build and the Pages version.

Specifically, the order of items in my navigation is different locally than it is on Pages. This appears to be the only difference.

Jekyll sorts pages by the filename, so I've given my pages files name beginning with numbers, e.g. '01-home', '02-about'. This order is respected on my local build, but not on the Pages build. In fact, there doesn't appear to be a specific order at all on the Pages build. Hopefully I'm just overlooking something!

Here's the site: http://linnullmann.pubspringdev1.com/
https://github.com/sonnetmedia/linnullmann

Here's my code (it's a bi-lingual site):

 {% if page.url contains '/en/' %}
      <a href="/en/"><li class="sidebar-nav-item">home</li></a>
      {% for page in site.pages %}
        {% if page.permalink contains '/en/'  %}
          {% if page.show_in_menu == true  %}
            <a href="{{page.url}}">
              <li id="{{page.url}}" class="sidebar-nav-item{% if page.url contains /page.url/  %} active{% endif %}">{{page.title}}</li>
            </a>  
          {% endif %}
        {% endif %}
      {% endfor %}
    {% else %}{% comment %}If EN isn't in URL serve up the 'unless' case{% endcomment %}
      <a href="/"><li class="sidebar-nav-item">hjem</li></a>
      {% for page in site.pages %}
        {% unless page.permalink contains '/en/'  %}
          {% if page.show_in_menu == true  %}
            <a href="{{page.url}}">
              <li id="{{page.url}}" class="sidebar-nav-item{% if page.url contains /page.url/  %} active{% endif %}">{{page.title}}</li>
            </a>  
          {% endif %}
        {% endunless %}
      {% endfor %}
    {% endif %}

LOCAL

PAGES

static_comments plugin no longer working with Jekyll v2. Why?

Hello,

I’m currently rebuilding my site with Jekyll. I’ve retained the comments that were posted on my previous Movable Type-powered website (using the Movable Type import script) and the static_comments.rb plugin, found here: https://github.com/shigeya/jekyll-static-comments/

This was working perfectly up until v1.5.1, but since the update to v2.0.x, I get the following error (using --trace):

Pinova:paulrobertlloyd.dev paulrobertlloyd$ jekyll build --trace
Configuration file: /Users/paulrobertlloyd/Sites/paulrobertlloyd.dev/_config.yml
            Source: /Users/paulrobertlloyd/Sites/paulrobertlloyd.dev
       Destination: /Users/paulrobertlloyd/Sites/paulrobertlloyd.dev/_site
      Generating... 
  Liquid Exception: undefined local variable or method `relative_path' for #<StaticComments::StaticComment:0x007f877c1ee3c0> in _includes/sections/comments.html, included in _layouts/post.html
/Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/lib/jekyll/tags/include.rb:114:in `rescue in render': undefined local variable or method `relative_path' for #<StaticComments::StaticComment:0x007f877c1ee3c0> (Jekyll::Tags::IncludeTagError)
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/lib/jekyll/tags/include.rb:106:in `render'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/liquid-2.5.5/lib/liquid/block.rb:106:in `block in render_all'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/liquid-2.5.5/lib/liquid/block.rb:93:in `each'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/liquid-2.5.5/lib/liquid/block.rb:93:in `render_all'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/liquid-2.5.5/lib/liquid/tags/if.rb:40:in `block (2 levels) in render'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/liquid-2.5.5/lib/liquid/tags/if.rb:38:in `each'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/liquid-2.5.5/lib/liquid/tags/if.rb:38:in `block in render'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/liquid-2.5.5/lib/liquid/context.rb:105:in `stack'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/liquid-2.5.5/lib/liquid/tags/if.rb:37:in `render'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/liquid-2.5.5/lib/liquid/block.rb:106:in `block in render_all'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/liquid-2.5.5/lib/liquid/block.rb:93:in `each'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/liquid-2.5.5/lib/liquid/block.rb:93:in `render_all'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/liquid-2.5.5/lib/liquid/block.rb:82:in `render'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/liquid-2.5.5/lib/liquid/template.rb:124:in `render'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/liquid-2.5.5/lib/liquid/template.rb:132:in `render!'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/lib/jekyll/convertible.rb:96:in `render_liquid'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/lib/jekyll/convertible.rb:142:in `render_all_layouts'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/lib/jekyll/convertible.rb:176:in `do_layout'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/lib/jekyll/post.rb:266:in `render'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/lib/jekyll/site.rb:245:in `block in render'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/lib/jekyll/site.rb:244:in `each'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/lib/jekyll/site.rb:244:in `render'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/lib/jekyll/site.rb:43:in `process'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/lib/jekyll/command.rb:43:in `process_site'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/lib/jekyll/commands/build.rb:46:in `build'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/lib/jekyll/commands/build.rb:30:in `process'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/lib/jekyll/commands/build.rb:17:in `block (2 levels) in init_with_program'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/mercenary-0.3.3/lib/mercenary/command.rb:220:in `call'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/mercenary-0.3.3/lib/mercenary/command.rb:220:in `block in execute'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/mercenary-0.3.3/lib/mercenary/command.rb:220:in `each'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/mercenary-0.3.3/lib/mercenary/command.rb:220:in `execute'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/mercenary-0.3.3/lib/mercenary/program.rb:35:in `go'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/mercenary-0.3.3/lib/mercenary.rb:22:in `program'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/gems/jekyll-2.0.2/bin/jekyll:18:in `<top (required)>'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/bin/jekyll:23:in `load'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/bin/jekyll:23:in `<main>'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/bin/ruby_executable_hooks:15:in `eval'
    from /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.0/bin/ruby_executable_hooks:15:in `<main>'

My source code is available here: https://github.com/paulrobertlloyd/paulrobertlloyd.com

_(Note that comments are not available on my GitHub repo as they contain user’s email addresses. However, there is a folder called comments in the root of the project, which contains a folder for each post with comments, and a .markdown file for each comment.)

What has changed in v2.0 that would cause this issue?

Thanks,

Paul

Error while trying to install pre-release

While running sudo gem install jekyll --pre on mac, I get the following:

Building native extensions.  This could take a while...
ERROR:  Error installing jekyll:
    ERROR: Failed to build gem native extension.

    /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby extconf.rb
checking for rb_thread_blocking_region()... yes
checking for sys/select.h... yes
checking for poll.h... yes
checking for sys/epoll.h... no
checking for sys/event.h... yes
checking for sys/queue.h... yes
checking for port.h... no
checking for sys/resource.h... yes
creating Makefile

make "DESTDIR="
compiling monitor.c
In file included from monitor.c:6:
In file included from ./nio4r.h:10:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/include/ruby-2.0.0/ruby/backward/rubyio.h:2:2: warning: use "ruby/io.h" instead of "rubyio.h" [-W#warnings]
#warning use "ruby/io.h" instead of "rubyio.h"

Here is the full output https://gist.github.com/justinmusgrove/9946007. I am pretty new to ruby so if you need more details or want me to try something, let me know. Thanks!

Implementing shorturls?

What is the best and/or easiest way to create base16 shorturls (short urls) mapping from your blog posts to your own domain without relying on services like bit.ly—which don’t protect your links, should the company fail or get acquired?

How have you implemented them on your site?

Problem with Upgrade

Hello, first thanks for Jekyll, and congrats on the anniversary! I was just playing around over the last few days on 1.5.1, then saw the update for 2.0.2 today and upgraded. However, if I change into a directory where I had a site built before it's still running 1.5.1 (and presently wont serve or build). I'm new to Ruby so not really sure where this all lives on my Mac (10.9) but I must have something configured incorrectly...

Here is my terminal history... is there a way to switch/force to use the new Jekyll? I suspect this may be a conflict with bundler, homebrew or other package manager? I'll admit I didn't know what the hell I was doing when I installed 1.5.1 last week :/

mbp:~ zachlyon$ jekyll -v
jekyll 2.0.2
mbp:~ zachlyon$ cd Sites/mysite.jekyll/
mbp:mysite.jekyll zachlyon$ jekyll -v
jekyll 1.5.1
mbp:mysite.jekyll zachlyon$ gem update jekyll
Updating installed gems
Nothing to update
mbp:mysite.jekyll zachlyon$ gem uninstall jekyll

Select gem to uninstall:
 1. jekyll-1.5.1
 2. jekyll-2.0.2
 3. All versions
> 1

You have requested to uninstall the gem:
    jekyll-1.5.1

jekyll-coffeescript-1.0.0 depends on jekyll (~> 1.0, development)
jekyll-sitemap-0.3.0 depends on jekyll (~> 1.4)
If you remove this gem, these dependencies will not be met.
Continue with Uninstall? [yN]  y
Successfully uninstalled jekyll-1.5.1
mbp:mysite.jekyll zachlyon$ jekyll -v
Could not find proper version of jekyll (1.5.1) in any of the sources
Run `bundle install` to install missing gems.
mbp:mysite.jekyll zachlyon$

The bundle install just grabs another 1.5.1. Any ideas?

Thanks!
Zach

THIS IS A PAIN IN THE ASS TO INSTALL

Can I get some instructions that are easier to install Jekyll????

Work with *.Rmd files and RStudio

Hello,

so far I was able to set up jekyll on github pages: http://magnusmetz.github.io/

I want to use it as a substitute for RPubs and publish posts written as *.Rmd files.

It seems, there are two major issues left, which were impossible for me to solve so far and I was not able to solve the problem with the information I found on the internet.

I use RStudio to version control the website. If I make a change in one of the markdown files in the _posts folder and commit these changes, the changes are not overtaken on http://magnusmetz.github.io/, although I can see them on http://localhost:4000/. Why is that? It seems that changes in the markdown files are tracked but the subsequent changes in _site are not transmitted to github. How to solve this issue?
I want to use *.Rmd files as the root files for my posts instead of markdown. How can I accomplish that? I know the blog of http://jfisher-usgs.github.io/ but I was not really able to accomplish that. But this is a pretty good example what I want to do.

Thanks in advance for further help.

Magnus

loop "Regenerating: 0 files at ..."

This problem appears with upgrade to Jekyll 2.
Using

bundle exec jekyll serve --watch

When some file modified jekyll regenerating one, and then keep trying to regenerate. Then, when something new was modified, it's regenerate the new file, and continues "0 files".

Regenerating: 1 files at 2014-05-20 16:34:32 ...done.
Regenerating: 0 files at 2014-05-20 16:34:33 ...done.
Regenerating: 0 files at 2014-05-20 16:34:34 ...done.

...

Regenerating: 1 files at 2014-05-20 16:34:39 ...done.
Regenerating: 0 files at 2014-05-20 16:34:39 ...done.
Regenerating: 0 files at 2014-05-20 16:34:40 ...done.

Using

bundle exec jekyll serve --watch --force_polling

solve this problem, but with this option regeneration event does not always work.

Theme settings in config or data?

I write a customizable theme for Jekyll. Call it theme. I see two places where the user can place her settings:

_config.yml
```
theme:
  option1: value1
  option2: value2
```
Then I access the settings via site.theme.
_data/theme.yml
```
option1: value1
option2: value2
```
Then I access the settings via site.data.theme.

Which one is better and why?

How do I create "Edit this page" links in Jekyll?

A few Jekyll docs pages I've visited have a handy "Edit" link that takes me to that page's file on GitHub, so I can edit it directly or make a pull request.

Example 1: Top right, "Improve this doc"
http://ionicframework.com/docs/api/directive/ionTabs/

Example 2: Top right, "Edit"
http://sendgrid.com/docs/API_Reference/index.html

Is there a default way of achieving this in Jekyll?

Better Objective-C syntax highlighting?

I know Jekyll supports Objective-C syntax highlighting now, but the Pygments implementation very bland. Is there a better way to do it? I've searched for hours, and short of writing my own (which I have absolutely no idea how to do), I'm beginning to believe this is the only option. Beggars can't be choosers, so if there's nothing else I'll be fine, but it never hurts to check.

SCSS compiles but SASS does not (v2.0.2)

In a new project, I removed main.css and replaced it with main.sass.

I included the two lines of "---" and just wrote

body
  background-color: red

This was copied as main.sass in _site/css when building.

Changing this to main.scss and

body {
  background-color: red;
}

It compiles to main.css in _site/css as you would expect.

Working, official-unofficial Atom feed code

I currently use this feed code for my blog. Unfortunately, it doesn’t seem to work in readers (ndarville/ndarville.github.io#11).

Finding the right feed code is a terrible experience I wouldn’t wish upon my worst enemy, and I recall how long it took me to get it to work for the static Blogofile CMS.

Can we establish a working official-unofficial Jekyll feed code that people can use, and which can be improved upon in one central place, should any new bugs be found?

Decisions

{{ site.baseurl }} vs. {{ site.url }} w/r/t SSL
xml_escape vs. CDATA
Filename: /atom/index.xml, atom.xml, feed.atom, etc.

Variables in include variables

Is there any way to make something like this work?

{% include navigation/social_listing.html url="mailto:{{ site.author.email }}" shortname="mail" label="Email" %}

Installation error

When I try to install jekyll on my Mac (OSX 10.9.2), I get the following errors:

$ sudo gem install jekyll
Building native extensions.  This could take a while...
ERROR:  Error installing jekyll:
    ERROR: Failed to build gem native extension.

    /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby extconf.rb
creating Makefile

make "DESTDIR=" clean

make "DESTDIR="
compiling porter.c
porter.c:359:27: warning: '&&' within '||' [-Wlogical-op-parentheses]
      if (a > 1 || a == 1 && !cvc(z, z->k - 1)) z->k--;
                ~~ ~~~~~~~^~~~~~~~~~~~~~~~~~~~
porter.c:359:27: note: place parentheses around the '&&' expression to silence this warning
      if (a > 1 || a == 1 && !cvc(z, z->k - 1)) z->k--;
                          ^
                   (                          )
1 warning generated.
compiling porter_wrap.c
linking shared-object stemmer.bundle
clang: error: unknown argument: '-multiply_definedsuppress' [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
make: *** [stemmer.bundle] Error 1

make failed, exit code 2

Gem files will remain installed in /Library/Ruby/Gems/2.0.0/gems/fast-stemmer-1.0.2 for inspection.
Results logged to /Library/Ruby/Gems/2.0.0/extensions/universal-darwin-13/2.0.0/fast-stemmer-1.0.2/gem_make.out

I have command line developer tools 5.1.0.0 and XCode 5.1.1. I can bypass the error by typing ARCHFLAGS=-Wno-error=unused-command-line-argument-hard-error-in-future before the gem install, but not sure if that was a good idea!

Accessing un-published posts in a template?

Hello,

New to Jekyll, but recently ported my blog to Octopress. And sorry if this should be posted over at Octopress instead, but it felt Jekyll related.

I'm working on a series about porting a blog from BlogSpot/Blogger to Octopress and found this post about creating a series template to live in _includes.

I've since modified the template and want access to un-published posts within the template. (or if this can be done through drafts - maybe I just need a tip on how to get them).

My end goal would be to get the following template to work.

Series Gist Template

Notice how I'm trying to use post.published == false to output (coming soon)...

This works when I use rake generate; rake preview but the (coming soon) posts don't show up immediately. There's some sort of delay before this gets generated, and I presume this is related to the preview rake task in Octopress (but haven't dug in enough). After some time if I refresh it will display what I want, but I'm pretty sure rake generate; rake deploy won't produce the same thing.

Is it possible to access un-published posts or possibly drafts - to accomplish something like this?

This article is Part 2 of 5 in a series about something awesome.

Part 1 - something awesome - Introduction
Part 2 - something awesome - (current) Step 1
Part 3 - something awesome - Step 2
Part 4 - something awesome - (coming soon) Step 3
Part 5 - something awesome - (coming soon) Wrapping up

Over on jekyll/jekyll#2226 @parkr

Presently, only posts which are published are added to the site.posts array, so this isn't possible.

Was hoping anyone with experience could light the way to an alternative approach to accomplish the desires output.

How to get a document's (page's) collection

I'm not seeing anything in the docs or code on this.

I'd like to do something like...{{page.collection_label}} or {{page.collection_name}} to output the collection of the current page's document.

Essentially, I want to accomplish two things: 1) Put a label for the collection at the top of the page and 2) create a menu of other items in the collection.

You know what would be nice?

A Powered by Jekyll image/button we could proudly display on our websites. I'm no designer, so yea. Something with a nice hover change too. 😃

Error with SCSS generation in Jekyll 2.0

I have my project laid out like so:

-Project
  -css
    -import.scss
    -_sass/
      main.scss

The contents of import.scss are:


---

---

@import "main.scss";

What I expected to happen was for main.scss to be imported into import.scss, then, import.scss would compile to import.css within the genrated _site/ directory.

Instead, I get the following error

Conversion error: There was an error converting 'css/import.scss'.
jekyll 2.0.3 | Error:  Invalid CSS after "-": expected number or function, was "--"

I'm guessing it's complaining about the YAML front-matter at the top of import.scss, but jekyll won't convert this if I remove the front-matter, will it?

Depreciation issue with pygments

Hi. I know jekyll for three day now and it seems to work fine so far. I get into it and I love the possibilities it provides to use jekyll in combination with Github pages, R, R markdown, and RStudio (see http://magnusmetz.github.io/). Just one (hopefully last) question: Everytime I call

jekyll serve

the command does its job and parses the site but I also get a message, which confuses me:

 Deprecation: The 'pygments' configuration option has been renamed to 'highlighter'. Please update your config file accordingly. The allowed values are 'rouge', 'pygments' or null.

What does that mean? Can you help interpret that and tell me what to do? I just want to understand what is going on. Thanks in advance for further help.

Yours,
Magnus

How do I create back/next pages like on jekyllrb.com?

I'd like to guide our readers from start to finish through our docs, so I need Back/Next links for pages, much like how on jekyllrb.com you start at Home and you can "Next"-click all the way to History, where the page series ends.

All the guides I've found appear to be talking about pagination for posts, not pages. Could you give me some pointers?

As an aside, this personal preference is probably plugin territory, but I would love it if I could define something like this in front matter:

series: guide
order: 1

or
guide-series: 1

It would be in the same vein as using custom taxonomies to achieve series in WordPress.

Once again I have another issue: running 'jekyll new myblog'

I got jekyll installed via 'sudo gem install jekyll' and now I get errors running 'jekyll new myblog' from quick start guide:

ubuntu:~$ jekyll new myblog
/var/lib/gems/1.8/gems/commander-4.1.6/lib/commander/runner.rb:385:in `require_program': program version required (Commander::Runner::CommandError)
    from /var/lib/gems/1.8/gems/commander-4.1.6/lib/commander/runner.rb:384:in `each'
    from /var/lib/gems/1.8/gems/commander-4.1.6/lib/commander/runner.rb:384:in `require_program'
    from /var/lib/gems/1.8/gems/commander-4.1.6/lib/commander/runner.rb:52:in `run!'
    from /var/lib/gems/1.8/gems/commander-4.1.6/lib/commander/delegates.rb:8:in `run!'
    from /var/lib/gems/1.8/gems/commander-4.1.6/lib/commander/import.rb:10
    from /usr/local/bin/jekyll:19
/usr/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require': no such file to load -- json (LoadError)
    from /usr/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:36:in `require'
    from /var/lib/gems/1.8/gems/jekyll-1.5.1/bin/../lib/jekyll/filters.rb:2
    from /usr/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require'
    from /usr/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:36:in `require'
    from /var/lib/gems/1.8/gems/jekyll-1.5.1/bin/../lib/jekyll.rb:44
    from /usr/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require'
    from /usr/lib/ruby/vendor_ruby/1.8/rubygems/custom_require.rb:36:in `require'
    from /var/lib/gems/1.8/gems/jekyll-1.5.1/bin/jekyll:7
    from /usr/local/bin/jekyll:19:in `load'
    from /usr/local/bin/jekyll:19

I really don't know what any of this means... Can someone help please?

Jekyll/GitHub workflow with hidden drafts?

I am thinking about doing a blog/site with multiple authors, and while I would like for the site to be open source (at least the majority of it), I would prefer the drafts remained hidden, and that, when published as posts, their edit history would be erased from before they were published.

private repo:
  - _drafts/ (w/ edit history)

public repo:
  - _posts/ (w/ edit history)
  - (...)

Assuming everything is hosted on GitHub, but deployed to S3 (to support custom domains), what would be the best way to do this?

And which publication hook would fit the best for automating this process as much as possible?

Jekyll 2 fails to auto-gen on folder starting with '___' outside of Jekyll scope

Hey guys,

A few of my projects have stopped working, and I realize it's because my folders are set up kind of like this:
Documents/Folders/___ImportantFolder/JekyllProjects/Project1
Documents/Folders/___ImportantFolder/JekyllProjects/Project2

Ideally I want Jekyll's escaping '___' only to happen within Project1 and Proejct2, so it's not generating folders that start with ___ in Project1 or 2, but right now it's stopped generating anything that starts with ___, even when those folders are outside of Jekyll's project folder's scope

This was never a problem with the previous Jekyll.

Thanks!

Error Installing Jekyll with Native Mavericks Ruby

Had native Mavericks ruby, and updated gems, and XCode Command LIne tools. Ran into this error:

ERROR:  Error installing jekyll:
    ERROR: Failed to build gem native extension.

    /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby extconf.rb
creating Makefile

make "DESTDIR=" clean

make "DESTDIR="
compiling porter.c
porter.c:359:27: warning: '&&' within '||' [-Wlogical-op-parentheses]
      if (a > 1 || a == 1 && !cvc(z, z->k - 1)) z->k--;
                ~~ ~~~~~~~^~~~~~~~~~~~~~~~~~~~
porter.c:359:27: note: place parentheses around the '&&' expression to silence this warning
      if (a > 1 || a == 1 && !cvc(z, z->k - 1)) z->k--;
                          ^
                   (                          )
1 warning generated.
compiling porter_wrap.c
linking shared-object stemmer.bundle
clang: error: unknown argument: '-multiply_definedsuppress' [-Wunused-command-line-argument-hard-error-in-future]
clang: note: this will be a hard error (cannot be downgraded to a warning) in the future
make: *** [stemmer.bundle] Error 1

make failed, exit code 2

Was able to solve the problem with the guidance of http://stackoverflow.com/questions/22479246/how-to-install-jekyll-on-mac-osx-10-9-with-ruby-2-0-0, which suggested installing rvm and then doing rvm use ruby-2.1.1 and then sudo gem install jekyll

Figured other people could benefit from the rvm/version suggestion. Cheers!

Creating static pages from markdown and evaluating liquid tags.

So I'd like to be able to create static pages from a markdown file in the same way I'd make a blog post from a markdown file, but I can't figure out a way to get jekyll to render liquid content in any markdown file that isn't in _posts/

Is this even possible? I mean I suppose I could put my page in posts and handle the case with something hacky, but I'd really like to be able to generate my site/about page from liquid tags laden markdown.

So far I've got this. It evaluates the markdown content but totally ignores the liquid tags.

_includes/about.md


---
title: about

---
La La La
{%some liquid tag%}

and in about.html


---
layout: layout

---

{% capture about %}{% include about.md %}{% endcapture %}
{{ about  | markdownify }}

My output in the site/about page is just:

La La La

Having issues running 'gem install jekyll'

I have all the requirements to run this command, however this keeps popping up.

ubuntu:~$ gem install jekyll
ERROR: While executing gem ... (Gem::FilePermissionError)
You don't have write permissions into the /var/lib/gems/1.8 directory.

Do I run 'sudo gem install jekyll' or will I screw something up doing that?

Liquid Exception: cannot load such file -- yajl/2.0/yajl

Hi,
When I run jekyll build command on windows I get this error.
:o(

C:\Users\rdquintas\Desktop\jek\zrq>jekyll build
Configuration file: C:/Users/rdquintas/Desktop/jek/zrq/_config.yml
            Source: C:/Users/rdquintas/Desktop/jek/zrq
       Destination: C:/Users/rdquintas/Desktop/jek/zrq/_site
      Generating...
  Liquid Exception: cannot load such file -- yajl/2.0/yajl in _posts/2014-05-21-
welcome-to-jekyll.markdown
C:/Ruby200/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require': c
annot load such file -- yajl/2.0/yajl (LoadError)
        from C:/Ruby200/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in
 `require'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/yajl-ruby-1.1.0-x86-mingw32/lib
/yajl/yajl.rb:2:in `<top (required)>'
        from C:/Ruby200/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in
 `require'
        from C:/Ruby200/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in
 `require'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/yajl-ruby-1.1.0-x86-mingw32/lib
/yajl.rb:1:in `<top (required)>'
        from C:/Ruby200/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:i
n `require'
        from C:/Ruby200/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:135:i
n `rescue in require'
        from C:/Ruby200/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:144:i
n `require'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/pygments.rb-0.5.4/lib/pygments/
popen.rb:3:in `<top (required)>'
        from C:/Ruby200/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in
 `require'
        from C:/Ruby200/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in
 `require'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/pygments.rb-0.5.4/lib/pygments.
rb:1:in `<top (required)>'
        from C:/Ruby200/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in
 `require'
        from C:/Ruby200/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in
 `require'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/jekyll-2.0.3/lib/jekyll/tags/hi
ghlight.rb:53:in `render_pygments'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/jekyll-2.0.3/lib/jekyll/tags/hi
ghlight.rb:41:in `render'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/liquid-2.5.5/lib/liquid/block.r
b:106:in `block in render_all'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/liquid-2.5.5/lib/liquid/block.r
b:93:in `each'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/liquid-2.5.5/lib/liquid/block.r
b:93:in `render_all'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/liquid-2.5.5/lib/liquid/block.r
b:82:in `render'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/liquid-2.5.5/lib/liquid/templat
e.rb:124:in `render'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/liquid-2.5.5/lib/liquid/templat
e.rb:132:in `render!'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/jekyll-2.0.3/lib/jekyll/convert
ible.rb:96:in `render_liquid'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/jekyll-2.0.3/lib/jekyll/convert
ible.rb:170:in `do_layout'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/jekyll-2.0.3/lib/jekyll/post.rb
:266:in `render'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/jekyll-2.0.3/lib/jekyll/site.rb
:245:in `block in render'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/jekyll-2.0.3/lib/jekyll/site.rb
:244:in `each'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/jekyll-2.0.3/lib/jekyll/site.rb
:244:in `render'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/jekyll-2.0.3/lib/jekyll/site.rb
:43:in `process'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/jekyll-2.0.3/lib/jekyll/command
.rb:43:in `process_site'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/jekyll-2.0.3/lib/jekyll/command
s/build.rb:46:in `build'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/jekyll-2.0.3/lib/jekyll/command
s/build.rb:30:in `process'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/jekyll-2.0.3/lib/jekyll/command
s/build.rb:17:in `block (2 levels) in init_with_program'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/mercenary-0.3.3/lib/mercenary/c
ommand.rb:220:in `call'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/mercenary-0.3.3/lib/mercenary/c
ommand.rb:220:in `block in execute'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/mercenary-0.3.3/lib/mercenary/c
ommand.rb:220:in `each'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/mercenary-0.3.3/lib/mercenary/c
ommand.rb:220:in `execute'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/mercenary-0.3.3/lib/mercenary/p
rogram.rb:35:in `go'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/mercenary-0.3.3/lib/mercenary.r
b:22:in `program'
        from C:/Ruby200/lib/ruby/gems/2.0.0/gems/jekyll-2.0.3/bin/jekyll:18:in `
<top (required)>'
        from C:/Ruby200/bin/jekyll:23:in `load'
        from C:/Ruby200/bin/jekyll:23:in `<main>'

C:\Users\rdquintas\Desktop\jek\zrq>

Problems installing Jekyll on Ubuntu

When I run

>> sudo gem install jekyll

I get the error

ERROR:  While generating documentation for jekyll-1.5.1
... MESSAGE:   Unhandled special: Special: type=17, text="<!-- more -->"
... RDOC args: --ri --op /var/lib/gems/1.8/doc/jekyll-1.5.1/ri --charset=UTF-8 lib README.markdown LICENSE --title jekyll-1.5.1 Documentation --quiet

Any ideas?

Jekyll safe_yaml libyaml warning

I'm getting this safe_yaml warning any time I run a Jekyll command.

$ jekyll help

  SafeYAML Warning
  ----------------

  You appear to have an outdated version of libyaml (0.1.5) installed on your system.

  Prior to 0.1.6, libyaml is vulnerable to a heap overflow exploit from malicious YAML payloads.

  For more info, see:
  https://www.ruby-lang.org/en/news/2014/03/29/heap-overflow-in-yaml-uri-escape-parsing-cve-2014-2525/

  The easiest thing to do right now is probably to update Psych to the latest version and enable
  the 'bundled-libyaml' option, which will install a vendored libyaml with the vulnerability patched:

  gem install psych -- --enable-bundled-libyaml

There are a lot of folks who solved this by either upgrading their libyaml through brew, which I have done, or installing the psych gem with the lib built in. I tried both with no results either way. I'd prefer to use libyaml through brew.

I believe the problem is in rvm, but I'm not sure how to troubleshoot this. Maybe I need to make sure Ruby is using the libyaml from brew when it installs.

Here's some info.

$ brew info libyaml
libyaml: stable 0.1.6 (bottled)
http://pyyaml.org/wiki/LibYAML
/usr/local/Cellar/libyaml/0.1.6 (7 files, 348K) *
  Poured from bottle
From: https://github.com/Homebrew/homebrew/commits/master/Library/Formula/libyaml.rb
==> Options
--universal
    Build a universal binary

One weird thing is that I get the message saying I'm using libyaml 0.1.5 but I can't find any evidence that it's installed.

Help is appreciated.

"Could not find blankslate-2.1.2.4 in any of the sources"

Hi folks,

I'm playing with Jekyll 2 in a fresh dir, in preparation for upgrading a few of our 1.5 sites to it. (thanks for all your work on the 2.0 release!)

The problem I'm running into, possibly a local env issue, is:

$ bundle exec jekyll --version
Could not find blankslate-2.1.2.4 in any of the sources
Run `bundle install` to install missing gems.

My test Gemfile's contents are simply:

source "https://rubygems.org"

gem 'jekyll'

And this is the output I'm seeing when I install the gems:

$ bundle install --path vendor/bundle
Fetching gem metadata from https://rubygems.org/.......
Fetching additional metadata from https://rubygems.org/..
Installing blankslate 2.1.2.4
Installing timers 1.1.0
Installing celluloid 0.15.2
Installing nio4r 1.0.0
Installing celluloid-io 0.15.0
Installing fast-stemmer 1.0.2
Installing classifier 1.3.4
Installing coffee-script-source 1.7.0
Installing execjs 2.0.2
Installing coffee-script 2.2.0
Installing colorator 0.1
Installing ffi 1.9.3
Installing jekyll-coffeescript 1.0.0
Installing sass 3.3.7
Installing jekyll-sass-converter 1.0.0
Installing kramdown 1.3.3
Installing liquid 2.5.5
Installing rb-fsevent 0.9.4
Installing rb-inotify 0.9.4
Installing listen 2.7.4
Installing mercenary 0.3.3
Installing posix-spawn 0.3.8
Installing yajl-ruby 1.1.0
Installing pygments.rb 0.5.4
Installing redcarpet 3.1.2
Installing safe_yaml 1.0.3
Installing parslet 1.5.0
Installing toml 0.1.1
Installing jekyll 2.0.3
Using bundler 1.6.2
Your bundle is complete!
It was installed into ./vendor/bundle

My global Ruby (via rbenv) is in ~/.rbenv/shims/ruby — ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-darwin13.0]

Any ideas why this might be happening?

Thanks in advance,
-Eric

Gist Inclusion

Is it me or did something change?

This doesn't work {% gist 8d38d89e7cba8dbaad61 %} @example

But this does {% gist iamgabeortiz/8d38d89e7cba8dbaad61 %} @example

Eventhough all my gists are Public. According to Jekyll Templates that should not be the case. Of course I could be a newb. 😛

Is the option relative_permalinks deprecated?

If I set the variable page.permalink to a relative permalink, I get a deprecation message.

Deprecation: Starting in 2.0, permalinks for pages in subfolders must be relative to the site source directory, not the parent directory. Check http://jekyllrb.com/docs/upgrading/ for more info.

If I explicitly set

relative_permalinks: true

I still see the deprecation message. Does it mean, that site.relative_permalinks will completely disappear in 2.0.0?

Format for FAQ

Assuming we get a large amount of issue, we should run into some frequently asked questions. Which way do you prefer we provide this: in the README, in faq.md, etc.?

The FAQ can also then be used in our CONTRIBUTING file.

Front Matter defaults: Use categories in scope?

Is it possible to use categories as scope for Front Matter defaults?

  # all files with the category `portfolio` have the layout `post--portfolio`
  -
    scope:
      path: ""
      category: "portfolio" # Doesn't work.
    values:
      layout: "post--portfolio"

Documentation matching github pages

Where will I find documentation that matches the version of Jekyll running on github pages? Or otherwise how can I know what features are and are not supported?

I tried setting the "front matter defaults" according to the documentation only to find after some digging that this feature became available in jekyll 2 but GHP is running 1.5.1. Will I have to cross-reference every feature in the documentation with the changelog or can I see the docs for 1.5.1 somewhere?

had problems with Quick Start Guide until...

Just wanted to note (in case others have similar issues) that I had to modify the instructions slightly on the quick-start guide page (http://jekyllrb.com/docs/quickstart/) to get it to work for me.

Instead of:
~ $ gem install jekyll
~ $ jekyll new myblog
~ $ cd myblog
~/myblog $ jekyll serve
=> Now browse to http://localhost:4000

I had to do:
~ $ sudo gem install jekyll
~ $ sudo gem install json
~ $ jekyll new myblog
~ $ cd myblog
~/myblog $ jekyll serve
=> Now browse to http://localhost:4000

As you can see, very minor differences. Also, I got errors when the Jekyll documentation was being installed, but it still worked fine.

Problems with installing

Tried to install jekyll today on Ubuntu 12.04 LTS.
Installed ruby1.9.1 and rubygems using
sudo apt-get install ruby1.9.1 rubygems
After problems installing jekyll via termina also installed ruby1.9.1-dev using
sudo apt-get install ruby1.9.1-dev
But I still couldn't install jekyll using
gem install jekyll
Output was
ERROR: While executing gem ... (Errno::EACCES) Permission denied - /var/lib/gems
Used
sudo gem install jekyll instead.
The result was following
Fetching: liquid-2.5.5.gem (100%) Fetching: fast-stemmer-1.0.2.gem (100%) Building native extensions. This could take a while... Fetching: classifier-1.3.4.gem (100%) Fetching: timers-1.1.0.gem (100%) Fetching: celluloid-0.15.2.gem (100%) ERROR: Error installing jekyll: celluloid requires Ruby version >= 1.9.2.
Installed ruby1.9.3 using
sudo apt-get install ruby1.9.3.

After that I tried again
sudo gem install jekyll.
Result was again
ERROR: Error installing jekyll: celluloid requires Ruby version >= 1.9.2.

What's wrong? Installation experience could be better.

Thanks in advance for reply.

Magnus

Template layouts

Similar to https://github.com/jekyll/jekyll/wiki/Sites would it be useful to have a list of some skeleton setups with different frameworks? For instance, I've been working on a new site, and there's still nothing site-specific in the repo, uploading it to a repo as an example and skeleton setup for Jekyll + Compass + ZURB Foundation 5 could be useful to others.

Full story pages: How to skip posts that are of a certain category?

Hi,

TL;DR:

On my full story pages (permalink pages), I'd like to setup the previous/next pagination so that it skips any posts that have a category of X.

Long version:

Specifically, I have some posts that are categorized as "external", and when these posts are clicked, the end user is taken to that external link.

Using the previous/next post pagination, I'd like to ignore all external posts and just paginate between actual posts.

I build my Jekyll site locally, so plugins aren't an issue, but I was mostly curious if there's built-in way to "filter" the pagination object based on post frontmatter (like category)?

Does any of that make sense?

Again, this is the pagination for the post pages … The permalink pages. Not the index page pagination.

For now, I don't use the prev/next pagination on permalink pages because I couldn't figure out how to ignore my "external" posts.

Thanks!

Trouble installing Jekyll on OS X 10.9.2

I had a bit of trouble installing Jekyll on OS X 10.9.2 on my Retina MacBook Pro. Here is the error I got when running 'gem install jekyll'.

sudo gem install jekyll
Building native extensions.  This could take a while...
ERROR:  Error installing jekyll:
    ERROR: Failed to build gem native extension.

    /Users/jessica/.rvm/rubies/ruby-1.9.3-p448/bin/ruby extconf.rb
creating Makefile

make  clean

make
compiling porter.c
porter.c:31:44: error: stdlib.h: No such file or directory
porter.c:32:47: error: string.h: No such file or directory
porter.c: In function ‘create_stemmer’:
porter.c:85: warning: implicit declaration of function ‘malloc’
porter.c:85: warning: incompatible implicit declaration of built-in function ‘malloc’
porter.c: In function ‘free_stemmer’:
porter.c:91: warning: implicit declaration of function ‘free’
porter.c: In function ‘ends’:
porter.c:188: warning: implicit declaration of function ‘memcmp’
porter.c: In function ‘setto’:
porter.c:199: warning: implicit declaration of function ‘memmove’
porter.c:199: warning: incompatible implicit declaration of built-in function ‘memmove’
porter.c: In function ‘step1ab’:
porter.c:233: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:234: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:234: warning: passing argument 2 of ‘setto’ discards qualifiers from pointer target type
porter.c:237: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:238: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:238: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:240: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:240: warning: passing argument 2 of ‘setto’ discards qualifiers from pointer target type
porter.c:241: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:241: warning: passing argument 2 of ‘setto’ discards qualifiers from pointer target type
porter.c:242: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:242: warning: passing argument 2 of ‘setto’ discards qualifiers from pointer target type
porter.c:249: warning: passing argument 2 of ‘setto’ discards qualifiers from pointer target type
porter.c: In function ‘step1c’:
porter.c:257: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c: In function ‘step2’:
porter.c:267: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:267: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:268: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:268: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:270: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:270: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:271: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:271: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:273: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:273: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:275: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:275: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:280: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:280: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:281: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:281: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:282: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:282: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:283: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:283: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:285: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:285: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:286: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:286: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:287: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:287: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:289: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:289: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:290: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:290: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:291: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:291: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:292: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:292: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:294: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:294: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:295: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:295: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:296: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:296: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:298: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:298: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c: In function ‘step3’:
porter.c:308: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:308: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:309: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:309: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:310: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:310: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:312: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:312: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:314: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:314: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:315: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:315: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c:317: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:317: warning: passing argument 2 of ‘r’ discards qualifiers from pointer target type
porter.c: In function ‘step4’:
porter.c:325: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:326: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:327: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:328: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:329: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:330: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:331: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:332: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:333: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:334: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:335: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:336: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:337: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:339: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:340: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:341: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:342: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:343: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
porter.c:344: warning: passing argument 2 of ‘ends’ discards qualifiers from pointer target type
make: *** [porter.o] Error 1

make failed, exit code 2

Gem files will remain installed in /Users/jessica/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/gems/1.9.1/gems/fast-stemmer-1.0.2 for inspection.
Results logged to /Users/jessica/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/gems/1.9.1/extensions/x86_64-darwin-12/1.9.1/fast-stemmer-1.0.2/gem_make.out

Template no longer included in site after upgrade from 1.4.3 to 2.0.2

Greetings,

I was excited to upgrade to 2.0.2, but found that my generated index.html file no longer included the template code. I reverted back to 1.4.3 and everything works again.

Here's the repo:

https://github.com/morea-framework/basic-template

It just generates the index.html without any content in the element.

What am I doing wrong, and/or what should I change for 2.0 to make this site work correctly?

Or if it works fine for you, that would be useful info as well.

Thanks,
Philip

Make a theme installable and upgradeable

Let me first explain, how I define a theme. It’s a bunch of files and configurations, that a user can try out inside an existing installation without affecting the previous theme.

I end up in the following namespace scenario for the theme Mytheme:

Layouts live in the directory _mytheme. The _config.yml must be changed to:
```
layouts: ./_mytheme
```
Includes live in the directory _includes/mytheme.
External libraries live in the directory mytheme.
Settings live in the variable mytheme inside of _config.yml.

I provide three scattered directories. The user should never modify them by hand. She should only set the options in the config. The installation should be foolproof. The upgrade should be one action only.

My ideas:

Maintain one theme repository. Provide a bash script that clones (git) my theme repository in a temporary directory. Then the directories get copied to the right places inside of user’s source. Existing mytheme files get overridden. The user executes the same script if she wants to upgrade the theme.
Maintain three theme repositories, one for every directory. Provide a bash script that creates three git submodules inside of user’s source. Provide a second script for the upgrade procedure.
Maintain three theme repositories. Use a package manager like Bower to handle installation and upgrade procedures.

What is the easiest way to install such a theme composed of three directories? How do you create installable and upgradeable themes?

{% raw %} {% endraw %} tags not being respected

I can't figure this out - for some reason the stuff I put inside of {%raw%}{%endraw%} tags is still being parsed/evaluated by Liquid.

So if I make a .md file with just this for content:

Start
{% raw %}
{{something}}
{% endraw %}
End

My generated HTML just looks like:
Start
End

Same goes for:

Start
{% raw %}
{% sometag %}
{% endraw %}
End

If sometag is a real tag, then Liquid evaluates it and replaces it with whatever that tag gets replaced with, and if it's not then jekyll build tells me it doesn't know that the tag 'something'

Been stuck on this for a while and really can't figure it out.

_config.yml:
encoding: utf-8
markdown: redcarpet
highlighter: highlighter
redcarpet:
extensions: ['highlight','strikethrough']
...

relevant gem versions:
jekyll 2.0.2
liquid 2.5.5
kramdown 1.3.3
redcarpet 3.1.1

FreeBSD: Could not find kramdown

Hi,
When I try to run jekyll new bloglocation on FreeBSD 10.0, I get this error:

/usr/local/lib/ruby/site_ruby/2.1/rubygems/dependency.rb:247:in `to_specs': Could not find kramdown (~> 1.0.2) amongst [classifier-1.3.3, colorator-0.1, commander-4.1.4, directory_watcher-1.4.1, fast-stemmer-1.0.2, highline-1.6.21, jekyll-1.0.3, kramdown-1.3.3, liquid-2.5.0, maruku-0.6.1, posix-spawn-0.3.6, pygments.rb-0.5.4, safe_yaml-0.9.4, syntax-1.0.0, yajl-ruby-1.2.0] (Gem::LoadError)
        from /usr/local/lib/ruby/site_ruby/2.1/rubygems/specification.rb:778:in `block in activate_dependencies'
        from /usr/local/lib/ruby/site_ruby/2.1/rubygems/specification.rb:767:in `each'
        from /usr/local/lib/ruby/site_ruby/2.1/rubygems/specification.rb:767:in `activate_dependencies'
        from /usr/local/lib/ruby/site_ruby/2.1/rubygems/specification.rb:751:in `activate'
        from /usr/local/lib/ruby/site_ruby/2.1/rubygems.rb:1232:in `gem'
        from /usr/local/bin/jekyll:22:in `<main>'

Ruby says I have kramdown on my computer, so why is it giving an error that kramdown isn't installed on my computer? I installed Jekyll from FreeBSD ports, and set the default Ruby version to 2.1.
BTW I have posted this issue on Jekyll's main GitHub repo, but @parktr said to come here.

Where are the group_by docs? :-)

I tried to group my posts by year by doing something like this:

{% for year in site.posts | group_by:"{{ date | date:'%Y' }}" %}

but it doesn't work, and I've been unable to find docs on what you can group by or how you should write it. And:

{% for year in {{ site.posts | group_by:"{{ date | date:'%Y' }}" }} %}
## {{ year.name }}
{% for post in year.items %}
- [{{ post.title | markdownify | remove:'<p>' | remove:'</p>' }}]({{ post.url }}) (<time>{{ post.date | date:'%F' }}</time>){% endfor %}
{% endfor %}

doesn't work either, like:

{% for year in site.posts | group_by:"date | date:'%Y'" %}

and

{% for year in {{ site.posts | group_by:"date | date:'%Y'" }} %}

Thoughts on a Content Folder?

(tl;dr) Seems to me that it'd be great to put all content, whether that's collections, pages, or posts into one content folder.

Jumping in to collections I'm creating a site now that has a bunch of folders of varying content, plus regular pages and posts. This is getting unruly because in one directory I've got all those content files and folders and config files, CNAME file, etc. etc.

I've long put my pages in their own folder (_pages) and created an include directive for that folder in my config file and just set up permalinks in front-matter.

I don't think there's currently a way to do what I'm suggesting aside from altering the permalink in each and every document in the front-matter, but I don't think we should need to put permalinks inside of every document in a collection because that could be cumbersome and error prone for content creators.

I think someone on here had suggested essentially the opposite, putting layouts and includes in a theme folder, but at any rate, I'd like to be able to organize things a bit better.

I'd be interested in hearing any thoughts you guys have on this or any way you've handled this yourself.

jekyll / jekyll-help Goto Github PK

jekyll-help's Introduction

Philosophy

Getting Started

Diving In

Need help?

Code of Conduct

Credits

Sponsors

Contributors

Backers

License

jekyll-help's People

Contributors

Stargazers

Watchers

Forkers

jekyll-help's Issues

Decisions

Is it possible to access un-published posts or possibly drafts - to accomplish something like this?

TL;DR:

Long version:

Recommend Projects

Recommend Topics

Recommend Org